Updating logging code to what @Fy0urM suggested & Fix grammar & Remove Clone Army

https://github.com/masterking32/MasterHamsterKombatBot/discussions/147

Why do we need to save logs in a file when we already have a Telegram log? The Telegram log isn't easily usable for everyone.

Why do we need to save logs in a file when we already have a Telegram log? The Telegram log isn't easily usable for everyone.

yes you are right

Why do we need to save logs in a file when we already have a Telegram log? The Telegram log isn't easily usable for everyone.

I dont use telegram and would prefer local logs and since there is already code in main.py for local logging which doesnt work it makes sense to fix it.

tested the promogames.py as working.

an attempt to push logging into a file?)))
you can make changes to the file yourself, but it will have to be done every time the bot is updated, not very convenient. i have half the script in modifications))

output.log still has ANSI escape codes but at least its producing a .log file.

tested fully working, thanks @Fy0urM

Logging code now working in main, grammar fixed in README and Clone Army removed from promogames, please merge.

Logging code now working in main, grammar fixed in README and Clone Army removed from promogames, please merge @masterking32.

You need to create a separate PR for each feature you add. Please don't include all of them in a single pull request, as it makes it difficult to select or merge individual features. Additionally, I don't believe everyone needs a log file. For some, including myself, it could result in a large, unnecessary file. The current log system is intended for display purposes only, so it's not essential for everyone. For other features, please submit separate PRs. Thanks.


Adding issue template suggestions

Description
Created three issue templates (highly inspired from other places):

Bug report
Bug fix
Enhancement

The goal will be to try them for four weeks, on this core and lsm.
Related to https://app.zenhub.com/workspaces/core-5a7c152b04a1652024289b7b/issues/inmanta/infra-tickets/82
Please express your opinion in comments.

I couldn't add Alexy as a reviewer, how should we share it with him?

I guess this one can be closed


xref link to a list is not working when the topic is used as conref in another topic and published with transtype xhtml

Expected Behavior
xref link should work as a normal link
Actual Behavior
link is broken due to the wrong xref id generated
Possible Solution
xref id should be generated using the target element id
Steps to Reproduce
1.create a bookmap, keymap and 2 topics and use one topic inside bookmap and use other one as conref inside another topic
2. add ul list with specific id and link this list using xref in the same topic
3. use this topic as conref in another topic
4. publish xhtml and observe the link
5. link is broken
ouptut html

link to topic 1 list #id_mjp_kh5_hbc__d36e25

topic 1 list item

topic 1 list item 2

sample-code
Copy of the error message, log file or stack trace
log
Environment

DITA-OT version: 4.2.2
Operating system and version:Windows
(Linux, macOS, Windows)
How did you run DITA-OT? : dita
(dita command, Ant, startcmd, oXygen, other editor, CMS, etc.)
Transformation type:
_(HTML5, PDF, custom, etc.)_xhtml

In such cases the link href should be "#./ul-list"
https://www.oxygenxml.com/dita/1.3/specs/archSpec/base/uri-based-addressing.html#uri-based-addressing__topics-with-uri


When is the new release date of the sdk?

Hi guys,
I see that on master there is a much simplified version of middleware usage after this commit: https://github.com/aws/aws-xray-sdk-node/commit/a2344c47f60722b2b3b74eea5da897e86c09c5b4 . This is a great improvement as for example our middleware on Koa will be just a few lines.
When do you have planned to release the next version of the SDK with this change? It has been more than 1 month since the last version was released :).
Thanks in advance.

Hello,
We are actually about to merge our own community-contributed piece of Koa middleware in #317! We will make a new release of the SDK after that is merged, but I cannot give an exact date. Feel free to try our vended Koa middleware or continue to use your own :)

It looks like the PR for Koa was merged. Any updates on when a release will be put out that includes those changes?

It looks like the PR for Koa was merged. Any updates on when a release will be put out that includes those changes?

Yep, I had to tweak the coa middleware to work because of the logger refactor. middlewareLog is not a function error otherwise.

any updates on release date?

@cmckni3 can you elaborate on your comment? Were you experiencing a bug with the (as of yet unreleased) Koa support package?
As for a release, sorry for not corresponding earlier as I've been occupied with another project. I can't give exact dates but will prioritize a release in the near future and update this issue when it's done.

@willarmiros i copied the koa middleware from the contrib folder. It doesn’t work with the core package on npm because middlewareLog is missing.


Generate 1 snapshot per track

In currently version it s possible to persist all fingerprints in one file and do a load to initiate an analysis.
It would be interesting to be able to generate one file for each track and load all files from a directory. This facilitates the maintenance and distribution of fingerprint.

Please use SoundFingerprinting.Emy storage. More details here: https://hub.docker.com/repository/docker/addictedcs/soundfingerprinting.emy


[Cody Ignore] Fix defects arising from file based .cody/ignore

There's a file-based .cody/ignore feature, there's an remote configured Cody Ignore feature planned for Enterprise, we need to make these coherent. This records clean-up while reviewing the VSCode, extension code:
☢ probable ship blocking issue
👷 integrating new requirements w/ existing code
💪 defensive, mitigation
🧹 clean up
### Tasks
- [ ] ☢ getContextFileFromDirectory, callers searches current directory without consulting cody ignore; passed thru edit user context files
- [ ] ☢ getWorkspaceFilesContext searches workspace without consulting Cody Ignore
- [ ] ☢ vscode/src/edit/prompt/context.ts getContext passes thru "user" context without checking Cody Ignore
- [ ] ☢ vscode/src/editor/vscode-editor.ts getTextEditorContextForFile does not check Cody Ignore
- [ ] 👷 Expand ignore concept to repos, eg vscode/src/chat/ContextProvider.ts updateCodebaseContext should filter ignored repos
- [ ] 💪 Security review
- [ ] 💪 Audit uses of VSCode document getText, etc.
- [ ] 💪 vscode/src/prompt/index.ts buildInteraction uses fixup file URI without checking ignore, strengthen this
- [ ] 💪 Consider carrying file, editor content substrings in objects, not strings; use template literals for concatenation preserving taint.
- [ ] 🧹 vscode/src/editor/active-editor.ts caches lastActiveTextEditor for no purpose
- [ ] 🧹 `check/isCodyIgnoredFile` is unused (at least in JetBrains) in Agent protocol, so remove it; API as designed is weird (takes a list of files, returns a single boolean) and wasteful (checks all of the files to return `true` even if the first file is `true`)
- [ ] 🧹 There are "chat based" and "new" edit, unit test commands. Minimize risk by deprecating, removing unused commands.

@dominiccooney For the ☢ items, IIRC we removed isCodyIgnored checks from those on purpose because we have moved them to the prompt constructing step in SimpleChatModel and prompt-builder where context will be filtered before the request is sent to the LLM.

@abeatrix thanks for the pointers, I have moderated the language in the issue a bit—defects to risks, etc.
We still need to clean this up, because it relies on really long range dependencies lining up and staying aligned. For example, if EditManager.executeEdit are passed configuration.document that doesn't belong to the active editor, then we check whether the editor is ignored, but I believe we can pass the document+selection down to buildGenericPrompt and put the selection in the instruction.


Zoom/Pan animation and Fling/Flick guestures

Hi Guys,
This is an enhancement that I'd like to know if anyone would like to have as a setting/option.
I have built zoom/pan animation with acceleration UWP/Droid/iOS, I have also added "fling/flick" type deceleration. I did this in xamarin.forms using their Animation system but it shouldn't be a big deal to port that back to native since they have open source code which could be used as a guide.
I guess the question would be, is this a desired feature or would others prefer to do this on their own? Most Map tools include things like double click zoom/animation and fling type guestures. Assuming we leave it as an option feature of the map controls then I can't see a negative in including this in the Mapsui project. The way I wrote the fling/double click zoom it is similar to how I did the MapControl interations where it converts to non-native values and then uses shared code. Double click zooms about the point that you double click.
This could then be animated on 16ms ticks with a variety of different types of acceleration, i.e sin in sin out which is good for center point changes where it will accelerate till the half way point then decelerate to stop at the new center. Zoom is just be linear (but could be a setting), similar to the WPF scroll zoom. I have found this makes the map interaction feel much more natural, especially with the fling/deceleration. It just gets complicated to make them all settings rather than just included as it'd be a fair bit of if/else ifs etc to get the right combination based on the settings. I have found a weakness to the animation when MANY (i.e 1000+) bitmap symbols are on the map, but having this enabled/disabled will give the user the option.
There are some rules with the interactions that I have followed

New touches cancel all animations
All new animations cancel all other animations (i.e selecting a new center while a zoom or new center animation is going will cancel the other animations and start anew as the new animation.)

Cheers

I would like it. All things, that Mapsui bring in direction of a complete map api would be very good.

Sorry for my late reply.
Yes this is a great feature to have. I have some experience with this myself and it is something that can have a lot of nasty edge cases. The two rules you mention at the end are exactly the kind of rules to can help to keep it simple and prevent these edge cases.
My experience was that it better to do the animation at the level of the Mapsui renderer, and not at the level of the UI framework (which might seem attractive because it often has some animation functionality built in).
I used a cubiceaseout for feature animations:
https://github.com/pauldendulk/Mapsui/blob/41a20c5e80ea038efec47a0f19154a282cde1821/Mapsui/Layers/AnimatedFeatures.cs#L13
If could add a number of easing functions that could be used for various purposes. Also zooming from one polygon to another could benifit from a nice animation.
First we should have the shared project set up, no?

I started in my fork with the shared project. It works. You need only to add an  to the project files.
Btw. I started today to add SVG for markers. Works good. Could even change the color on the fly. Would be nice to have this as SymboleStyle :)

oh SVG markers is a great feature! Do you use the skia support for SVG?

I have already done SVGs using Skia, I just render them to bitmaps first and then use the bitmapids with the symbol style. SVG in skia a little unreliable as it doesn't support much of the SVG standards and I have had to do a fair number of preprocessing of SVGs to make them work well. I did this so I could change colors, and sizes from a single file.
The only thing I had to do after that was manage the bitmapids so that I reused the bitmaps rather than regenerating them based on the color replacements, sizes, scale etc.

Yes. 10 lines of code :)
And sorry, no WPF implementation. Perhaps we could do this later. Up to now, it is only in the Forms part.

How did you do the SVG Marker specifically? Do you have a link? As it would be good to natively draw the SVG rather than store a bitmap but I'd be worried about the performance side of it if it isn't caching the resulting bitmap. I am sure I'll still need to clean the SVGs alot to make them work but thats a one off thing.

Skia could be used for WPF by just using SVG to bitmap even for the XAML renderer as the code to make the SVG into a bitmap from an SVG wouldn't change anything. It'd just require Skia as part of the build even though its not the main renderer.

You should have the link. It is in my Mapsui repository in the branch Forms. You could find the code in Pin.cs. There are although samples for the Forms part. There you could test it. Each time you tap on the map, you set a new marker.

And yes, up to now, I convert the SVG to a bitmap. This is stored in the BitmapRegistry.

For cleaning, you could find online optimizer. Work perfect. But be careful, the Skia implementation is only a subset.

Yes the I have used SVGO for optimisation, but even then it doesn't work if you don't take out the x and y in favour of the viewport etc. I have written some cleaning code which is outside the scope of mapsui for this purpose.

I used SVGOMG, but asume, that it is the same.
I don't understand, what you mean with x and y.

Funny thing to have the tiger as marker image :)

Would it be helpful to have an extra SymbolSyle for SVG?

Next to bitmap and the built in ones?

First I thought, that this would be a good idea. Now I‘m not longer sure. Perhaps the bitmap is enough. It depends, if we draw the SVG each time or if we create a bitmap from it and use this for drawing.

For performance we probably want to rasterize but if you have symbols that differ in scale vectors are nicer. Maybe it should be optional.
Initially my idea was to have two options, vector and bitmap symbols. SVG would then parse towards the vector type. It seems however that skia has specific functionality to draw SVG, so perhaps there would be a place for a separate SVG type.

Possible an SVG layer? which could then follow the zoom level, i.e image overlays that map to the world coordinates.

I checked this today. Added SVG to PointRender for Skia. Works, but I have some problems with the hover events ;).
I check this tomorrow and, if it works, will make a PR.

This is still open, but I assume it is solved. We now have fling.


Update the getMyRights C++ snippet to the new C++ SDK version

:warning: depends on https://github.com/kuzzleio/sdk-cpp/pull/42 :warning:
Description
Since the last C++ SDK update, the user_rights* structure created in the C++ SDK by the auth:getMyRight API call is now correctly freed.
This cause another problem, since a vector is returned by that method, referencing pointers from the now deallocated structure. This dangling pointers problem causes random crashes whenever one tries to access the value returned by auth:getMyRight, as done in the C++ code example for that API method.
This problem has been resolved in this PR: https://github.com/kuzzleio/sdk-cpp/pull/42
This documentation PR updates the C++ example, as the type of the value returned by auth:getMyRight has changed.

 Snippets tests reports   SDK Version Tests overview      v6        v5                           :heavy_check_mark:                            v1        v1        v1


Enhance Mobile Responsiveness for Contributors Component

We're looking for community help to improve the mobile responsiveness of our Contributors component in the free-api-list-with-react project. This component currently uses Material UI components and is designed primarily for desktop view. We want to ensure a seamless and user-friendly experience on mobile devices as well.
Current Behavior:
The Contributors component displays a table with the columns: Name, Contributions, Last Contribution Date, and GitHub Profile.
On mobile devices, the table does not resize or reformat, leading to a cramped and hard-to-navigate interface.
Desired Behavior:
The table should be easily readable and navigable on mobile devices.
Consider reformatting the table layout, adjusting font sizes, or implementing a different UI pattern (like cards or a collapsible list) for mobile view.
Ensure that the design is consistent with the overall aesthetics of the application.
Technical Details:
The component is implemented in React.js using Material UI components.
Please make sure to adhere to the existing coding style and comment on any significant changes.
How to Get Started:
Fork the repository and set up the project locally.
Reproduce the issue by viewing the Contributors component on a mobile device or using a mobile view in your browser's developer tools.
Experiment with different UI solutions to improve the mobile experience.
Once a suitable solution is found, create a pull request with your changes.
Additional Resources:
Material UI Documentation
React Documentation
We appreciate any contributions made to this project and look forward to your innovative solutions!

Hi @Curtis-Thomas , I am working on this issue.


Implement acknowledgement for the compound config

The PR adds seq and ack_seq fields for the CompoundEdgeDevConfig and ConfigRequest messages.
seq and ack_seq implement compound config acknowledgements. Every request from EVE is sent with the last "seen" and processed compound config aka 'ack_seq' field, every compound config sent from the LOC contains the 'seq' field, which is guaranteed to be incremented once new command is created by the user.
For the compound config message I change the order of all fields to have the sequence field to be the first. This is safe, because the structure is not in use anywhere.

Difference to the previous version:

Create a separate message CompoundEdgeDevConfigRequest which includes the ConfigRequest and the ack_seq field.
Code comments tweaks.

Difference to the previous version:

rename cfgReq to cfg_req
a few code comments tweaks

Difference to the previous version:

Rename seq/ack_seq fields to timestamp/last_cmd_timestamp as requested by Erik


Supporting rememberLastLogin option

Describe the problem you'd like to have solved
Hi, I'm wondering if this library will support the rememberLastLogin option from some of the other SDKs (https://auth0.com/docs/libraries/lock/v11/configuration#rememberlastlogin-boolean-) as we've lost this feature switching over to the hooks-based solution.
Describe the ideal solution
The rememberLastLogin setting is supported via the React SDK
Alternatives and current work-arounds
I've tried adding this to https://auth0.github.io/auth0-react/interfaces/withauthenticationrequiredoptions.html#loginoptions even though the option isn't listed but doesn't seem to be implemented
Additional context

Hi @jhebb - looking at https://auth0.com/docs/libraries/lock/v11/configuration#rememberlastlogin-boolean-
"New tenants automatically have Seamless SSO enabled. With this enabled, the rememberLastLogin option will not be relevant because if there is a session in place then the hosted login page will not be displayed at all. Using Seamless SSO is highly recommended because it provides a seamless authentication experience: users log in once and won’t have to enter credentials again when they navigate either through the applications you have built, or third party apps. If the user is not logged in they will be redirected to the login screen, as expected."
Instructions on how to check the Seamless SSO setting in your tenant: https://auth0.com/docs/dashboard/guides/tenants/enable-sso-tenant

Hi @adamjmcgrath - thanks for the reply.
Maybe I'm misunderstanding how the rememberLastLogin feature works - enabling Seamless SSO doesn't seem to make a difference, but i'm testing by explicitly logging my user out via the logout action in useAuth0() so perhaps Auth0 doesn't try to remember your user in that situation?

Hi @jhebb by default logout will log you out of your Auth0 session too. You can do logout({ localOnly: true })to prevent this https://auth0.github.io/auth0-react/interfaces/logoutoptions.html#localonly
But beware, we have a known issue with localOnly #72 so you'd need to do something like logout({ localOnly: true }); window.location.reload() as a workaround before we fix it

If I leave Seamless SSO off and use localOnly: true, then I get the behaviour we had from before, but reading the docs you provided I see that maybe this isn't the experience we want so I'll re-assess our goals first.
Thanks for the info, and feel free to close since this behavior already exists!

Will do - thanks @jhebb


feat: coproducts in the category of Ind-objects

Shows that

the functor C ⥤ Ind C preserves finite colimits,
if C has coproducts indexed by a finite type α, then Ind C has coproducts indexed by α,
if C has finite coproducts, then Ind C has small coproducts.

The proof that finite coproducts exist is pretty magic; I started with a proof that is several hundred lines long and reduced it bit by bit to the nine lines it is now. You can't really see anymore why the result is true, but that's okay I think.
I'm not worried about the large-import label; Indization/Category.lean is supposed to be the file you import if you want Ind C with all its properties, so it's inevitable that it pulls in a lot of basic category theory.

Thanks!
bors merge

bors d+

bors r+


build: update 1.4 release for -nopie fix

#21042 fixed an issue in the 1.4 release branch. We should update the 1.4 source release tarball and docs.
@broady @bradfitz

Tangential, but I'd suggest changing the milestone name to go1.4-bootstrap and the milestone description, it's quite misleading

We will likely never make a Go 1.4.4 release. The only reason to do so would be to ease bootstrapping of newer Go releases

a) we regularly publish new go1.4-bootstrap releases to "ease bootstrapping" b) they're not called go1.4.4, they're called go1.4-bootstrap

I'd suggest changing the milestone name to go1.4-bootstrap and the milestone description

Huh. Apparently I can edit milestones (!). Done. Anyone who cares about the text there should review. cc @kevinburke in case maintner cares. I left the capital "G" in the milestone name to match the others for now.

Huh. Apparently I can edit milestones

@josharian me too. I think it's normal (for users marked as Member).
I asked (instead of changing it myself) because I wasn't sure people would be fine with it.

I asked (instead of changing it myself) because I wasn't sure people would be fine with it.

Guess I'll ask forgiveness instead of permission then. :) I wish GitHub had all this config in the repo itself, so this could be codereviewed.

@ALTree yes, thanks.


Modal is closing when press space

Prerequisites

[X] I have not leaked any internal company information.
[X] I have not posted internal links or code snippets.

What happened?
I have switch button in modal, and closeOnBackdropClick:true,
If I focus the switch button and press space to change status. modal is closing immediately
What type of frontend frameware are you seeing the problem on?
Angular
Which version of iX do you use?
latest
Code to produce this issue.
you can check here
https://stackblitz.com/~/edit/xnfrdi-hwdxjf

Internal ref [IX-908]

A fix for this issue is now available in v2.1.1-beta.0.
We kindly ask you to install this version in your dev environment to check if it resolves the problem for you and give us some feedback about this.

Hi @danielleroux ,
It is working like a charm.
many thanks


fix(frontend): 🐛 users without token no longer cause error on scan

when scanning plex server causes an error occur when guest account is enabled

i need someone to test to make sure this still works on jellyfin with these changes

i need someone to test to make sure this still works on jellyfin with these changes

Just testing functionality? Or is there a specific feature in mind that needs testing?

@PhantomMantis Scanning works as intended on Jellyfin, not sure what else you require me to test. Both normal avatars and ones without an avatar work fine.

Fixes #339


When the property contains an array an assertion to validate an empty field is generated

Hi everyone, when I tried to run the generated tests for the following response body the tests are failing due the following assertion is being generated:
assertThatJson(parsedJson).field("['something']").isEmpty();
response {
status 200
    headers {
        contentType(applicationJson())
    }
    body(
            something: [
                    "fields":
                            [
                                    field1: 49.75,
                                    field2: 6.1667
                            ],

            ],

            "transactionId": consumer(regex('[0-9a-fA-F]{8}\\-[0-9a-fA-F]{4}\\-[0-9a-fA-F]{4}\\-[0-9a-fA-F]{4}\\-[0-9a-fA-F]{12}'))

    )

    bodyMatchers {

        jsonPath('$.something.fields.field1', byRegex(nonBlank()))
        jsonPath('$.something.fields.field2', byRegex(nonBlank()))

    }
}

Version: 2.1.1.RELEASE
This happens when I have the body and the body matchers defined in the response.
I really appreciate your help.
Thanks.

Please always upgrade to the latest version before filing an issue. We already have 2.1.5.RELEASE and maybe your issue is already fixed?

Ok thanks.


Running duster via composer script causes event returned with error code 1

I run duster via a custom command configured in the composer.json file:
"scripts": {
    "format": [
      "vendor\\bin\\duster fix --dirty"
    ],
    "format:all": [
      "vendor\\bin\\duster fix"
    ]
  }

Since one of the latest versions however, the script stops somewhere when running the Fixing using Pint part with the following error:
Script vendor\bin\duster fix handling the format:all event returned with error code 1
However, when running the comment vendor\\bin\\duster fix manually in the console the process finishes as usual.
Anything I could additionally check to see where the error is coming from?

You could try appending -vvv verbose flag to the command:
vendor/bin/duster fix -vvv

Unfortunately, that starts dumping the whole source code to the console showing all changes when the Pint part is started, probably because TLint and PHP_Codesniffer applied their rules before. No obvious additional error is shown.
I still wonder why calling vendor\\bin\\duster fix directly runs fine but using a custom command returns error code 1.

After using it for some while with the error, it just seems thats normal. No issues during formatting, everything works as expected except that at the end the error code 1 is shown.

This is also happening to us. It runs fine with no errors alone, but from composer invocation, it has this:
Script @php vendor/bin/duster -v fix handling the lint event returned with error code 1


[?] Migrations

I ran the cookiecutter and pushed this project to a GitLab repository. I set up a VPS with Docker Swarm and GitLab Runner (based on the instruction from dockerswarm.rocks). I ran the pipeline and the test, build and deploy-stag completed successfully. I can access everything on stag.domain.com without issues. Then..

I made some change to the user model (split full name to first and last name) in the gitlab repository master branch and committed the changes. But the CI/CD job failed, because the backend container failed, because the column did not exist in the table, because there was no migration done. How do I make migrations and migrate automatically when I make changes to the GitLab repository with this set up? Why is it necessary to manually enter the container and make migrations using alembic?

Any time there is a new commit, I want it to make the migrations (if applicable) and migrate automatically, otherwise the backend container will fail every time.  It seems unnecessary to manually connect to the backend container and make the migrations each time. How do I accomplish this?

How it should work:

Upload repository to GitLab
Run CI/CD pipeline
Make changes to files in repository
Commit changes
Repeat steps 2-4 again and again in the same way, forever

Why are there so many extra steps?
I've been pulling my hair out for a couple days on this.
Thanks in advance!

Solution can be found here: https://github.com/sqlalchemy/alembic/issues/80

Thanks for reporting back and closing the issue :+1:


Permission denied issue

(venv) ➜  python-demo-bot ./bin/proxy
zsh: permission denied: ./bin/proxy

I know chmod or chown might fix this issue. I am wondering can we avoid this issue altogether?

I installed pip3 with hombrew, I do not need sudo in my mac.
Fixed bin/* permission probblem
try pip3 install 'ringcentral_chatbot_factory>=0.0.2' to upgrade


stop does not return

When i run the asyn-profiler with -e cpu i am not able to get it to return any data after i invoke profiler.sh with the stop argument.
It works fine when the system is not too busy. But if i try to capture data when the process is busy, i dont see errors, but the call does not return. The process does not consume too much CPU either.
I tried to strace the jattach call on stop which is left hanging - i can see that its stuck on a read call (file descriptor count 3 - which is  3 -> socket:[14138219] as reported from proc) but thats pretty much it.
I can also see a few errors messages "perf_event mmap failed: Operation not permitted" initially but it does not repeat unlike where the kernel settings are not changed.
Would appreciate any help on this. Is there a limit on the no of samples that can be collected?
Thanks
process is 32 bit
Kernel = Centos 7 = 3.10.0-8<IP_ADDRESS>.el7.x86_64
perf rpm =  perf-3.10.0-693.el7.x86_64
Java version = java version "1.7.0_191"
Perf settings applied :
echo 1000000 >  /proc/sys/kernel/perf_event_max_sample_rate
echo 50 > /proc/sys/kernel/perf_cpu_time_max_percent
echo 0 > /proc/sys/kernel/kptr_restrict
echo 1 > /proc/sys/kernel/perf_event_paranoid

There was a report on a similar issue - #221. Still not sure about the reasons :(
Looks like perf_event_open syscall becomes slow in some cases, so that profiler's start command does not complete in a reasonable period of time. Then stop command hangs as it waits AttachListener to complete a previous command.
Does your application run many threads under load? (I mean, thousands). How long does the profiling session run?
Try

increasing profiling interval -i
-e itimer mode

I guess itimer should help, since the problem seems to be hidden somewhere inside perf_event_open.
Also perf_event mmap failed: Operation not permitted message means that perf_event_mlock_kb has exceeded. It's not a fatal error, but it's better to increase the limit as described here.

I have moved to later version of JVM and 64 bit in the hope i will be running something more closer to whats being used commonly.


Add new feature to review the pull request and suggest adding license headers

Example https://github.com/kezhenxu94/skywalking-cli/pull/4

Interesting feature :)

Interesting feature :)

This can be a distinguished feature why people should migrate from existing license tool (rat, checkstyle, etc.)


Add support for parent document URL to Asset Manager

Whitehall attachments can include a Link header containing the URL of their parent document (added to Whitehall in alphagov/whitehall#2202). We need to add support for this functionality to Asset Manager so that we can serve Whitehall attachments from this app.
Although this is primarily for Whitehall attachments I felt that it'd be less confusing to add support for it to both non-Whitehall and Whitehall assets.

I've rebased this on master and force pushed in preparation for merging.


Broken backtab key on st.

Before 1.3.0, Shift+Tab would be properly detected on st and return 78 and Backtab on tcell.EventKey.Key() and tcell.EventKey.Name() respectively, but now I get 256 and Alt+Rune[[].

Probably I didn’t have a current terminfo for this when I regenerated the database.

Hey @gdamore , we are facing a similar problem in the following issue: https://github.com/Bios-Marcel/cordless/issues/247
In our case it's not Shift+Tab though, but Alt+ArrowKey, which also just gives us Alt+KeyRune.

I think #369 will address the Alt key mixing with arrow keys.
I'm less confident of Shift Tab.

So it appears that the "st" terminfo entry lacks kcbt -- which means that we don't encode back tab.  This is unfortunate -- we need a more complete terminal definition for it.

So good news, the git repo for st does have a useful definition that includes kcbt.


Trim whitespaces/fix types error

semicolon or no semicolon? It's mixed currently

I'm generally a no-semis person, but I'm not offended too far either way 👍🏻

Ace, this is better than today


Improvement for k8s.io/docs/tasks/administer-cluster/ip-masq-agent/

please add clarification in the case of containers, where are containers masq records saved or how to track down which container initiated a connection behind node ip

/language en
/kind support

Hey, I think this is not a support request, however, it would require more information.
Have you checked the IP masq agent documentation as well that this page link to for more precise information on these topics?

If you can describe what you wanted when you wrote

how to track down which container initiated a connection behind node ip

then @porrascarlos802018 we might be able to make that into a request to improve the documentation.


Make ColumnSize be size in characters after encoding

Fixes https://github.com/mkleehammer/pyodbc/issues/221

I have confirmed that this tweak fixes the error that I was getting with "ODBC Driver 13 for SQL Server" under Linux (ref here).

This looks good, but once again there are a bunch of merge commits.  I'm not sure why that is the default on your system.  Can you rebase and/or cherry-pick to move this commit to the end?  Thanks

Trying again at https://github.com/mkleehammer/pyodbc/pull/287 . Closing this one now.


Replace incorrect granular by set/map

Fixes #25153
/cc @TBBle

Page preview:
https://deploy-preview-25155--kubernetes-io-master-staging.netlify.app/docs/reference/using-api/server-side-apply/#merge-strategy

/lgtm

/approve


add a Makefile?

The test tool people might be used to running (go test ./...) both iterates over the vendor directory and is slow (98 seconds on my machine).
maybe we could add some targets for e.g. make test, make race-test, make unit, make vet to tell people how to run the tests in various circumstances? Also could use those targets in the .travis.yml file.

hahha I tried this: https://github.com/golang/dep/pull/51
but to be honest the go team seems to be pretty against makefiles and running tests is as easy as go test w no args same goes for install and build so i dont really see an issue

ok

I use an uncommitted Makefile so that I don't forget key steps before submitting a PR. I may not be the only contributor who would appreciate a single command to validate their branch before making making preventable mistakes (like forgetting to run go fmt or adding a new test file without a license at the top).


dlang.org: issuing "make" after a successful "make" does a lot of work

Andrei Alexandrescu (@andralex) reported this on 2017-12-11T23:54:48Z
Transferred from https://issues.dlang.org/show_bug.cgi?id=18064
CC List

berni44 (@WalterBright)
Seb

Description
We want to create dependencies properly so we don't wait a long time when building the site.

greeenify commented on 2019-12-14T19:07:55Z
@berni44: FYI you almost never want to run the full dlang.org target. 'html' or 'phobos_prerelease' should be the two most common targets.

bugzilla (@WalterBright) commented on 2019-12-14T18:52:39Z
Seems still be valid:

$> make -f posix.mak -j3
[...]
$> time make -f posix.mak -j3
[...]

real    1m54,227s
user    4m25,409s
sys     0m18,270s


Update for security response in bundle sub calls.

Description
This makes it so that when a sub call within a bundle received a 403 response that the correct HttpContext is updated.
Related issues
Addresses [issue #].
Testing
Describe how this change was tested.

As discussed, we should have an E2E test for this


[Issue] - Automation rules must appear at the top or bottom of the column in order to run.

The automation rules are not running unless the Automation Rules card is located at the top or bottom of the list. If the card is located between two or more issues the automation rule is not applied.

I'm by no means a dev, but based on the comment here and a surface-scan of the code below it, I would venture that this is not so much a bug as an undocumented requirement. I'll submit a PR to update the README.


ENH: new Signature API

The .defaults property has been replaced by storing a ParameterSpec for
every public parameter. inputs, paramters, and outputs are still present
but now map a parameter name to a ParameterSpec.
The ParameterSpec has three properties: qiime_type, view_type, and
default. Additionally it provides has_<property> helper methods to
determine if any of the prior properties exist in a given ParameterSpec
instance.

This is going to break everything. Working on corresponding interfaces now.

q2cli: https://github.com/qiime2/q2cli/pull/106

flake8 failures

👍, thanks @ebolyen!!


Quick Test Routine After Import

Hi,
we are currently facing an interesting issue downstream in setuptools with an imported, incompatible Cython install that might exist in a user's environment, e.g. while working with python virtual environments, conda or spack: https://github.com/pypa/setuptools/issues/1229#issuecomment-349644856
The main issue comes down to the fact that a downstream "optional usage of Cython" in the form of
try:
    # Attempt to use Cython for building extensions, if available
    from Cython.Distutils.build_ext import build_ext as _build_ext
except ImportError:
    # some fallback such as
    _build_ext = _du_build_ext

will not catch any errors that can occur when using a compiled library such as Cython. Exemplary errors can look like
failed to import Cython: /home/axel/.local/lib/python2.7/site-packages/Cython/Compiler/Scanning.so: undefined symbol: PyUnicodeUCS4_DecodeUTF8
Unexpected error: <class 'distutils.errors.DistutilsPlatformError'>

in the case of symbol mismatches between currently used virtual environment, system or user libraries. Unfortunately, such errors are not triggered on import but as soon as the imported functionality is used later on. (A full reproducer is posted here including a Dockerfile.)
We were wondering if there already is or if one could add a short, side-effect free "test" interface that one could call directly after the import in the same try scope in order to reliably trigger and catch incompatibly imported Cython installs?
Any feedback or suggestions are very welcome!

Closing, as I think an explicit import solves this issue.


Annotate natOutgoing used to be nat-outgoing in v1 api

Description
Annotate natOutgoing used to be nat-outgoing in v1 api.
Todos

[ ] Tests -- I'm going to assume that upgrades, when they're supported, will test this.

Release Note

None required

closing ...


Docker causing unexpected behavior

Hello,
Installing and starting docker is causing me every type of problem when running jobs. The cluster is running on CentOS8 and with v2.10.2. The jobs keep running (not doing anything productive) but I can see messages such as:
taskid: 3 hostname: compute-st-r52xlarge-1
[compute-st-r52xlarge-1][[11331,1],3][btl_tcp_endpoint.c:626:mca_btl_tcp_endpoint_recv_connect_ack] received unexpected process identifier [[11331,1],1]

which reflect that something is just not right. Should I expect this behavior even without doing anything with a container?
Thanks.

Hi @afernandezody,
From the messages you provided, it's not clear to understand the problem and root cause, could you provide more information like:

How and when is you installing and running docker?
Are there any other logs you can provide that might help us to investigate the problem?

Hi @yuleiwan,
Firstly, let me clarify that there is no error message per se (beyond the previously mentioned message) so let me try to explain the issue in greater detail. It has been causing me trouble since Saturday so I have tried several things.
Method A - I created a custom AMI where Docker is installed. For CentOS8, the installation reads:
sudo dnf config-manager --add-repo=https://download.docker.com/linux/centos/docker-ce.repo
sudo dnf install docker-ce --nobest -y
sudo systemctl enable --now docker
sudo usermod -a -G docker centos

These commands are slightly different than for Alinux2. Anyhow, checking docker status return enabled as expected. This was my original configuration on Saturday when I launched the 1st cluster. It actually kept running for almost 2 hours until I realized that the ranks were running (checked the compute instances) but there was no progress at all. After several attempts, it was evident that the cluster runs the jobs without any issue when no Docker is active but, when this is active, the jobs don't make any progress even if the cores are apparently crunching numbers.
Method B - Docker is installed as a postscript. The logs report this installation and chef completes as usually. Then, it's the same story (cores are running but there is no progress and I can see the "unexpected process identifier message").
Please let me know if this is now clear enough.
Thanks.
cfn-init-cmd.log

Hi @afernandezody,
Thanks for your details. I tried to reproduce the issue on centos8 pcluster 2.10.2, but I can't. I just installed and enbaled the docker on cluster as the commands you provide and submit a simple job, it succeeded.
Are you using slurm as scheduler? Could you check slurmctld log to see you job status and use command `scontrol show jobs -o {job_id} to see the job status?
Thank you

Hi @yuleiwan,
scontrol is returning
JobId=2 JobName=EXE_2
   UserId=centos(1000) GroupId=centos(1000) MCS_label=N/A
   Priority=4294901759 Nice=0 Account=(null) QOS=(null)
   JobState=RUNNING Reason=None Dependency=(null)
   Requeue=1 Restarts=0 BatchFlag=1 Reboot=0 ExitCode=0:0
   RunTime=00:00:32 TimeLimit=UNLIMITED TimeMin=N/A
   SubmitTime=2021-03-18T23:01:34 EligibleTime=2021-03-18T23:01:34
   AccrueTime=2021-03-18T23:01:34
   StartTime=2021-03-18T23:01:34 EndTime=Unknown Deadline=N/A
   SuspendTime=None SecsPreSuspend=0 LastSchedEval=2021-03-18T23:01:34
   Partition=compute AllocNode:Sid=ip-172-31-35-136:5650
   ReqNodeList=(null) ExcNodeList=(null)
   NodeList=compute-st-c6gmedium-[1-2]
   BatchHost=compute-st-c6gmedium-1
   NumNodes=2 NumCPUs=2 NumTasks=2 CPUs/Task=1 ReqB:S:C:T=0:0:*:*
   TRES=cpu=2,node=2,billing=2
   Socks/Node=* NtasksPerN:B:S:C=0:0:*:* CoreSpec=*
   MinCPUsNode=1 MinMemoryNode=0 MinTmpDiskNode=0
   Features=(null) DelayBoot=00:00:00
   OverSubscribe=OK Contiguous=0 Licenses=(null) Network=(null)
   Command=/home/centos/EXEBench_2.sbatch
   WorkDir=/home/centos
   StdErr=/home/centos/output.txt
   StdIn=/dev/null
   StdOut=/home/centos/output.txt
   Power=
   MailUser=(null) MailType=NONE

I'm not that familiar with slurm internals so any help is welcomed. Thanks.
slurmctld.log

From slurmctld log, I saw it was the first job you submitted to scheduler, there may get stuck when you spin up the compute instances, but I am not sure about the root cause right now. Could you scancel {job_id} to cancel the job and resubmit it? If it still doesn't work, we need your job script without confidential and personal data to reproduce your issue for further investigation.

I terminated the cluster so I'd need to launch it again. However, I only submitted one single job and I never log in before the whole cluster launch is complete.
I was trying to decipher why the log is claiming that it cannot open the node_state or trigger_state files, but I can tell you that. based on the time stamps, these warnings/errors happened during the spin up (before I logged in). Something else is that my jobs are always numbered starting with 2 (not that this matters per se but makes me wonder if something else might have gone during launch).
[global]
update_check = true
sanity_check = true
cluster_template = w1cluster

[aws]
aws_region_name = us-east-1
aws_access_key_id = ***
aws_secret_access_key = ***

[cluster w1cluster]
vpc_settings = odyvpc
placement_group = DYNAMIC
placement = compute
key_name = llave_i3
master_instance_type = c6g.medium
compute_instance_type = c6g.medium
cluster_type = spot
initial_queue_size = 2
max_queue_size = 2
maintain_initial_size = true
scheduler = slurm
base_os = centos8
custom_ami = ami-***
master_root_volume_size = 50
compute_root_volume_size = 50
post_install = ***
post_install_args = ***
additional_iam_policies = ***
tags = ***

[vpc odyvpc]
master_subnet_id = subnet-***
vpc_id = vpc-***

[aliases]
ssh = ssh {CFN_USER}@{MASTER_IP} {ARGS}

Hi @yuleiwan,
I have finished some further testing and my observations are pretty much the same as yesterday. Let me begin with a very vanilla config without any custom AMI:
[global]
update_check = true
sanity_check = true
cluster_template = w1cluster

[aws]
aws_region_name = us-east-1
aws_access_key_id = ***
aws_secret_access_key = ***

[cluster w1cluster]
vpc_settings = odyvpc
placement_group = DYNAMIC
placement = compute
key_name = llave_i3
master_instance_type = t3.micro
compute_instance_type = c5.large
cluster_type = spot
disable_hyperthreading = true
initial_queue_size = 2
max_queue_size = 2
maintain_initial_size = true
scheduler = slurm
base_os = centos8

[vpc odyvpc]
master_subnet_id = subnet-***
vpc_id = vpc-***

[aliases]
ssh = ssh {CFN_USER}@{MASTER_IP} {ARGS}

This doesn't do much but the slurmctld log (attached) still claims some missing files during the spin up period. After it, I launched a larger cluster (2xr5.2xlarge) with a custom AMI. This one doesn't have any Docker stuff and the app runs without any issue. Once the job is running, the slurmctl.log has added the lines describing the job
[2021-03-19T11:12:08.964] _slurm_rpc_submit_batch_job: JobId=2 InitPrio=4294901759 usec=282
[2021-03-19T11:12:09.220] backfill: Started JobId=2 in compute on compute-st-r52xlarge-[1-2]
[2021-03-19T11:12:09.220] prolog_running_decr: Configuration for JobId=2 is complete

and scontrol return is very similar to yesterday's (when the cores are running but with no progress). I really don't know why the presence of Docker is causing these issues.
Thanks.
slurmctld.log

Hi @afernandezody,
Your case is very similar to this github issue about extra docker network interface in cluster. Could you confirm if it helps your issue. Meanwhile I will use your config files to try to reproduce the issue and do investigation.

Hi @yuleiwan,
I missed that thread in my initial search for related issues and didn't cross my mind that Docker was creating the network interface and messing with the MPI wrapper. It seems to be working now so I'm closing the ticket.
Thanks.


Calling WebService Method throws Exception

I am unable to call the WebService method and it results in below exception thrown.
Message part x00A0 in namespace urn:xxxxx appears more than once in Message.
Here xxxx refers to my webservice interface.
Calling the same method through the executable which is not Obfuscated it works fine. I am using latest build .32.
Application being built using Visual Studio 2017 against Dot Net 4.5.2
I tried all combinations of below xml attributes but still not getting to work.

I solved this issue by changing the config.xml file

Closing this issue.


Docs: Use same subtext typo in API as example pages

Description

Now the API page matches the example page
How Has This Been Tested?

visually
Type of Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[X] Documentation (fix or improvement to the website or code docs)

Example page:

API page, before:

API page, after:

Checklist

[X] The PR is submitted to the correct branch (dev).
[X] My code follows the code style of this project.
[ ] I've added relevant tests.

Here's where the example header markup is defined
https://github.com/MudBlazor/MudBlazor/blob/c3c77f14f888faf13b5a1d029e9109e61cfc62ce/src/MudBlazor.Docs/Components/DocsPageHeader.razor#L34-L39

@jperson2000 I noticed this affects the description text as well (too large now). Is it possible for me to decouple that easily?

@jperson2000 I noticed this affects the description text as well (too large now). Is it possible for me to decouple that easily?

Hi Daniel!  Hmm, since both places use the ApiText component, I think we'd need to add a Typo parameter to ApiText to allow it to be explicitly specified.  Then, one more change would be needed to add a Typo parameter to the AddMudText extension method.  This should help to customize the size for the page description versus member descriptions.

@jperson2000 Thank you for the pointers! I'll wait for #9316 before I make an attempt

TODO:
Make this text bold:

not all of it just the component name, im sure it looked like this before

Garderoben


feat: Implement EFS IOPs specification in Project YAML

Description of Changes
We want to be able to specify the filesystem used and the throughput. This allows customers with large numbers of large files to accelerate workflows. Filesystem options are S3 and EFS, with a default of S3 for Cromwell and Nextflow and a default of EFS for MiniWDL. Valid throughput values are 1 to 1024.
Description of how you validated changes
I have added a test that checks that the default throughput is set. I have run ./scripts/run-dev.sh and agc project validate with a valid agc-project.yaml and an invalid version containing an invalid filesystem.
Checklist

[ ] If this change would make any existing documentation invalid, I have included those updates within this PR
[x] I have added unit tests that prove my fix is effective or that my feature works
[x] I have linted my code before raising the PR
[x] Title of this Pull Request follows Conventional Commits standard: https://www.conventionalcommits.org/en/v1.0.0/

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

Can you check and see if it's possible to enforce values for engine and filesystem in the packages/cli/internal/pkg/cli/spec/project_schema.json. For example, currently cromwell and nextflow must use s3 and miniwdl must use EFS.
You will also need to add logic so that the fileystem information is passed through to the cdk that generates the filesystem so that the resulting EFS volume has the desired provisioned IOPs.

Looking good. General comments:

Does the code handle the case where EFS is specified as the filesystem but provisioned IOPs is not (meaning you get the default MaxIO with burst mode). Provisioned IOPs is optional.
There seems to be a lot of content from the snakemake implementation. Possibly a rebase on top of HEAD would generate a cleaner commit?


multi detection simultaneously

I have 4 camera on my system and I want to detect object from this cameras simultaneously.
For each detection for one camera, i should detect 2 times with different configuration and weight.
How can I achieve this? or at least, is it possible?

I think it is possible but i must change before some logic of the code. Have you try with to separated processes?

I am going to use 4 threads, so one thread per one camera.
And for 2 times detection per one camera,
currently, i made the YoloWrapper1 class that copied YoloWrapper class,  and imported the Yolocpp1.dll (that copied Yolocpp.dll).
And detected the object 2 times for one camera using Yolowrapper, Yolowrapper1 class.
But this way is too troublesome.
Maybe in yolocpp. dll, only allow one instance for one weight, one configuration.
I'd like to u add the function for multi instance.

I have check the current code, but i think currently is not easy viable. You must split your code into individual processes.

I'm not sure if it would be accepted, but I have local modifications to darknet that removes the static instance of the detector inside the dll. I'll submit a pull request later this week.
The init method returns a pointer from the detector. You'd have to pass it to the detect method and to the clean method. By tracking the pointer yourself (aka, in the C# code) you could spawn as many instances of the detector as you have resources to handle.
I am a C++ newb, so I'm not sure how "correct" my change is, but I'll post it over on darknet later anyway.

I submitted a pull request. If accepted, with some modifications to your version of the YoloWrapper (see my update to the one in the pull request), each instance of the YoloWrapper would have it's own backing Darknet detector.
https://github.com/AlexeyAB/darknet/pull/2830

Hi all! Is there an update on the progress of the current pull request for multi detection?
Hi @randellhodges, have you manage to find out what the maximum number of models you can run with your current solution?
Thanks all!

What is the reason for run multi detectors?

Well, one reason i'm using this is for daisy chaining multiple models.

Dispose and Initialize is to slow?

Well, essentially i would like to daisy chain a few Yolo models as follows:
Image => Model 1 => Crop image where detection was found => Model 2 => Repeat
The image is coming directly from a camera feed. All this are running at GPU speeds.
However, I wouldnt know how would disposing and reinitialising for each model would affect the speed

I have add a new webservice project. You can start this project twice and load different configurations. Alturos.Yolo.WebService
In the app.config you can set the service port.
You can test it with the swagger interface http://localhost:8080/swagger

Take a look here (workaround): https://github.com/AlturosDestinations/Alturos.Yolo/issues/68#issuecomment-521122054

Hi,
I am detecting object using 2 cameras .. one code..my question
is it possible to give the object on both camera same detection ID (in other words; identify the same object on both cameras?)
thank you in advance

Yolo can only detect a object type. Your logic must calculate that the position of camera1 match the position of camera2


Sending operation times out in Unity 2020

Narrowed down the issue to a HttpClient.SendAsync call in ServerAPI that never returns.
This leads to the server transport deadlocking and timing out.
The issue appears to be fixed in Unity 2021, so perhaps this is a known issue on Unit's side?
See https://speckle.community/t/some-funk-in-unity-with-helpers-send-vs-operations-send/2582

Now I've confirmed it's specific to Unity 2020, this issue is a low priority.
Parking this issue for now until someone complains 😁


Update meta.yaml

Add K8S API
Add local test

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Modification meta.yaml : ajout dépendance kr8s et test local

@conda-forge-admin, please add user @criou-cg


📝 draft community/communication page

A draft with links to social accounts, etc.
Please improve wording. Should we include Discord or drop it? =)

Is the Discord server supposed to be used just for CF stuff or also projects (those that decide to spin off a dedicated channel I suppose).

Is the Discord server supposed to be used just for CF stuff or also projects (those that decide to spin off a dedicated channel I suppose).

In my head: it's CF as a community (towards the IRC-feel that folks remember from Commonhaus .. mailing lists aren't really that for me anymore)

In that case it should be listed as well.

I think I will leave it as supporter-only benefit, and will add a link to the community on the supporters page to help curb spam.
I'll also double check with another community on how they do role assignment associated w/ support..

Merged to make progress. We can make additional revisions as we go.


:seedling: Enhance error message for cross-rs webhook execution

Close this one, will be addressed in a future version 📜 Roadmap (Retry when failed to push because of a locked mutex
).


Strange issue with json data

I have a simple json file, can be seen http://squid.live/folders.json when I load this in
this.$http.get('/folders.json').then(
            // success
            function (response) {
                // use response.data to populate the assets and folder structure
                console.log(response);
                this.folders = this.unflatten(response.data);
            },
            // failure
            function (response) {
                alert('Failed to load folders.json');
            });

any item with a parentId of 0 then has an id of undefined?!
If I change id to something else then it seems fine. Am I missing something with tracking or the likes? (Vue 1.0.16, resource 0.7.0)

Noting, if I use  Vue.http.get and console log the response then the data is as expected... until I try and do anything with it, e.g. add var that=this then that.folders = that.unflatten(response.data);

Is it maybe an issue with the unflatten function that handles the 0 parents wrong ?

 Sorry for wasting your time :(


optimistic locking error log with 'version-required'

Given the following code:
db.config.serverprops.write({'update-policy': 'version-required'}).result().then((response) => {
  console.log(response); //returns true
});

db.documents.read('/tamas.json').result().then(function(document) {
  var document = document[0];
  console.log('Read ' + document.uri + ' with version ' + document.versionId);
});

db.documents.write({
  uri: '/tamas.json',
  contentType: 'application/json',
  content: {
    person: {
      name: 'Tamas',
      age: 32,
      hobby: 'waterpolo'
    }
  }
}).result()
.then(function(result) {
  console.log(result);
})
.catch(function(error) {
  console.log(error);
});

I'd expect the Error message to be 412 even when I don't provide the versionId. At the moment the error looks like the following:
➜  locking node app.js
{ [Error: write single document: cannot process response with 403 status]
  message: 'write single document: cannot process response with 403 status',
  statusCode: 403,
  body:
   { errorResponse:
      { statusCode: 403,
        status: 'Forbidden',
        messageCode: 'RESTAPI-CONTENTNOVERSION',
        message: 'You do not have permission to this method and URL.' } } }

Updating the above code and adding an incorrect versionId yields the following:
db.documents.write({
  uri: '/tamas.json',
  contentType: 'application/json',
  content: {
    person: {
      name: 'Tamas',
      age: 32,
      hobby: 'waterpolo'
    }
  },
  versionId: 1
}).result()
.then(function(result) {
  console.log(result);
})
.catch(function(error) {
  console.log(error);
});

➜  locking node app.js
{ [Error: write single document: cannot process response with 412 status]
  message: 'write single document: cannot process response with 412 status',
  statusCode: 412,
  body:
   { errorResponse:
      { statusCode: 412,
        status: 'Precondition Failed',
        messageCode: 'RESTAPI-CONTENTWRONGVERSION',
        message: 'RESTAPI-CONTENTWRONGVERSION: (err:FOER0000) Content version mismatch:  uri /tamas.json has current version<PHONE_NUMBER>9530720 that doesn\'t match if-match: 1' } } }

The standards seem to be silent on a missing IF MATCH etag, and common practice seems to prefer the 403.  For instance:
http://stackoverflow.com/questions/16056980/response-code-when-etag-is-expected-but-not-received
The message could certainly be improved for this situation.  That would be a REST API bug instead of a Node.js API bug.

That makes sense @ehennum, but instead of the returned code maybe the error message should be more precise because it's not I don't have permission but more like I didn't provide an actual versionId.

Since is a REST API issue, I'm moving this to Bugtrack an assigning it to @ehennum:
https://bugtrack.marklogic.com/44316


Introduce a dependency extractor abstraction

Summary
This PR changes the dependency ingester to use a generic extractor abstraction. The goal is to make the dependency analysis more pluggable to allow us to easily switch backends. This PR breaks the change into three commits:

09685cf108b90659044ad144bc7807514c962885 introduces a new dependency extractor abstraction
f8249b2c9e0eda8f500b78fa384af2f771601cda creates an extractor implementation with osv-scalibr based on the current ingester
1bd70b92cbc7473efd1ca8dac9518f648d42ec5e removes the scalibr-specific logic from the deps ingester to use the new abstraction  (defaulting to scalibr), the tests are now ported to the new implementation.

Change Type
Mark the type of change your PR introduces:

[ ] Bug fix (resolves an issue without affecting existing features)
[ ] Feature (adds new functionality without breaking changes)
[ ] Breaking change (may impact existing functionalities or require documentation updates)
[ ] Documentation (updates or additions to documentation)
[x] Refactoring or test improvements (no bug fixes or new functionality)

Testing
Outline how the changes were tested, including steps to reproduce and any relevant configurations.
Attach screenshots if helpful.
Review Checklist:

[x] Reviewed my own code for quality and clarity.
[x] Added comments to complex or tricky code sections.
[ ] Updated any affected documentation.
[x] Included tests that validate the fix or feature.
[ ] Checked that related changes are merged.

coverage: 55.122% (-0.009%) from 55.131%
when pulling 1bd70b92cbc7473efd1ca8dac9518f648d42ec5e on puerco:deps-extractor
into<PHONE_NUMBER>76e8ac6c2da65f677bf4b19e0dd096 on mindersec:main.


Possibly wrong initialization in LinearEmbeddings

It seems that in LinearEmbeddings output size (-1 dim) is being used for kaiming, not input size, which is inconsistent with both Pytorch nn Linear initialization (https://pytorch.org/docs/stable/generated/torch.nn.Linear.html) and other similar layers (e. g. NLinear)
https://github.com/Yura52/rtdl/blob/b354b35d68f28b4f5bbebd2e6d5b1f6cfa91eed1/rtdl/nn/_embeddings.py#L275

(just in case, I will mention this warning from README: "Please note that the code in the "main" branch not released to PyPI is unstable and should not be used")
I see the following aspects to this issue:

Did you observe a suboptimal performance on your tasks caused by the current initialization scheme?  What was the initialization scheme that fixed the issue for you?
I am not sure if we there is a direct analogy between LinearEmbeddings and torch.nn.Linear/NLinear. Overall, I should say that the current initialization scheme is not a result of systematic research, but rather a heuristic choice, that, so far, has worked well enough in the papers.

@Yura52
Thank you for the feedback!

No, with the current init I get very good results already. Havent tried other schemes
I was just under the impression that every linear-like layer is initialized like nn.Linear, but on the other thought it doesnt really make sense to do so - you would need to set input_dim as 1 for those layers, which would probably result in too high initialization.

I think that the current init works good, so closing the issue, but in the future the relationship between current init and kaiming in nn.Linear may be worth clarifying in the comments


[boost-json] Fails to build static library

Boost.JSON by default is a compiled library yet boost-json treats it like a header-only target and does not create a libboost_json.a.
While b2 should be capable of producing the library, Boost.JSON is built by a single TU including a src.hpp file which end-users then compile and link against.

Hi,
I've just compiled boost_1_77, but still, libboost_json is not generated.
Are you sure that the fix has been propagated to boost 1_77 ?
cheers

@vynilas Have you tried this PR #19556?

Sounds like I post my comment in the wrong place : I've been compiling on Ubuntu, not Windows.
Hence I guess that the PR#19556 does not apply to my issue ?

Actual master contains version 1.76.0. Update to 1.77.0 hasn't been ready yet.

Thanks a lot Yury.


Animated.Value.addListener not getting callback

I made a demo at https://github.com/cani1see/AnimationDemo
I can't get any callback whether useNativeDriver or not.
https://github.com/cani1see/AnimationDemo/blob/f18418eb545fe5fcb5f631e0c55ca3f7cdfe2970/src/RotateWheel.js#L18
test in android don't know ios
react-native info
React Native Environment Info:
System:
OS: macOS 10.14.3
CPU: (8) x64 Intel(R) Core(TM) i7-4710HQ CPU @ 2.50GHz
Memory: 29.09 MB / 16.00 GB
Shell: 5.7.1 - /usr/local/bin/zsh
Binaries:
Node: 10.16.0 - /usr/local/bin/node
Yarn: 1.17.0 - /usr/local/bin/yarn
npm: 6.9.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.2, macOS 10.14, tvOS 12.2, watchOS 5.2
Android SDK:
API Levels: 15, 16, 17, 19, 21, 22, 23, 24, 25, 26, 27, 28
Build Tools: 19.1.0, 20.0.0, 21.1.2, 22.0.1, 23.0.1, 23.0.2, 23.0.3, 24.0.0, 24.0.1, 24.0.2, 24.0.3, 25.0.0, 25.0.1, 25.0.2, 25.0.3, 26.0.0, 26.0.1, 26.0.2, 26.0.3, 27.0.0, 27.0.3, 28.0.2, 28.0.3
System Images: android-28 | Google Play Intel x86 Atom, android-28 | Google Play Intel x86 Atom_64
IDEs:
Android Studio: 3.4 AI-183.6<IP_ADDRESS>22156
Xcode: 10.2.1/10E1001 - /usr/bin/xcodebuild
npmPackages:
react: 16.8.3 => 16.8.3
react-native: 0.59.8 => 0.59.8
npmGlobalPackages:
create-react-native-app: 0.0.6
react-native-cli: 2.0.1
react-native-git-upgrade: 0.2.7
react-native-macos-cli: 2.0.1

Hello @cani1see, how are you feeling today? I looked at your example and I concluded that this is NOT a react-native bug. You see, at line 23 (https://github.com/cani1see/AnimationDemo/blob/f18418eb545fe5fcb5f631e0c55ca3f7cdfe2970/src/RotateWheel.js#L23) you create a new Animated.Value before starting the animation, which overrides the callback listener register that you did in here https://github.com/cani1see/AnimationDemo/blob/f18418eb545fe5fcb5f631e0c55ca3f7cdfe2970/src/RotateWheel.js#L14
.
You have two options to fix this problem.
At line 23 you could replace the
this.rotateDeg = new Animated.Value(0)

to
this.rotateDeg.setValue(0)

This would lead to the following implementation
  rotateImgDelegate = () => {
    if (!this.state.rotating) {
      this.rotateDeg.setValue(0)
      this.setState({
        rotating: !this.state.rotating,
      }, () => {
        this.rotateImg();
      });
    } else {
      this.rotateToIndex(7)
    }
  };

Or if you really want to create a new Animated.Value you will need to do the following
  rotateImgDelegate = () => {
    if (!this.state.rotating) {
      this.rotateDeg = new Animated.Value(0)
       this.rotateDeg.addListener(this.rotateListener)
      this.setState({
        rotating: !this.state.rotating,
      }, () => {
        this.rotateImg();
      });
    } else {
      this.rotateToIndex(7)
    }
  };

By the way, you need to adjust your rotating state toggle since it needs to be updated using the prevState due to react batched state updates. Please look at https://reactjs.org/docs/react-component.html#setstate for more info.

@cabelitos thank you

you're welcome!


fix(mps-legacy-sync-plugin): fix ModelSyncService initialization

ModelSyncService.<init> was called from within ModelSyncService.<init> when a cloud repository was set (see. CLOUD_REPOS_SYSPROP).

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


希望模板填充支持csv格式的excel

Excel Type

[ ] XLSX
[ ] XLSM
[x] CSV
[ ] OTHER

Upload Excel File
Please attach your issue file by dragging or droppng, selecting or pasting them.
e.g : https://github.com/shps951023/MiniExcel/files/6538107/demo.xlsx
MiniExcel Version
Description
希望模板填充支持csv格式的excel

@ShaoYaoHua
你好，今天处理这个issue
请问为何什么场景需要填充csv


Redact ingored_parameters from CachedResponse.url

#409

Coverage remained the same at 99.497% when pulling 1a6881aa4d44d41fef9338c5b17d8a2cf6be6949 on JWCook:redact-response-url into e0e16ceac849bbbc691bf816b1e66ba952701aae on reclosedev:master.


NSInvalidArgumentException

I'm trying this gem for the first time in my RedPotion app. I've added the gem to the Gemfile, bundled, and ran rake pod:install. I'm pretty sure that I've installed everything correctly.
However, when I run this code:
Notifier = Motion::Blitz
Notifier.show
Notifier.loading

I end up with this error:
Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[NSBundle initWithURL:]: nil URL argument'

What am I doing wrong?

Hey @andrewhavens,
Sorry about the issue you're having with motion-blitz!
I'm guessing that the exception you're seeing is coming from these few lines in the SVProgressHUD source code. It seems like SVProgressHUD can't find it's asset bundle within your application resources. I believe that motion-cocoapods takes care of linking asset bundles for pod installed dependencies to the resources folder.
Are you seeing SVProgressHUD install successfully when you run rake pod:install?

By the way, I think you were right about the pod not being installed correctly. I ran rake newclear and it solved the problem.


app.config.js reportedly not a full replacement for app.json

Build/Submit details page URL
No response
Summary
According to this popular issue, useFrameworks: 'static' cannot be used in app.config.js like it can in app.json.
I haven't tried to replicate this finding because we absolutely require an app.config.js, but thus far a hundred other things I've tried have not resolved the issue reported in that thread, and so I have to imagine the problem is our use of app.config.js instead of app.json.
Can this discrepancy be addressed?
Managed or bare?
Managed
Environment
  expo-env-info 1.2.0 environment info:
    System:
      OS: Linux 6.5 Ubuntu 23.10 23.10 (Mantic Minotaur)
      Shell: 5.9 - /usr/bin/zsh
    Binaries:
      Node: 20.11.0 - ~/.nvm/versions/node/v20.11.0/bin/node
      Yarn: 1.22.21 - ~/.nvm/versions/node/v20.11.0/bin/yarn
      npm: 10.2.4 - ~/.nvm/versions/node/v20.11.0/bin/npm
      Watchman: 4.9.0 - /usr/bin/watchman
    SDKs:
      Android SDK:
        API Levels: 31, 32
        Build Tools: 30.0.3, 31.0.0, 33.0.0, 33.0.1, 34.0.0
        System Images: android-31 | Google APIs Intel x86_64 Atom, android-31 | Google Play Intel x86 Atom_64
    npmPackages:
      expo: ~49.0.21 => 49.0.21
      react-native: ~0.72.5 => 0.72.6
    npmGlobalPackages:
      eas-cli: 7.0.0
      expo-cli: 6.3.10
    Expo Workflow: managed

NOTE: Reported expo-doctor errors have been occurring for the past 6-7 SDK versions and are due to some error on the Expo or its handling of monorepos, not our code. The requiring packages for the flagged problems are the recommended versions of expo packages for our SDK version, eg<EMAIL_ADDRESS>✔ Check Expo config for common issues
✔ Check package.json for common issues
✔ Check dependencies for packages that should not be installed directly
✔ Check for common project setup issues
✔ Check Expo config (app.json/ app.config.js) schema
✔ Check npm/ yarn versions
✔ Check that packages match versions required by installed Expo SDK
✔ Check for legacy global CLI installed locally
✔ Check that native modules do not use incompatible support packages
✖ Check that native modules use compatible support package versions for installed Expo SDK
Detailed check results:
Expected package<EMAIL_ADDRESS>Found invalid:
<EMAIL_ADDRESS>(for more info, run: npm why @expo/config-plugins)
Expected package<EMAIL_ADDRESS>Found invalid:
<EMAIL_ADDRESS>(for more info, run: npm why @expo/metro-config)
Advice: Upgrade dependencies that are using the invalid package versions.
One or more checks failed, indicating possible issues with the project.
Error output

❌  (../../node_modules/react-native/ReactCommon/cxxreact/Instance.cpp:24:10)

  22 | #include <folly/MoveWrapper.h>
  23 | #include <folly/json.h>
> 24 | #include <react/debug/react_native_assert.h>
     |          ^ 'react/debug/react_native_assert.h' file not found
  25 |
  26 | #include <glog/logging.h>
  27 |
› Compiling react-native Pods/React-cxxreact » CxxNativeModule.cpp
› Compiling react-native Pods/React-cxxreact » cxxreact_vers.c
⚠  Script has ambiguous dependencies causing it to run on every build.
   To fix, go to: Xcode » ourproject/ourproject » Build Phases » 'Start Packager'
   Either: Uncheck "Based on dependency analysis", or select output files to trigger the script
⚠  Script has ambiguous dependencies causing it to run on every build.
   To fix, go to: Xcode » ourproject/ourproject » Build Phases » 'Bundle React Native code and images'
   Either: Uncheck "Based on dependency analysis", or select output files to trigger the script
⚠  Script has ambiguous dependencies causing it to run on every build.
   To fix, go to: Xcode » ourproject/ourproject » Build Phases » '[CP-User] [RNFB] Core Configuration'
   Either: Uncheck "Based on dependency analysis", or select output files to trigger the script
▸ ** BUILD FAILED **
▸ The following build commands failed:
▸   CompileC /Users/expo/workingdir/build/packages/mobile/ios/build/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/React-cxxreact.build/Objects-normal/x86_64/Instance.o /Users/expo/workingdir/build/node_modules/react-native/ReactCommon/cxxreact/Instance.cpp normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler (in target 'React-cxxreact' from project 'Pods')
▸ (1 failure)
2024-01-20 16:07:37.517 xcodebuild[4297:14424] DVTCoreDeviceEnabledState: DVTCoreDeviceEnabledState_Disabled set via user default (DVTEnableCoreDevice=disabled)
** BUILD FAILED **
The following build commands failed:
  CompileC /Users/expo/workingdir/build/packages/mobile/ios/build/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/React-cxxreact.build/Objects-normal/x86_64/Instance.o /Users/expo/workingdir/build/node_modules/react-native/ReactCommon/cxxreact/Instance.cpp normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler (in target 'React-cxxreact' from project 'Pods')
(1 failure)
Exit status: 65

Reproducible demo or steps to reproduce from a blank project
N/A

@brentvatne @szdziedzic could you possibly advise on this issue? I examined the code starting from these lines but couldn't identify any reason this might be the case, but have tried (probably) every other solution anyone has ever suggested on the internet. https://github.com/expo/expo/blob/33efd9c7bdc89dccfe8a77d06e6c3e4fd693adde/packages/%40expo/config/src/Config.ts#L211-L229

According to this https://github.com/invertase/react-native-firebase/issues/6332#issuecomment-1833316987, useFrameworks: 'static' cannot be used in app.config.js like it can in app.json.

you can indeed use it with app.config.js. both app.json / app.config.js are evaluated with the npx expo config --type public command, so if the result is the same in both cases you can use whichever config format you like.
the only limitation of the dynamic config is that we can't safely modify the config file itself automatically (eg: to add an eas project id) so we instead tell you what to add to your file.


Recommended subject count

Hello,
Is there any recommended limit to subject count using nat-streaming.
Specifically, we're looking to support 10-20k online users. We wish to have subjects corresponding to changes in their state. We'll it be ok to have a dedicated channel for each user or will it be better to have a single channel routing all users changes and do the filtering on the app level?
Thanks
Chen

@chenmarko this is the issue repo for node-nats-streaming. Your question should go here:
https://github.com/nats-io/nats-streaming-server/issues.
@kozlovic may have additional comments.
A few things to clarify when you move the issue:

Are you only interested in the current user state? - ie the last thing that they updated or do you need the 'log' of all their state changes?

If this is 'online' session, this effectively means that the streaming channels are only used for the session, after the session ends the store will have a lot of stale data. If this case, I question is whether this should be on nats-streaming at all. Likely plain NATS would be better. If anything likely the streaming server should be configured to only hold messages for a specific amount of time.

To add to Alberto's comments, depending on what type of stores you are planning to use, the file store requires several file descriptors per channel, although there is an option to limit the use of opened file descriptors (at the expense of performance).

@chenmarko - I am closing this issue since really it is a general question about NATS Streaming scalability.


Support for Bitbucket

Thanks for the PR. It seems your changes fail some tests Could you look at it?

:tada: This issue has been resolved in version 1.5.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[WIP] transient cow disk image support

This PR adds a new API for so called transient disks. Transient disk is a disk that overlays regular disk image. We can write to such disk without having the changes propagated to the base image. The API for that is a new VolumeSource called TransientVolumeSource that nests supported VolumeSources (indirectly, so only 1 level of transient overlays is supported).
The initial version aims to keep the COW image on the node's disk (not memory), created through separate container and shared with the VM container via path. The image size is not arbitrarily limited, but it does respect any limits imposed by Kubernetes EmptyDir (these are, by default, nil -- meaning that the image can grow arbitrarily large, up to available disk space). Images provided elsewhere (through PVs, separate network volumes etc.) are not in scope of this PR.
API example -- given regular PVC-backed storage:
  volumes:
    - name: pvcvolume
      persistentVolumeClaim:
        claimName: disk-alpine

we are able to overlay that by nesting persistentVolumeClaim under transient key:
  volumes:
    - name: pvcvolume
      transient:
        persistentVolumeClaim:
          claimName: disk-alpine

The main driver for this feature is CI, where we have to avoid "tainting" the base images while still allowing writes to the overlay image.

TODO: see if the qemu-img is needed; it most likely is not and could be replaced by BackingStore within libvirt

Please provide a good description of the change in the PR description / initial comment.

Please provide a good description of the change in the PR description / initial comment.

@mpolednik I think it would be important to know more on the motivations for supporting transient disks (it seems tricky so we should try to understand the story)

@simon3z Done.

@mpolednik I began questioning if our use of the term "transient" here is accurate.
While 'transient' does mean 'short lived',  I've typically heard the term used to describe something that is intermittent... like a 'transient' failure that occasionally appears and is self corrected.
Example: "During a transient failure the database reads are eventually consistent."
With respects to storage, the two terms that appear most common are persistent and ephemeral.  aws and openstack use the term ephemeral when describing storage that does not outlive the lifecycle of a running VM instance.
Example: "We use ephemeral EBS volumes on our EC2 instances because our applications are stateless"

@davidvossel That makes for an interesting conflict with what we already call ephemeral volumes. I don't have hard feeling about the name itself, renaming currentEpehemeral -> persistent and transient -> ephemeral is fine by me (and could be done as a part of this PR).

The main driver for this feature is CI, where we have to avoid "tainting" the base images while still allowing writes to the overlay image.

Thanks @mpolednik!
Can you add few words on where we plan to keep the cow layer (e.g. tmpfs, same PV, additional PV, host disks, etc.) and the considerations/limitations based on that? (e.g. there may be limits on how large the cow layer could grow, etc.)

@simon3z added a paragraph highlighting these details. It's worth noting that since current scope of the PR is CI, we haven't thought of imposing any limitation on the max size or other disk attributes. @fabiand maybe the limits are worth a consideration?

In general I am a little skeptical to add an entirely new feature just for CI for two reasons:

it's hard to mark it as just CI feature, someone will use it (at their own risk) and will bump in limitations creating some noise (issues, questions, etc.)
CI is going to test a case that we don't support instead of testing what we support, the result is that the feature created for CI (with all it usability limitation) ironically could result more tested/stable than the officially supported ones

In the specifics I think that the emptyDir approach is a little bit tricky because it depends on configurations that could vary very much in deployments and solutions (e.g. OpenShift has its own defaults).
Anyway I am not familiar with what specific CI problem is trying to solve (I can just try to guess) so I may not be able to understand the compromises that we're willing to make here.

In general I am a little skeptical to add an entirely new feature just for CI for two reasons:

CI and testing are important (and often the first) users of a project

it's hard to mark it as just CI feature, someone will use it (at their own risk) and will bump in limitations creating some noise (issues, questions, etc.)

If it is also useful outside of the CI context, then it is valuable in my opinion.

CI is going to test a case that we don't support instead of testing what we support, the result is that the feature created for CI (with all its usability limitation) ironically could result more tested/stable than the officially supported ones

CI needs it to test windows installations. I don't want to modify 30 gig images and I don't want to rely on snapshot/clone support of storage at this testing stage (windows support is independent of storage support/features and I don't know when we get what).
Apart from that it is in general useful. I also have a use-cases associated with the cluster auto-scaler. There are two typical use-cases on how one uses cloud images:

one boots a read-only image and it is expected that another disk is mounted (addressed by #694).
one boots a writable image and expects that the base-image will not be modified (addressed here).

An HA-storage solution with its own heavy requirements works too. This provides a features which allows addressing some of these use-cases in a very lightweight fashion which can be useful for a lot of people.
@simon3z I hope that clarifies that.

That makes for an interesting conflict with what we already call ephemeral volumes. I don't have hard feeling about the name itself, renaming currentEpehemeral -> persistent and transient -> ephemeral is fine by me (and could be done as a part of this PR).

@mpolednik where do we already use the term ephemeral volumes in KubeVirt?

@mpolednik where do we already use the term ephemeral volumes in KubeVirt?

@davidvossel We use ephemeral in the user-guide in the context of registry disks. I think we are using it in a consistent way if we use it here too. So +1 for your desire to move to ephemeral.

Ack, I've confused ephemeral disks with ephemeral volumes.

@simon3z added a paragraph highlighting these details. It's worth noting that since current scope of the PR is CI, we haven't thought of imposing any limitation on the max size or other disk attributes. @fabiand maybe the limits are worth a consideration?

@mpolednik Starting without that is perfect for me in this context. I think we can take it into account in the resource section on the pod in the context of the ephemeral-store attribute there. Also #694 will need something like this.  We can tackle this in a common solution later.

We use ephemeral in the user-guide in the context of registry disks. I think we are using it in a consistent way if we use it here too. So +1 for your desire to move to ephemeral.

Excellent. In the user guide, we'll just point out that registry disks are inherently ephemeral in nature, and that other volumes (like PVCs for now) are can be toggled to be ephemeral with writes backed by local storage if desired. I don't think that will be too confusing.

@mpolednik yes - limits would be something that are worth to consider in future. we could combine it with local PVs which can be requested with resources - which mean sthat we also get available space guarantees.

Ran make generate against all commits; current travis error seems to be caused by
Get https://registry-1.docker.io/v2/library/fedora/manifests/27: Get https://auth.docker.io/token?scope=repository%3Alibrary%2Ffedora%3Apull&service=registry.docker.io: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

@mpolednik restarted travis

With directly calling qemu-img from within virt-launcher the code should get much simpler. It can work like the cloud-init code. No extra containers are needed for that.

@mpolednik I think Roman's right. we should be taking the cloud-init approach here.
Take a look at the preStartHook() function in pkg/virt-launcher/virtwrap/manager.go. That should be the entry point for the ephemeral disk logic that generates the qcow2 backing file. You'd just need to loop through the ephemeral volumes in the VM spec there and create the backing files. All the template.go logic with volumes and containers could go away after that.
Originally I liked the way you were using containers and volumes to generate the backing file up front before the VM start flow, but @rmohr pointed out that it's way more complicated and inefficient to take that approach. It also requires shipping another container with KubeVirt that we could avoid.

@mpolednik The new direction you're taking looks like what I was hoping to see.

functests are now added and working (at least locally)

ok to test

@mpolednik travis failes because of #777, working on that.

retest this please

@rmohr on it.

User guide update: https://github.com/kubevirt/user-guide/pull/29


i2p-zero http proxy

always getting destination lease set not found unless using i2pd http proxy

needed to run a new build.
https://github.com/creating2morrow/i2p-zero/releases/edit/v1.21-nevmes

Why is i2p-zero chosen for neveko? Can it work with i2pd instead?

Why is i2p-zero chosen for neveko? Can it work with i2pd instead?

it doesn't matter. i2p-zero is just a wrap. you can use any i2p instance. neveko uses i2p-zero to abstract all i2p tunnel creation away for normal users. power users can configure their own i2p proxy server through advanced settings.
https://github.com/creating2morrow/neveko/issues/22


[Doc] Step invalid for Authenticating and Authorizing REST APIs

https://docs.wso2.com/display/IS540/Authenticating+and+Authorizing+REST+APIs
Step 1 and 2 mention uncommenting few lines in config. the latest pack has given lines already uncommented

Thank you for your contribution!
We are closing this issue since it has not been prioritized for a long time. Chances are that it has already been solved in more recent versions. If not, we will be re-evaluating this when it becomes a priority.


 Has it been tested?

Same concern as JP, what happens if ovs dpdk is enabled, and different values are set for numa/hp settings ?

It seems to me that this PR needs to be closed as its aim was to reorder the interaction of all the NFV features which is now part of another PR.

Closing this PR due to https://github.com/dsp-jetpack/JetPack/pull/81


Import an Excel file based on sheet names from the database

Prerequisites

[x] Have read and understood: https://github.com/Maatwebsite/Laravel-Excel/blob/3.1/.github/SUPPORT.md
[x] Checked if your Laravel Excel version is still supported: https://docs.laravel-excel.com/3.1/getting-started/support.html#supported-versions
[x] Checked that your question isn't already asked before.
[x] Filled in the entire issue template

Versions

PHP version: 7.4.3
Laravel version: 7.20.0
Package version: 3.1

Description
I would like to import the Excel file into my database based on the table sheets. I save the table sheetnames in the database. I need to define the table sheetnames as a string in the import class. Retrieving the sheetnames from the database and looping through them does not work because it breaks after the first return. Does anyone know how to import the Excel file based on the sheetnames in the database? Thanks in advance!

Have you tried the conditional multiple sheets feature? https://docs.laravel-excel.com/3.1/imports/multiple-sheets.html#conditional-sheet-loading

Yes, I did. But then I would still have to list all the table sheets in the Import class first. But I don't want to use hard coded strings but rather variables from the database

You probably should use phpspreadsheet directly first to get the list of sheet names and then feed them to your Laravel Excel export class. I believe there's a getSheetNames method on the spreadsheet class.

Yes, there is. I can use it to list all the worksheets. But I already have them in the database. I want to store each worksheet in the database with an identifier in a column, for example Worksheet 1. But I want to do this using variables from the database and not hard coded strings.

You can query them before calling the export and pass the variables through the constructor.


Borders are too thin, practically invisible

Describe the bug

1.85 changes the border to be less thicker (1px -> hairlineWidth) but it seems to be making borders practically invisible especially on the true black theme variant.

See how weird the rounded borders look here. I think keeping Android to 1px might be the safest bet.
Details

Platform: Android
Platform version: 13
App version: <IP_ADDRESS>; Bundle info: 2285819 (prod); Bundle date: 24060503; Platform: android

Additional context

N/A

Looks similar on iOS, I think it's a pure black dark mode issue. Maybe we just need to up the border contrast on that theme

Hmm I'm not sure if that's the entire story given that zooming around the images I've provided shows that the borders are now displayed inconsistently (sometimes visible, sometimes thinner around edges, sometimes invisible)

Noticed this on web as well where the borders seemingly leave gaps like these.

Fixed here: https://github.com/bluesky-social/social-app/pull/4538


Snabbdom Support

Snabbdom uses a hyper-script-like function to build it's vdoms, but it's second argument is different. Instead of attributes it's properties are used by various "modules";
h('div', {
  props: {title: someString}, // snabbdom/modules/props
  classes: {selected: isSelected}, // snabbdom/modules/class
  on: {click: doSomething}, // snabbdom/modules/eventlisteners
  style: {color: someColor} // snabbdom/modules/style
}, ['children'])

The snabbdom-jsx module handles this using prefixed attributes in JSX:
<div
  title={someString}
  class-selected={isSelected}
  on-click={doSomething}
  style: {({color: someColor})}
>
  children
</div>

Would it be feasible for hyperx to do this as well?

You could create a wrapper around snabbdom's h and pass it to hyperx, so it could recognize prefixed attributes, or make intelligent choices.

Maybe this can help https://www.npmjs.com/package/hyperx-to-snabbdom.

Can this be supported inside hyperx, maybe through special option like concat? Using another module seems like unecessary overhead, and hyperx could be useful for render functions in Vue out od the box (Vue uses snabbdom as vdom library).

@niksy I'd love to, I just wonder, my only concern is how should hyperx deal with snabbdom unique idioms (non existent in virtual dom or morphodom) like hooks?

Ohh, interesting I've found this after creating a module.
I made snabby which is more like yo-yo.
@jbucaran for handling hooks inside this module, I plan to use a snabby.hooks function, e.g.:
snabby.hook(vnode, { ...handles })
// Or
snabby.hook(vnode, handle, fn)

Although I haven't implemented this yet, or even written tests...  It is pretty experimental
Looking for people to collaborate on it, if anyone is interested.

@jamen Here is what I ended up with. Essentially:
} else if ("data-hook-" === key.substr(0, 10)) {
    data.hook[key.substr(10)] = value
}

Good luck with Snabby!

@jbucaran That structure you've got makes sense after I've experimented more.  I'm probably going to have to do something similar.  So let me know if you want me to add you as collaborator on Snabby.

An update on this, I've made snabby support hooks and various other modules, by using an s-* prefix (similar to v-* in vue).
Example:
snabby`
  <div s-hook:destroy=${fn}>
  </div>
`

// Using `eventlisteners`:
snabby`
  <div s-on:click=${...}>
  </div>
`

Open to suggestion on how to make this more nice.


VT100 support

We should add proper VT100 / ANSI code support

I did some testing with a basic C program to see how various non-alphanumeric inputs are encoded:
#include <stdio.h>
#include <stdlib.h>

int main(int argc, char** argv)
{
	system( "/bin/stty raw" );
	while ( 1 ) {
		int input = getc( stdin );
                printf( "Read %d (0x%02x)\r\n", input, input );
		if ( ( input == 3 ) || ( input == EOF ) ) {
			break;
		}
	}
	system( "/bin/stty cooked" );
	return 0;
}

Results (two bytes is a hex byte, single char is ASCII, ESC is 0x1B):

Key
Result

Up Arrow
ESC [ A

Down Arrow
ESC [ B

Right Arrow
ESC [ C

Left Arrow
ESC [ D

Home
ESC [ N

End
ESC [ F

Escape
ESC

Page Up
ESC [ 5 ~

Page Down
ESC [ 6 ~

Insert
ESC [ 2 ~

Delete
ESC [ 3 ~

Backspace
7f

Print Screen
Interpreted by GNOME Desktop

Pause
Ignored

Break
Ignored

Sys Req
Did a print-screen

F1
ESC O P

F2
ESC O Q

F3
ESC O R

F4
ESC O S

F5
ESC [ 1 5 ~

F6
ESC [ 1 7 ~

F7
ESC [ 1 8 ~

F8
ESC [ 1 9 ~

F9
ESC [ 2 0 ~

F10
No effect

F11
Made window full-screen

F12
ESC [ 2 4 ~

Control A
01

Control B
02

Control M
0d

Control Z
1a

Enter
0d


Fix: Tweaks tab dissapearing with hook component

This pull request addresses an issue where the tweaks tab on ApiModal disappears when using a webhook component.

LGTM


Server rendering

This is roughly how we're doing it: https://github.com/justin808/react_server_side_rendering_webpack/tree/redux-on-rails-server


feat: support exec and logs

What type of PR is this?

/kind feature
What does this PR do?

Which issue(s) does this PR fix?

Fixes #247
Special notes for your reviewer:

Does this PR introduce a user-facing change?

support exec and logs

/cc @xyz2277 @hanweisen @wangyizhi1 @duanmengkk

/lgtm

/lgtm

/approve


Error [ERR_REQUIRE_ESM]: require() of ES Module

Hi Team,
I am facing below error when i run "node index.js"
warn: DeprecationWarning: The Parse Server option 'allowClientClassCreation' default will change to 'false' in a future version.
warn: DeprecationWarning: The Parse Server option 'allowExpiredAuthDataToken' default will change to 'false' in a future version.
warn: DeprecationWarning: The Parse Server option 'encodeParseObjectInCloudFunction' default will change to 'true' in a future version.
Error [ERR_REQUIRE_ESM]: require() of ES Module /home/farhan/parse-server-example/cloud/main.js from /home/farhan/parse-server-example/node_modules/parse-server/lib/ParseServer.js not supported.
main.js is treated as an ES module file as it is a .js file whose nearest parent package.json contains "type": "module" which declares all .js files in that package scope as ES modules.
Instead rename main.js to end in .cjs, change the requiring code to use dynamic import() which is available in all CommonJS modules, or change "type": "module" to "type": "commonjs" in /home/farhan/parse-server-example/package.json to treat all .js files as CommonJS (using .mjs for all ES modules instead).
at ParseServer.start (/home/farhan/parse-server-example/node_modules/parse-server/lib/ParseServer.js:146:13)
at async file:///home/farhan/parse-server-example/index.js:36:3 {

code: 'ERR_REQUIRE_ESM'
}
/home/farhan/parse-server-example/node_modules/parse-server/lib/ParseServer.js:146
require(path.resolve(process.cwd(), cloud));
^
Error [ERR_REQUIRE_ESM]: require() of ES Module /home/farhan/parse-server-example/cloud/main.js from /home/farhan/parse-server-example/node_modules/parse-server/lib/ParseServer.js not supported.
main.js is treated as an ES module file as it is a .js file whose nearest parent package.json contains "type": "module" which declares all .js files in that package scope as ES modules.
Instead rename main.js to end in .cjs, change the requiring code to use dynamic import() which is available in all CommonJS modules, or change "type": "module" to "type": "commonjs" in /home/farhan/parse-server-example/package.json to treat all .js files as CommonJS (using .mjs for all ES modules instead).
at ParseServer.start (/home/farhan/parse-server-example/node_modules/parse-server/lib/ParseServer.js:146:13)
at async file:///home/farhan/parse-server-example/index.js:36:3 {

code: 'ERR_REQUIRE_ESM'
}

@mtrezza Looks like cloud folder is dynamically imported
https://github.com/parse-community/parse-server/blob/alpha/src/ParseServer.js#L187

Is that an example repo issue or a parse server issue?

@mtrezza You reopened an issue for this https://github.com/parse-community/parse-server/issues/7559

I faced this issue and I was able to resolve it by following this comment https://github.com/parse-community/parse-server/issues/7559#issuecomment-2402720234
Hope this can help you :)


Add Article for Hello World in Crystal

Merged #56. Now, let's write an article.

Finished the article. Updating the README.

Added the link!


deprecate NIF-GrossAnatomy

add deprecated true to classes
port proper_part_of, has_proper_part to an uberon bridge
check if any synonyms need to be ported to the bridge
create an FMA slim to support the cortical partonomy for Russ OR see if we can map the FMA identifiers to uberon identifiers via xrefs and recreate the cortical partonomy on uberon identifiers in the bridge mentioned in 2.

make sure all deprecated nif terms have a 'replacedBy' pointing to uberon

deal with NIFGA:UBERON_* identifiers, and move them to a proper bridge where they are local assertions on remote identifiers rather than forks... yes the uberon-bridge sort of fixes this, but talk about inducing madness....

All done but the FMA slim.

Closing and adding new issue for FMA slim.


FIRCLSExceptionRecordNSException v.s. raise it

It seems like FIRCLSExceptionRecordNSException is not a public api? Wondering why not just raise the NSException.

Yeah, correct, it isn't part of the public API.
The main reason why we don't raise exceptions is that we don't want to interrupt the existing flow.
If we were to raise an exception, any existing unhandeled exception hooks wouldn't be called anymore.

Does FIRCLSExceptionRecordNSException be called explicitly when an exception triggered/raised in a pure iOS project without KMP? I want to follow the same flow.