frank could not launch simulator after update xcode to 5.1

Just update xcode to 5.1, after that unable to launch the simulator.
Details:
Frank Launch.
LAUNCHING APP...
sh: line 1: 44406 Trace/BPT trap: 5       /Library/Ruby/Gems/1.8/gems/sim_launcher-0.4.6/lib/sim_launcher/../../native/ios-sim "showsdks" 2>&1
sh: line 1: 44409 Trace/BPT trap: 5       /Library/Ruby/Gems/1.8/gems/sim_launcher-0.4.6/lib/sim_launcher/../../native/ios-sim "launch" "/Users/royt/practice/temp/Frank/frankified_build/Frankified.app" "--sdk" "" "--family" "iphone" "--exit" 2>&1
I believe this was caused by xcode 5.1, any change I could make on the Frank side to solve this problem? Thanks

Tried couple of things, no luck. Still running into same issue.
Updated the sim_launcher (0.5.0) but later it conflicts with frank build
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/dependency.rb:296:in `to_specs': Could not find 'sim_launcher' (~> 0.4.6) - did find: sim_launcher-0.5.0
Updated frank to latest, thinking it will refer latest sim_launcher. But it doesn't seem to be the case.
I have  xcode v7.2 installed.
Would be great if someone can look at it and fix the issue at the earliest.
Regards,
Vijay

Looks like with brew install ios-sim, above issue is fixed. Able to launch the app using frank now.
brew install ios-sim

Still seeing this issue in a fresh RubyMotion app
* CFPropertyList (2.3.4)
* activesupport (5.0.1)
* builder (3.2.3)
* bundler (1.13.6)
* claide (1.0.1)
* colored (1.2)
* concurrent-ruby (1.0.4)
* cucumber (2.4.0)
* cucumber-core (1.5.0)
* cucumber-wire (0.0.1)
* diff-lcs (1.3)
* dnssd (3.0.1)
* frank-cucumber (1.2.2)
* gherkin (4.0.0)
* i18n (0.7.0)
* json (2.0.3)
* minitest (5.10.1)
* motion-frank (<IP_ADDRESS>)
* multi_json (1.12.1)
* multi_test (0.1.2)
* nanaimo (0.2.3)
* plist (3.2.0)
* rack (1.6.5)
* rack-protection (1.5.3)
* rake (12.0.0)
* rspec (3.5.0)
* rspec-core (3.5.4)
* rspec-expectations (3.5.0)
* rspec-mocks (3.5.0)
* rspec-support (3.5.0)
* sim_launcher (0.5.0)
* sinatra (1.4.7)
* thor (0.19.4)
* thread_safe (0.3.5)
* tilt (2.0.5)
* tzinfo (1.2.2)
* xcodeproj (1.4.2)

I've updated brew install ios-sim, but still no luck.


Add a nested option on handler config definition

Q
A

Bug fix?
no

New feature?
yes

BC breaks?
no

Deprecations?
no

Tests pass?
yes

Fixed tickets

License
MIT

Doc PR

Marked nested handlers with not be pushed to the logger handler array.
This options may be usefull when using custom handler (as service type handlers) which rely on a sub handler defined in the monolog-bundle configuration.
Marking this subhandler as nested avoid monolog to directly call it.
Sample Usage
monolog:
    handlers:
        foo:
            type: service
            id: my_site.custom_log_handler
        bar:
            type:  stream
            path:  "%kernel.logs_dir%/%kernel.environment%-bar.log"
            level: debug
            nested: true

services:
    my_site.custom_log_handler:
        class: AppBundle\Logger\CustomHandler
        arguments:
            -<EMAIL_ADDRESS>

May i've missed something or this PR didn't interested you?

No it looks good to me, I just missed it :)

no problem. thanks a lot for your work !


Colours on Slack messages can't be discerned by colour-blind users

These look almost identical to me:

I'm not sure exactly what a better solution would be, though. Maybe bolder for the failed job? A more obvious cue like 'FAIL' or 'SUCCESS'?

Good call, perhaps an option for customizing the color will help resolve this.

consider aligning with Jenkins color scheme (blue and red works just fine for most color-blind people).

@ceralena What about prefixes:

SUCCESS
FAILURE

The prefixes would help, but I think @samrocketman's suggestion of red and blue would have the most impact.

Correction, blue/red suggested by @nicorikken.  Which I agree is a great suggestion.  Perhaps configurable with a default of blue/red.

I would vote for including hints in the text but keeping the default colours the same (reg/green). We do get notifications from other systems as well and all of them are using the same semaphore colours.
Making the Failure bold should be enough.

Apparently the predefined message colors are based on the predefined colors in Slack: https://api.slack.com/docs/message-attachments#color
As GitHub integration is also using its own coloring scheme for Slack messages, it seems fair to me to use the Jenkins color scheme. Unless Slack gets its act together on this issue, keeping a high level of accessibility for Jenkins seems a worthy goal to me. So blue/red and maybe grey. Right?
Then I think a basic case handling in https://github.com/jenkinsci/slack-plugin/blob/master/src/main/java/jenkins/plugins/slack/StandardSlackService.java would do.

Closing this issue as it is stale,
Feel free to send a PR adding the colours to the global configuration as configurable if this is still wanted.
Otherwise you have full control in pipeline


Cmdlet and RestApi page support for file listing in data sync page

@tianlong12
After fixing ##1329,  you can add more complex methods in CmdletManager and ActionRestApi to enable data sync page feature in backend. Both Classes are the kernel modules of SSM.
Two methods should be modified:

CmdletManager.getFileActions
In current version, we return List<DetailedActionInfo>, but that's not enough. Modify this method according to listActions, and return ActionGroup.

ActionRestApi.actionFileList
Modify actionFileList according to actionList.

If you finished all these methods, please contact @zhiqiangx for integration test. Zhiqiang will replace old restful API calls in WebUI.

Already done. Issue closed.
Thanks @tianlong12 .


Powershell core does not sort versions with letters correctly (e.g. 80.0b1), while powershell classic does

I've noticed recently I could not update the firefox-beta app from the extras bucket from powershell core (7.0.3) anymore, while powershell "classic" does work.
Powershell Classic:
$ scoop status
Scoop is up to date.                                                                                Updates are available for:
    firefox-beta: 80.0b5 -> 80.0b6
    imagemagick: 7.0.10-26 -> 7.0.10-27
    vim-nightly: 8.2.1399 -> 8.2.1412
Everything is ok!

If I do this in Powershell Core 7.0.3, I get:
$ scoop status
Scoop is up to date.
Updates are available for:
    imagemagick: 7.0.10-26 -> 7.0.10-27
    vim-nightly: 8.2.1399 -> 8.2.1412
Everything is ok!

Notice how firefox-beta is missing from the list.
I pinned it down to the version comparison/sorting not working correctly.
I have populated an array with the firefox-beta versions on my system:
$ Write-Output $versions
79.0b7
79.0b8
79.0b9
80.0b1
80.0b2
80.0b3
80.0b4
80.0b5

If I use scoop's "sort_versions" function inside classic powershell, I get:
$ sort_versions($versions)
79.0b7
79.0b8
79.0b9
80.0b1
80.0b2
80.0b3
80.0b4
80.0b5

However, if I use the same function in powershell core 7.0.3, I get a wrong result:
$ sort_versions($versions)
79.0b7
79.0b8
79.0b9
80.0b2
80.0b3
80.0b4
80.0b5
80.0b1

See https://github.com/lukesampson/scoop/issues/3812#issuecomment-569715241


[Feature]: Add mmdet2torchserve tool

This P.R. enables serving MMDetection models with TorchServe. A new section Model Serving has been added in useful_tools.md.
Closes #4661

Hi @daavoo ,
Overall, this PR LGTM and torchserve will definitely a good feature for mmdet. Let's see whether @hellock has any suggestions.

Hi, @daavoo Does the writing in Dockerfile require a specific version of docker?  My Docker version is 18.01.0-ce, the following error occurred:
Error response from daemon: Dockerfile parse error line 43: Unknown flag: mount

Hi, @daavoo Does the writing in Dockerfile require a specific version of docker? My Docker version is 18.01.0-ce, the following error occurred:
Error response from daemon: Dockerfile parse error line 43: Unknown flag: mount

Hi @hhaAndroid , it actually requires 18.09 or higher:
https://docs.docker.com/engine/reference/builder/#buildkit
We can maybe change the syntax to support lower versions?

OK, It's best to be compatible. Thank you

I found some small errors, you can also fix them together：

add mmcv.mkdir_or_exist(output_folder)
https://github.com/open-mmlab/mmdetection/blob/master/tools/deployment/mmdet2torchserve.py#L44

--output_folder -> --output-folder
https://github.com/open-mmlab/mmdetection/blob/master/docs/useful_tools.md#1-convert-model-from-mmdetection-to-torchserve


--consolelogs not working with Genymotion emulators

ionic cordova run android -lc works on a real device, but not on a Genymotion emulator. No logs in the console.

Hello @shawnlan , as this is most likely an issue with the Genymotion emulator and not app-scripts, I am going to close this issue for now. Also, i would recommend updating to the latest version of Android studio and giving the official android emulator a try. It has been GREATLY improved over the last year and a half.


Disable logging for QtWebEngine

📒 Description
This should help with log flooding in case of Snapcraft uninstall. I haven't actually tested this yet, personally, as I don't have a working Snapcraft configuration on my computer at this moment (can't download an Ubuntu image using multipass while running snapcraft)
🕶 Types of changes

Bug fix (non-breaking change which fixes an issue)

🤯 List of changes

Logging is now disabled for QtWebEngine

👫 Relationships
Closes #2941
🔎 Review hints
While TogglDesktop installed using Snap is running, uninstall it. Without this patch, you should notice the process logging huge amounts of error messages in your system log. With this patch, it should not log anything.

Seems to be nonbreaking commit, so let's just merge it.


Where is Uchuu Engineer?

If I remember correctly, the Steins;Gate PSP have 2 opening(or 1) and one of them is Uchuu Engineer, the other: Skyclad no Kansokusha. Could you tell me when will you translate and implemented it into this translation
P.S: Sorry for my broken English(in advance)

Hey! I know there might be some misunderstanding over which openings I have used, let me clear this up.
There are three openings in the PSP version:

OPEN.PMF - which is the Skyclad Observer OP. It is using these subtitles from the same opening on the PC.
OPEN2.PMF - which is the A. R. OP. It is using these subtitles from the same opening on PC.
OPEN3.PMF - which is the Space Engineer OP. However, this one does not have an equivalent on the PC, as such I don't have any subtitles available. This OP was replaced by the Hisenkei Geniac OP with these subtitles.

While I can say that Space Engineer is an amazing OP, I unfortunately have no plans on making the subtitles for it. The reason it was replaced by the Hisenkei Geniac OP is primarily because I wanted to avoid making my own subtitles (instead I've used the ones Committee Of Zero has publicly available, with proper credits). I hope this answers your question.

Well...thank you. But could the Space Engineer be unlock in the normal,
unpatched psp version?
Vào Th 5, 22 thg 7, 2021 vào lúc 10:07 Yaroslav Mikhaylik <
@.***> đã viết:

Closed #13
https://github.com/HaselLoyance/steins-gate-psp-patch/issues/13.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/HaselLoyance/steins-gate-psp-patch/issues/13#event-5053404406,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AU2FQX43V6T5JO33SR4OOA3TY6DOJANCNFSM5AG2RP3Q
.

You don't even need to unlock it. If you start the unpatched game and wait ~20s at the title screen without pressing any of the buttons then one of three openings will play randomly. As far as I know, this is actually the only way to see OPEN3 in the entire game.


get_query_set method should be renamed get_queryset

Warning on running server:
site-packages/django/forms/widgets.py:143: RemovedInDjango18Warning: FluentCommentsAdmin.queryset method should be renamed get_queryset.
.new(mcs, name, bases, attrs))
site-packages/django/forms/widgets.py:143: RemovedInDjango18Warning: FluentCommentsAdmin.queryset method should be renamed get_queryset.
.new(mcs, name, bases, attrs))

Closing since #53 got merged!


several code errors

Could you please explain what happening, looks like some errors in the code.
ffmpeg was installed (but it would be great if the would be a more detailed instruction how to do that to save time for users/ anyway)
ffmpeg installed and seen in cmd. extension installed but there still errors.

Hi,
This error seems to indicate that no face was detected in one of the images. Does that sound possible in your situation?

Hello
I think not cause the vidie is good quality and all clear seen there.
Ill try to with other video ald reply here a bit later.

Same story. the soft starts workin but at some point it just give an error.
The video was clear.
Also just to make it clear. Any video can be added? video shoul be without audio? I meen as the audio shoul be added separately does it means that the video shhoul be without audio?
Also coul it be because of ffmpeg? I installed it but not sure is it there I mean how  to check it? How ever the errors are not about the ffmpeg so it means that the problem is not about ffmpeg
Any way errors are still there.

thanks for report,
your last error is "face not detect..." that mean there is an image in the video sequence where face  too poor quality  or bad angle, or ...
you can find the bad image in :
"c:\Users\user\stable-diffusion-webui\extensions\sd-wav2lip-uhq\scripts\wav2lip\temp\faulty_frame.jpg"


Add a remove credentials command

I put them in wrong, and now have to do keychain hacking.

This has been fixed by not storing credentials anymore. I believe existing fastlane credentials are still being used, though. Maybe @KrauseFx wants to shed some light on how Spaceship works now? For reference, this is the code: https://github.com/neonichu/xcode-install/blob/master/lib/xcode/install.rb#L144


Mm/ng prototype - open PR to keep track of changes [do not merge]

work on this will continue at /bobanetwork


Include hplip

Describe the package
hplip requires write access to some directories that are read only. They don't provide an rpm installer though so I don't think we can use rpm os-tree.
https://developers.hp.com/hp-linux-imaging-and-printing/gethplip
Is there a method to install packages like this? We can extract the drivers, but I wanted to ask if this is even something we should consider.
Image
All Images

Not sure if this will pull in libsane-hpaio but we can pull that in if we need it.


Lyrics sources (with parse support)

[x] netease
[x] #59
[ ] kgmusic
[ ] kwmusic
[ ] mgmusic
[ ] musicxmatch

https://docs.rs/musixmatch


⚠ SceneTime has degraded performance

In 51a8cb0, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 1298 ms

Resolved: SceneTime performance has improved in f343522 after 14 minutes.


Add one_email_per_occurrence option and migration task

Motivation:
We are happily using Solid Errors in our production app but because that app connects to some external APIs we can run into situations where we are sent a lot of emails for the same error's reoccurrence.
Details:
Introduced a new configuration option one_email_per_occurrence that serves to limit email notifications to one per occurrence. If an error is resolved but reoccurs, an email will be sent, again, for that first reoccurrence.
In order to do this, a migration was created to add a new column/attribute to the solid_errors table called prev_resolved_at.
This column/attribute is updated to match the resolved_at value whenever it is set - but it is never nill'ed out like resolved_at is when the issue is resolved.
A Rake task, solid_errors:install_migrations, was also added to copy any new migrations from the lib/solid_errors/db/migrate directory and then immediately run them.
The README was updated as was the error controller to support the new feature.
The .gemspec was also updated to add a note reminding users to ensure they've run the task to copy over the migration(s).
Please let me know if there's anything you'd change, do better, etc. Thank you for your excellent work on Solid Errors. We are grateful to have it!

I like this! Thanks for such a clear and thorough PR. I've made a few comments for things to tweak to get it over the line.

Thank you so much for taking the time to review this and to add all your helpful edits and comments. Much much appreciated!
I am not sure if you need me to/if I should make some commits in my branch and redo my PR (this is my first PR to a gem so please forgive any stupidity or missteps on my part!).
Thanks, again, so much for your work. Please know how much my team appreciates Solid Errors!

AWESOME! Man, really appreciate it. I will make the changes and commit them shortly

For the prev_resolved_at. I just made a commit that might be a better way? Let me know your thoughts. Basically, I removed that element from the buttons in the _action and _row view files as well as the controller. Instead, I set it in the Subscriber just before the resolved_at value is nilled out.
Maybe less intrusive and more seamless?
Totally open to other alternatives of course!
Finally, for the migration, I just kept the rake task the same in terms of copying the migration files over. But, I killed the running of them (I have some commented out code as an alternative approach to run just the specific migration if desired) because Rails will, of course, scream and yell at us that we have pending migrations to run ... duh on my part 🤣

We still need a note in the README explaining the behavior for email sending

We still need a note in the README explaining the behavior for email sending

Just pushed a commit with an edited note about sending emails. Let me know if you think that fits the bill or needs some added massaging, etc.

I know we are taking a while polishing the final exacting details, but we are close and this is a great PR. Thanks for the patience

I know we are taking a while polishing the final exacting details, but we are close and this is a great PR. Thanks for the patience

Happy to! I like getting things polished and as close to ideal as possible. No problems at all on my end!  Time to go walk and feed the pups!

Ok, Stephen, I think I got that last round of changes in place. Thanks for catching the spelling error(s) 🤦🏻
Let me know how that README line sounds about the post-install message, etc. Or any other changes you find need made. Thanks!

I want to chat with @bensheldon some about how he manages versions with schema changes before merging and releasing. I want a clear plan.

👋🏻 Happy to chat. I can try to sketch out a few things (I've been wanting to blog about this forever!) and maybe invite further chatting.
Upfront: GoodJob does a lot of migrations. A lot! I want to say there have been about 30 migration files over its lifespan so far. That's more than like Active Storage which has... 4. So take this with a grain of salt if your gem is more like Active Storage than GoodJob.

Required database migrations are breaking changes, so that means if I make a breaking change it warrants a major version release. I try very hard not to allow a database migration to be required.
It takes more work to make migrations (or more importantly, their absence) non-breaking and optional. This largely means doing schema checks (does this column exist? if so, then do x, if not, then don't), and writing fairly defensive code (e.g. constructing attribute hashes and array accessors for Active Record models instead of using accessor methods)
I make sure that the migrations themselves are idempotent

The first time developer rails g good_job:install command installs a single migration that should get the developer the most up-to-date schema.
The rails g good_job:update which installs all the update migrations (which could be several) for the current major version. This one gets a little weird because some of the migrations must be noops if they did the former first-time good_job::install migration. So I add a schema check to make them noops. The Rails generator command will detect duplicate migrations based on the name, so it is idempotent.

When I do release a major version, I squash down all of the "update" migrations. I do this because I would not be happy, as a first-time user of GoodJob, to immediately be confronted with 30 migrations. The downside of this is that people will upgrade to a major version without applying all the previous major version's migrations and then ask why GoodJob is broken (this is why I do x.99 releases to try to be explicit about the upgrade path). I get many support issues on this when I cut a major release.
I have a whole set of generator tests that create a new Rails app and validate that the install and upgrade migrations are in sync. It's very slow but has saved my bacon a lot.

Sorry, that's a wall of text 😅

I pushed a small update (well, two) yesterday evening. These two ensure that, in the current approach to the migration, it does copy over correctly.
Note: I did bump the version on this branch (<IP_ADDRESS>) so I could ensure that my bundle update grabbed the newest code. That can, of course, be reverted any time.
Let me know, please, if you have any thoughts or approaches you'd like for this PR's final push. Thanks!


Modified default vanta colors

Modified the animation colors to avoid colors like white and golden

I was hoping for seeing this working! LFG!! Thank u so much for the contribution 😁


[Question]: Connect to ssh

Is your question not already answered in the FAQ?

[X] I made sure the question is not listed in the FAQ.

Is this a general question and not a technical issue?

[X] I am sure my question is not about a technical issue.

Question
I installed the ssh server on the windows, I also changed the windows ssh port, so that it is not the same as the linux one.
But, I can't connect to ssh.
Is there any way to do it?

i need a way to run automation on the windwos vm. can we connect by ssh ? any other way to run automation on the windows vm ?  i can create a ssh server on the windows vm but, i can access the windows ip , <IP_ADDRESS> . can someone guide me how i could access the ssh server ?


device-availability feature support

First of all Stanislav, how are you doing during this awful war? Are you healthy with you and your family?
Feature request description
Enables the view of offline zigbee devices in domoticz.
Koekk added a device-availability optional feature a while ago. If activated zigbee2mqtt checks if devices are available. When a device is not online a payload offline will be published to /device-xxx/availability.
Example:
State "Offline" of the device, instead of the last-known state.
Feature definition
Set domoticz state to Offline when a availability payload offline is received and set state back to the state back to the current state when a availability online payload is received.
zigbee2mqtt log:
info  2022-05-02 11:04:02: MQTT publish: topic 'zigbee2mqtt/Hue-4/availability', payload 'offline'
info  2022-05-02 11:25:26: MQTT publish: topic 'zigbee2mqtt/Hue-4/availability', payload 'online'

@jpveen do you have any examples of such "Offline" state in other Domoticz plugins/devices, I'm not sure that Domoticz really supports that

Hi, from what I have found domoticz has around 20 device statusses, but not a specific Offline status. But you could probable use the STOP nvalue 19 for that.
So it would be very helpfulm if the z2m plugin could send a nvalue=19 to domoticz when a availability payload offline is received for a device. No need to handle the 'online' payload, as when a device gets online the plugin already triggers a state change.
Thx!


Error when i test

hi sir
when i test my own  620*420 jpg,the flowing error occur,do you know how can i resolve the error?

This is probably because x and v have different sizes during decoding. Before taking x or v as input to the function window_partition, we usually need to pad them. But the process of padding x or v is based on the size of x, the size of v may get wrong after padding. U can change the padding process(it's in the Class CRFBlock) so that the size of padded v get the same size of the padded x.


Scrolling necessary in modals even in Full HD

When editing a motion, etc. in a modal, the modal is often enough higher than the screen and there is no scrollbar. My screen is Full HD and I'm using OpenSlides 2.3.

Cannot reproduce. Tested on current firefox and current chrome.
What browser are you using?

I'm using current firefox, but I have a slightly smaller window. Besides the taskbar at the bottom of my screen, I have the menu bar displayed in my browser, the tabs, the adress bar and a bookmarks bar, so my usable screen area is 933px high.

I am curious if there will ever be a 2.3.1, since the milestone got removed.
was something planned there @emanuelschuetze?

There is no 2.3.1 milestone any more. We currently develop 3.x only. This issue can be closed.


JRTB-3: Implement Command pattern for telegrambot

Implement Command pattern for telegrambot.
Acceptance criteria:

/start stub command added

added in #15 pull-request


Remove untranslatable on_date key

Follows #23988
Closes #24074 by removing this key

GitHub's relative-time elements allow us to force their rendering to auto, past, or future tense. We will never show an absolute date on ... in TimeSince
Before

After

I think the commit dates look better this way, GitHub also does this

I made some changes, you can test it with: http://localhost:3000/devtest/gitea-ui

Why from now? Drop duration, stick with tense=future

It's the old translation. I do not think "Drop duration, stick with tense=future" works, you could try and share your screenshot.

diff --git a/modules/timeutil/since.go b/modules/timeutil/since.go
index 4c292da32..e6a2519d2 100644
--- a/modules/timeutil/since.go
+++ b/modules/timeutil/since.go
@@ -121,15 +121,12 @@ func timeSinceUnix(then, now time.Time, lang translation.Locale) template.HTML {
        attrs := `tense="past"`
        isFuture := now.Before(then)
        if isFuture {
-               attrs = `format="duration" tense="future"`
+               attrs = `tense="future"`
        }

        // declare data-tooltip-content attribute to switch from "title" tooltip to "tippy" tooltip
        htm := fmt.Sprintf(`<relative-time class="time-since" prefix="" %s datetime="%s" data-tooltip-content data-tooltip-interactive="true">%s</relative-time>`,
                attrs, then.Format(time.RFC3339), friendlyText)
-       if isFuture {
-               return template.HTML(lang.Tr("tool.from_now", htm))
-       }
        return template.HTML(htm)
 }

I think it's better

Oh you are right, I made a mistake during my test.

If you want to remove the on_date, we also need to fix this page, after the fix:

So the only problem with this approach is we will not have on DATE on far-off dates. @silverwind is that a blocker for you?

So the only problem with this approach is we will not have on DATE on far-off dates.

How "far"? The default threshold is P30D, my test include one year.

Today 4 years ago would appear as 4 years ago, but on issue list page GitHub shows on April 4, 2023 by letting tense be auto

b130c9ed24cd552ac2c398d348dbc5e35861df3a crashes?
failed to render template: package/view, error: template error: builtin(static):package/view:89:81 : executing "package/view" at <.CreatedUnix.FormatDate>: wrong number of args for FormatDate: want 0 got 1
----------------------------------------------------------------------
									{{template "shared/datetime/short" .CreatedUnix.FormatDate .CreatedUnix.FormatDate}}
									                                                                       ^
----------------------------------------------------------------------

Today 4 years ago would appear as 4 years ago, but on issue list page GitHub shows on April 4, 2023 by letting tense be auto

I have a plan for that, if it is necessary, we can let callers do: ``{TimeSince .time (dict "prefix" "on" "tense" "past")}}`
And leave the i18n problem to the future.

Good enough now, we can translation the "on %s" on our side now.

No, on is not translatable. I prefer the previous commit

No, on is not translatable. I prefer the previous commit

Single on is not, but now it is (for most language), it's better than before.

I don't like it. I think TimeSince should always be relative (like it was before) and if some one wants absolute time it should be relative-time with format="datetime". If we decide to do on we should use ``format="datetime"`

I don't like it. I think TimeSince should always be relative (like it was before) and if some one wants absolute time it should be relative-time with format="datetime". If we decide to do on we should use ``format="datetime"`

But it really doesn't matter, no code uses it yet. It's just here to help the issue list (in case).

I prefer to not have that key. Leave it per use (e.g. "joined_on" user profile)

OK, reverted.

Would re-introduce later either on %s or whole sentence translation where it makes sense.


Made changing transform impossible for children of Containers.

Made changing transform impossible for children of Containers and added a warning stating:
Cannot change transform of children of Containers.
Fixes #20750 and all issues referenced in it.

@groud I just did what reduz suggested in #22317. I could make the nodes not selectable if you want

Basically, I would expect that children of containers behave like locked nodes (but for the icon display)
What I would do is creating a new function called somehow _is_canvas_item_editable
which would check if the node is locked or if it is a control child of container. Then replace wherever it is pertinent, the test for locked nodes by a call to this function.


Improve ReaderInputStream documentation

Resolves:

https://issues.apache.org/jira/browse/IO-713
https://issues.apache.org/jira/browse/IO-715

Please let me know if you want anything changed, or if I should split this pull request.

@Marcono1234 Do not change @link to @code.

Not even when referring to the class itself ({@link ReaderInputStream })?
To me it appears that this does not add any value; when you are already reading the documentation of ReaderInputStream you don't want to open its documentation again.
See also https://www.oracle.com/technical-resources/articles/java/javadoc-tool.html#inlinelinks (in case you have not noticed it in the commit message); though it might be slightly dated.

Not even when referring to the class itself ({@link ReaderInputStream })? To me it appears that this does not add any value; when you are already reading the documentation of ReaderInputStream you don't want to open its documentation again.

To me, the value is that you get a shortcut to the class comment.

See also https://www.oracle.com/technical-resources/articles/java/javadoc-tool.html#inlinelinks (in case you have not noticed it in the commit message); though it might be slightly dated.

Obviously dated indeed since this document talks about old style HTML links which were underlined, and which Javadoc no longer generates. You'll notice on our Javadoc pages, the hyperlink coloring is rather (IMO) subtle and no longer the harsh bright blue with underline style from the Web 1.0 days.

Ok, I have omitted the changes to replace {@link ...}.
Linking to the class itself could also cause confusion because you might be wondering why there is a link (e.g. is that a different class and have I misread its name?, is this linking to a specific subsection?), but your point makes sense as well.

Also unrelated to this, but it looks like many of your commits use an incorrect (?) e-mail address, for example https://github.com/apache/commons-io/commit/8f7a6430d535b0227fc25cb917af94b9339c3b19.patch<EMAIL_ADDRESS>(the first y is missing).
If you actually own that e-mail address as well, it might make sense to add it to your GitHub profile to get the commits attributed to you.

You have 2 PRs with same title, this is confusing and wasted reviewers' time. Please pick one and close the other.

Can I resolve the corresponding Jira issues (IO-713 and IO-715) now, or do you want to do that? (in case there is anything to consider when resolving them)

Thanks a lot for merging the changes!
Can I resolve the corresponding Jira issues (IO-713 and IO-715) now, or do you want to do that? (in case there is anything to consider when resolving them)

Feel free to close them. Thank you!


feat: add transaction entity to store payment information

Closes #31
Description
Add Transaction entity to store payment information and update the seeder file.
Current Tasks

[x]  Create Transaction table in schema.prisma
[ ]  Seed Course, Subscription, & Transaction data in seed.ts
[ ] Write integration tests (using Jest) to verify data integrity of the seed script (depends on Configure Jest #33)

@guntoroyk, could you please let me know what's your NodeJS & NPM versions?
I'm trying to debug the package-lock.json issue at the moment and finding a solution that works for all contributors.
Thanks! 🙏

@guntoroyk, could you please let me know what's your NodeJS & NPM versions? I'm trying to debug the package-lock.json issue at the moment and finding a solution that works for all contributors. Thanks! 🙏

I'm using NodeJS version v14.17.3 and NPM version 6.14.13

@guntoroyk, could you please let me know what your NodeJS & NPM versions are? I'm trying to debug the package-lock.json issue at the moment and finding a solution that works for all contributors. Thanks! 🙏

I'm using NodeJS version v14.17.3 and NPM version 6.14.13.

I see. That's the root cause of the issue. I just fixed it recently at #62.
To fix the package-lock.json in this PR, please upgrade your NodeJS version into version 16. You can do so easily by using Volta. After that, please reset the package-lock.json file into the current version in the main branch.
If you need some help to do it, please let me know. I can help you with the package-lock.json issue like what I did in #34 just now.
In the meantime, you can also try to resolve my other comments regarding the ids in the seed.ts file. Thanks! 🙏

@guntoroyk, could you please let me know what your NodeJS & NPM versions are? I'm trying to debug the package-lock.json issue at the moment and finding a solution that works for all contributors. Thanks! 🙏

I'm using NodeJS version v14.17.3 and NPM version 6.14.13.

I see. That's the root cause of the issue. I just fixed it recently at #62. To fix the package-lock.json in this PR, please upgrade your NodeJS version into version 16. You can do so easily by using Volta. After that, please reset the package-lock.json file into the current version in the main branch. If you need some help to do it, please let me know. I can help you with the package-lock.json issue like what I did in #34 just now.
In the meantime, you can also try to resolve my other comments regarding the ids in the seed.ts file. Thanks! 🙏

OK Mas @zainfathoni , I think the issue with package-lock.json has been fixed.
And I will continue to resolve the other comments regarding the ids in the seed.ts tomorrow morning.

OK Mas @zainfathoni, I think the issue with package-lock.json has been fixed.

Oh, yeah, I didn't realize it. 😅
I think I fixed it by applying the package-lock.json changes in #34, which is compatible with NPM version 6, while NPM version 8 is backwards compatible with it. 😁

And I will continue to resolve the other comments regarding the ids in the seed.ts tomorrow morning.

Awesome! Thank you for contributing! 🙏

Mas @zainfathoni , I've already updated seed.ts and enum.ts. Please help review yah. Thanks.

Oh, yeah, I didn't realize it. 😅 I think I fixed it by applying the package-lock.json changes in #34, which is compatible with NPM version 6, while NPM version 8 is backwards compatible with it. 😁

Btw, I've merged my current branch with the latest upstream branch last night. But, after I run npm run setup, I got a warning like this

After that, my package-lock.json has a lot of changes like this. Currently, I'm not committing these changes.

Is this OK mas @zainfathoni ?
NodeJS and NPM versions I'm using
❯ node -v
v16.13.1
❯ npm -v
8.1.2

Mas @zainfathoni , I've already updated seed.ts and enum.ts. Please help review yah. Thanks.

When it's ready for review, please remove the Draft status of the PR by clicking this Ready for review button, @guntoroyk. 😁

Is this OK mas @zainfathoni?
NodeJS and NPM versions I'm using
❯ node -v
v16.13.1
❯ npm -v
8.1.2

Yes, it is expected when you have upgraded your NPM into version 8. We can resolve this warning separately. For this PR, let's avoid making changes to the package-lock.json file. Thanks, Mas @guntoroyk! 🙏

@all-contributors please add @guntoroyk for code


Add easy record steps to builds

Currently, in order to record test results for playback, we have to carry along a lot of environmental settings. This makes it a bit cumbersome to re-record tests once changes have occurred.
It'd be good to be able to have the necessary settings picked up from the environment (and then stripped away as necessary) via an npm build step (eg: record-browser or record-node)

Jonathan, the only thing needed is the TES_MODE environment variable. What are we missing?

Last I tried it, you had to pass in all the environment variables the test used (including the CLIENT_ID, etc that EnviromentCredentials used). This is a bit lengthy and error-prone, so why not just have the recorder (if possible) know what environment variables it needs so that it can store them for the playback

The recorder already replaces all the environment variables with stub values! Only TEST_MODE.

Yes, though this was around what you pass to the recorder to do a recording. Using the .env file might be a better fix, which is sounds like the direction we're going.

I'm closing this for now! Please open again if I'm missing something ❤


What is best way to use multiple presenters within a fragment?

Most examples use annotation RequirePresenter to bind a presenter to one fragment which in turn extends from NucleusFragment. However, let's say I have a fragment which can be conceptually split into multiple views and which could be populated by one presenter each. Is there any current way to do it. We can like make a Presenter object inside each sub-view and pass on all Fragment Lifecycle events to it but that may become prone to error in case one of lifecycle events are not passed to presenter. Is there any thing already present within nucleus which can handle such scenario or will we need an implementation something like I mentioned before

https://github.com/konmik/nucleus/issues/89


vcpkg is not integrated into VS2017

Very similar to https://github.com/Microsoft/vcpkg/issues/707
I ran through the readme, exactly as this user has. Restarted VS and still nothing.
Package: libjpeg-turbo
Installed using:  .\vcpkg install libjpeg-turbo:x64-windows
Ran: .\vcpkg integrate install
I don't get any output from intellisense, and this is from the build output:
------ Build started: Project: jpeg_test, Configuration: Debug Win32 ------
Build started 7/16/2018 2:01:30 PM.
Target InitializeBuildStatus:
Touching "Debug\jpeg_test.tlog\unsuccessfulbuild".
Target VcpkgTripletSelection:
Using triplet "x86-windows" from "C:\PKG_MNGR\vcpkg\installed\x86-windows"
Target ClCompile:
All outputs are up-to-date.
jpeg_test.cpp
c:\users[username]\source\jpeg_test\jpeg_test\jpeg_test.cpp(5): fatal error C1083: Cannot open include file: 'turbojpeg.h': No such file or directory
Done building target "ClCompile" in project "jpeg_test.vcxproj" -- FAILED.
Done building project "jpeg_test.vcxproj" -- FAILED.
Build FAILED.
c:\users[username]\source\jpeg_test\jpeg_test\jpeg_test.cpp(5): fatal error C1083: Cannot open include file: 'turbojpeg.h': No such file or directory
0 Warning(s)
1 Error(s)

If I include the entire path like so:
#include "C:\PKG_MNGR\vcpkg\installed\x64-windows\include\turbojpeg.h"
It can find the header (obviously) but the library linking breaks.

Why does it say this:
Installed using: .\vcpkg install libjpeg-turbo:x64-windows
then it says this:
Using triplet "x86-windows" from "C:\PKG_MNGR\vcpkg\installed\x86-windows"

@DogFive

I don't get any output from intellisense, and this is from the build output:

------ Build started: Project: jpeg_test, Configuration: Debug Win32 ------
You installed a 64 bit library, but you compile a 32-bit project. The 2 need to be matched, select x64 from the pull down windows of the configuration menu bar.
@carmangary
See above.

This was sadly after I tried all the configurations. I figured I would try the x86 debug as well and see if that would work. I forgot to change it back for the logs to post here.
I'll upload the x64 output when I get back.

I've got the same issue having ran through the read me and installed the zlib triplet for windows-x64-static. In this case the header can't be found (error c1984).
What is the process for integrating in to vs manaually?
This is vs 2017 community 15.7.5.

The problem I already filed as #3780. Nobody, amongst the people maintaining vcpkg seem to test the triplet x64-windows-static in a deployment situation, it builds all fine, but the integration does not work.


Only display "Toggle Inherited fields" when there's a super class, closes #120

Ideally we would also check if there are any additional fields, but this is a start.
@markknol: Can you make sure that this change gets into the other themes too?

I'm not sure if the haxe theme has inherited fields?

@Simn In the new haxe theme there is no such thing as inherited fields. http://api.haxe.org/v/dev/js/html/Element.html
Should we add it?

Yeah


bug: nvim-treesitter-context Unable to load context query for haskell:

Did you check docs and existing issues?

[X] I have read all the LazyVim docs
[X] I have searched the existing issues of LazyVim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
NVIM v0.9.5
Operating system/version
Archlinux Rolling
Describe the bug
Every time when I firstly open a haskell file with lazyvim, nvim-notify will inform me that something wrong with nvim-treesitter-context
Steps To Reproduce

Install haskell tree-sitter parser
simply open a haskell file

Expected Behavior

LazyVim does not have any control over the treesitter parsers. Please create an issue at the appropriate repo. Either nvim-treesitter or the plugin treesitter-context.


msbot connect qna command fails if .bot file already contains a qna service with empty strings

[EDIT: editted to reflect this only happening with qna command. LUIS, appinsights and dispatch work as expected]
Discovered using the nodejs sample from botbuilder-samples, #11. QnAMaker
Describe the bug
I'm attempting to build one of the samples programmatically, without having to manually add in keys. This sample comes with an 'empty' qna maker service connection in the botfile, ready to be filled out manually (see screenshot below). Attempting to add a qnamaker service via 'msbot connect qna [options]' results in 'invalid URL' error until that whole section is deleted from the bot file. Attempting to use 'msbot disconnect ' with the service's pre-set ID (34) results in the same 'invalid URL' error. Once it's been removed through VSC or VS2017 manually, 'msbot connect qna [options]' works as expected.
To Reproduce
Steps to reproduce the behavior:

Using command prompt, use the command 'git clone https://github.com/Microsoft/BotBuilder-Samples' to clone repo.
Still in CP, navigate to NodeJS sample 11.
enter 'msbot connect qna' along with correct options
Receive error 'TypeError [ERR_INVALID_URL]: Invalid URL:'
enter 'msbot disconnect 34' (since the qna service has no associated 'name').
Receive error 'TypeError [ERR_INVALID_URL]: Invalid URL:'
Open VSC, navigate to bot file, delete entire qna section.
enter 'msbot connect qna' along with correct options
no error.

Expected behavior
msbot has no problem duplicating an already existing qna service or adding a second qna service, it should not hiccup about this 'empty' service.
Screenshots

If applicable, add screenshots to help explain your problem.

[bug]

We are no longer using .bot file. Please use ARM templates that ship with the samples.


add: Affinity Propagation ALgorithm

Describe the algorithm/code
This clustering algorithm is completely different from the others in the way that it clusters data. Each data point communicates with all of the other data points to let each other know how similar they are and that starts to reveal the clusters in the data. You don't have to tell this algorithm how many clusters to expect in the initialization parameters. Please assign me this issue with hacktoberfest tag
Do you want to work on this feature?

[X] I am willing to implement this feature.

Hi @adi271001! 👋🏻
You can start working on this issue! Do let me know if you need any help. ✨

created pull request and added codes