creating GuessingGame.html

Closes: #224
Describe the changes you've made
added files related to guessing game
Describe if there is any unusual behaviour of your code(Write NA if there isn't)
NA
Checklist:

[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation.
[x] New and existing unit tests pass locally with my changes.

I have done the required changes,
but i am not able to squash all the commits into one,
Please be kind enough to merge this request

I have done the required changes,
but i am not able to squash all the commits into one,
Please be kind enough to merge this request

@kmryashasvi Read this to squash the commits.

That article is tedious for me,
but you can also do the following in one click,
but I have to go the long way

Please tolerate and (squash and merge) this time,
I will not create unnecessary commits by next time.

@kmryashasvi Sorry but these are 33 commits. You should squash them by your own and learn how to do squashing :)
I know I can squash them but these are much more than expected!!


adds query data confirm by exact range

Closes https://github.com/celestiaorg/celestia-app/issues/366

Yes, 100% we will need to clean up the queries and also the keepers


Add syllable tokenizer based on legality and onset maximization

This adds the second of the two syllable tokenizers based on the Legality Principle and Onset Maximization from #2203 .

Thanks, @cuspymd , updated!

Thanks @henchc and @cuspymd!


Vulnerability in hoek package

There is a vulnerability in the hoek package which is required by hawk that request depends on.
Request depends on hawk version ~6.0.2. Updating to hawk version 7.0.0 would fix the problem.

I tried just bumping the version earlier today but the test broke. I had to jump off to do something else but I only got as far as this faster way to run the test:
npx taper tests/test-hawk.js

as far as i understand it, the issue is with a cve, https://nvd.nist.gov/vuln/detail/CVE-2018-3728, regarding hoek < v5.0.3; hawk v6.0.2 includes hoek 4.x.x.
the cve states that “hoek node module before 5.0.3 suffers from …” and references https://github.com/hapijs/hoek/commit/32ed5c9413321fbc37da5ca81a7cbab693786dee as a fix in v5.0.3
however, v4.2.1 also has that fix:
https://github.com/hapijs/hoek/commit/5aed1a8c4a3d55722d1c799f2368857bf418d6df
https://github.com/hapijs/hoek/blob/v4.2.1/lib/index.js#L116
i sent an email to nvd.nist.gov about the issue.

See here: https://github.com/request/request/issues/2891#issuecomment-372271727

To confirm the findings of dan-nl, both links from securityfocus and hackerone in the CVE state that it has been fixed

Not Vulnerable:
| Hoek Hoek 4.2.1
| Hoek Hoek  5.0.3

vdeturckheim posted a comment. Feb 15th (2 months ago)
Fix has been backported to 4.x track of the module and published as 4.2.1. (see https://github.com/hapijs/hoek/pull/231 )

and it's confirmed by @nlf in https://github.com/hapijs/hoek/issues/230#issuecomment-366056246

It has been fixed.
To further discuss, (…)

@warpdesign you said

Request depends on hawk version ~6.0.2. Updating to hawk version 7.0.0 would fix the problem

Bu how do I do that if I don't have hawk directly as a dependency?
<EMAIL_ADDRESS>/home/jfolpf/autocosts
└─┬<EMAIL_ADDRESS>  └─┬<EMAIL_ADDRESS>    ├─┬<EMAIL_ADDRESS>    │ └──<EMAIL_ADDRESS>deduped
    ├─┬<EMAIL_ADDRESS>    │ └─┬<EMAIL_ADDRESS>    │   └──<EMAIL_ADDRESS>deduped
    ├──<EMAIL_ADDRESS>    └─┬<EMAIL_ADDRESS>      └──<EMAIL_ADDRESS>deduped

which npm command?
thanks

Can confirm, I've had 6 repos flagged by github for having the hoek vulnerability because of the request library.

@jfoclpf  I guess it should be possible to temporary fix the problem by publishing forks with an updated version. But you don't want to go this road. Better wait for an official resolution (which shouldn't be long to come this the vce state just needs to be updated for hoek v4.2.1).

The Node.js 4.x release line is going end of life April 30th, compatibility with it should not be a concern after then.

yes, hi :wave: hoek maintainer here. version 4.2.1 has been patched. github's alerts are currently wrong. i've submitted a request to correct the version range in the CVE and also harassed some kind folks at github to take care of things on their end. hopefully they'll stop reporting that version as vulnerable soon.

https://github.com/request/request/issues/2926#issuecomment-385087487
version 4.2.1 has been patched

https://github.com/hapijs/hoek/issues/247#issuecomment-385012074
I submitted a request to update the CVE, hopefully that’ll happen soon and GitHub can get their db updated. Until that happens this is all out of my hands. I’m leaving this open in the hopes other people will find it.

!?

@dscalzi,
hawk > v7.0.0 drops support for node 4 and 6
https://github.com/hueniverse/hawk/blob/v7.0.1/.travis.yml
hawk > v6.0.2 includes hoek 5.x.x
https://github.com/hueniverse/hawk/blob/master/package.json#L19
hoek > v4.2.1 drops support for node 4 and 6
https://github.com/hapijs/hoek/blob/v5.0.0/.travis.yml

How is this issue going now plz?

@diamont1001 it's already fixed

@Bjornskjald are u sure?
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

@diamont1001 hoek 4.2.1 has the bugfix backported

@Bjornskjald

@diamont1001 because if you weren't lazy enough to read the whole discussion you would see it's a bug with GitHub and hoek maintainer already contacted them...

status update?

status update?

@phillmv from @GitHub staff has posted an explanation at https://github.com/hapijs/hoek/issues/247#issuecomment-386708295:

[...] We fixed the versions we alert on back on Monday, and I personally deleted all the bad alerts earlier today. [...]

@NadGu plz check your package-lock.json file first.

@diamont1001 done right now. The version of  hoek is 4.2.1. What can I do to update it?

<EMAIL_ADDRESS>is ok.
I think that u just have to wait for github to refresh the data, at least I did it at the time, and it worked.

@diamont1001 So let's wait! At least I did all that I could. Thank you!


subtraction function

For some reason users want this, but yeah, it completes the basic math palette, so why not : )

simple enough, i mean you can just use the add function with negative numbers, but alright

Yeah, this has been discussed many times in support server, but users are still lazy and say add -1 is confusing


Option to upload to upload to HotSLogs won't stay checked

When I updated the uploaded, it unchecked my option to upload to HotSLogs. And then just now, I noticed it was unchecked again, but I don't think there was an update recently, and I'm not sure how it happened the 2nd time.
The checkbox should persist.

First time did it update automatically or you downloaded and ran setup.exe?

It was an automatic update.

In that case it's weird, I didn't get any settings resets. Did your replay list (upload statuses) got cleared too?
After a fix for #19 gets released settings should be more stable, but next version 2.0 is planned after I implement #17, could be a week or two from now

Did your replay list (upload statuses) got cleared too?

Not that I noticed.
I will try and keep an eye out and see if it happens again and/or if I can more reliably reproduce it.


fix: pill: ensure pill heights match latest design specification

SUMMARY:
Pill component height is determined by the line-height of its content because it may wrap via lineclamp prop. This change adjusts the line-height so it's not a float, updates padding as necessary to match the following spec:
PillSize.Large = 44px
PillSize.Medium = 30px
PillSize.Small and PillSize.XSmall = 24px
The medium size Pill spec also requires the border-radius to be 6px, as this isn't snapped to the base 4 grid, it will not be referenced from SASS variable definitions. Some padding also needs to be local to the module as the base 4 line-height effects that spacing relative to the font-size.
https://github.com/EightfoldAI/octuple/assets/99700808/6147123d-4db7-4c8c-ac34-8fbcb1cba9b3
Figma Specification (Eightfold internal only)
JIRA TASK (Eightfold Employees Only):
ENG-51328
CHANGE TYPE:

[x] Bugfix Pull Request
[ ] Feature Pull Request

TEST COVERAGE:

[x] Tests for this change already exist (CSS only UI snaps updated with this change)
[ ] I have added unittests for this change

TEST PLAN:
Pull the PR branch and run yarn and yarn storybook. Verify the Pill stories behave as expected.

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@421d785). Click here to learn what that means.
Patch has no changes to coverable lines.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #626   +/-   ##
=======================================
  Coverage        ?   84.66%
=======================================
  Files           ?      809
  Lines           ?    17575
  Branches        ?     6260
=======================================
  Hits            ?    14879
  Misses          ?     2629
  Partials        ?       67

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


all-contributors-cli: init at 6.26.1

Description of changes
CLI for All Contributors. See the documentation for more details.
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Thanks for your contribution!
Could you package this with yarnConfigHook and so on? nixos.org/manual/nixpkgs/unstable#javascript-yarn Unfortunately, we can no longer accept new nodePackages. see #229475

Ah! Thanks for the information. I wondered why the script took so long to build …
I've attempted reimplementing this with the newer method, but ran into some issues with the lockfile as the upstream repo doesn't provide one. It seems like something goes wrong when prefetching the dependencies. Any clue as to what could be causing this?

Seems like upstream has more issues and isn't really maintained any more in favour of the GitHub bot, so I'll close this for now


Spyder couldn't start after main window shows up

Description of your problem
After a clean setup of WinPython-64bit-<IP_ADDRESS>Qt5, and clicking the spyder.exe icon, the main window of Spyder shows up, but the IPython console could not be started and connected to, meanwhile the windows becomes frozen and un-clickable after a while (10 or 20 seconds). The same issue happens if I install 3.5.4 instead. (I already have all the antivirus or firewall stopped while trying)
Another weird thing is that, two other colleagues with basically the same computer setup and internet environment do get Spyder working normally, while it's me and another colleagues have the same issue. Could this be related to any other software installed on the computer?
Thanks in advance!
What steps will reproduce the problem?

Install WinPython-64bit-3.6.2 or WinPython-64bit-3.5.4
Start Spyder by double-clicking the Spyder.exe icon

What is the expected output? What do you see instead?
The main window shows up and gets frozen before connecting to IPython console.
Please provide any additional information below
Versions and main components

Spyder Version: 3.2.1dev0
Python Version: 3.6.2
Qt Version: n/a
PyQt Version: 5.9
Operating system: Windows 7 64 bit

Dependencies
Please go to the menu entry Help > Optional Dependencies (or
Help > Dependencies), press the button Copy to clipboard
and paste the contents below:
Couldn't do since Spyder is not clickable.

Thanks for reporting. Could you start Spyder in a console with this command
spyder --show-console

and see if any errors are printed there?
@stonebig, have you seen this bug before?

Hello,
Thanks for the reply. I tried that before but it didn't help much. There was a console window that flashed for a second on the screen then disappeared, but then the main window of Spyder would never show up.

Does this problem happen if you use Anaconda instead of WinPython?

Sorry but I don't have Anaconda installed on my computer. Do you think that might make a difference? I can certainly try it out.
Also, I've seen other similar issues reported online, and some people think it's the problem between pyqt5.9 and Windows 7. So do you think I should try a WinPython version with an elder pyqt5?
Thanks

Update: I just tried WinPython 3.5.3 with PyQt5.7.1, and everything works just fine! So is it really of the PyQt5.9 being incompatible with Windows 7? But then I don't understand why my other colleagues can get it working with the same setup...

Ok, this seems an issue with WinPython and not Spyder, so I'm closing it.
If you want to keep discussing about it, please open an issue in the WinPython issue tracker.


Telegram bot support

Anyway to add telegram bot support too ? via heroku config vars ?

https://github.com/pawanpaudel93/PTorrentBot code is here but i havenot checked if it is working or not. I will update this repo with readme soon. Follow there.

Thank you !


adb fails to install legacy WhatsApp | macOS

Describe the bug
After backing up and uninstalling the existing Whatsapp on the device, the script proceeds to install the legacy WhatsApp. However, it runs into the following error: adb: failed to install helpers/LegacyWhatsApp.apk: Failure [INSTALL_FAILED_VERSION_DOWNGRADE].
To Reproduce

Device connected via cable to Mac and USB debugging enabled
Python requirements installed and dependencies installed
Run python3 wa_kdbe.py
See error

Screenshots

Desktop:

OS: macOS Big Sur

Smartphone:

Device: Motorola G4 Plus
Android Nougat
Version 7.0

[INSTALL_FAILED_VERSION_DOWNGRADE]. is a known bug. Fix it by running with python wa_kdbe.py --allow-reboot


Add support for SupportFragments and possibility of disabling minutes.

Currently using support fragments in my project and the dialog.setTargetFragment() is expecting a fragment. Anyway of using support fragments? Also allowing minutes to be disabled would be a cool feature.

Hi, thanks for feedback. Have you use android.support.v4.fragment? In this
case, for now, I don't know how resolve your problem but with the next
release I will try to support it too. For the possibility to disabling
minutes, in the next release I will add it. Thanks and have a good day
Il mer 28 mar 2018, 01:37 stshelton<EMAIL_ADDRESS>ha scritto:

[image: Boxbe] https://www.boxbe.com/overview This message is eligible
for Automatic Cleanup<EMAIL_ADDRESS>Add cleanup rule
https://www.boxbe.com/popup?url=https%3A%2F%2Fwww.boxbe.com%2Fcleanup%3Fkey%3DtZlDG3k0%252FFGQhBdVQhp4iJ%252BlzKQN5sJrV8y%252FC0xdgJg%253D%26token%3DWsgqn%252FO00YgNaM9S%252B7T80c0UG9xCvtAZNI9dQSQ7UYEWa0043HV6F6v73WzTgvcez50CK2Ro8RUO3x6BFJSLMCW%252FASzwuzsyVNcVvXit1pf%252FhIpVPkX3li9alQWr3yK9NB9wQT%252BvKHqvAohrFgu82w%253D%253D&tc_serial=37861328089&tc_rand=1167587825&utm_source=stf&utm_medium=email&utm_campaign=ANNO_CLEANUP_ADD&utm_content=001
| More info
http://blog.boxbe.com/general/boxbe-automatic-cleanup?tc_serial=37861328089&tc_rand=1167587825&utm_source=stf&utm_medium=email&utm_campaign=ANNO_CLEANUP_ADD&utm_content=001
Currently using support fragments in my project and the
dialog.setTargetFragment() is expecting a fragment. Anyway of using
support fragments? Also allowing minutes to be disabled would be a cool
feature.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/PuffoCyano/Range-Time-Picker-Dialog/issues/2, or mute
the thread
https://github.com/notifications/unsubscribe-auth/Ainf8IVbIaIzjpZvpGFKj2QpfwXmKlbVks5tisvRgaJpZM4S9yw7
.

hi, I have the same problem.

Hi guys. In the last release I have added the ability to disable minutes. Try it ;)


Sticky menu looses it's stickiness when off-canvas menu opened (Foundation 6.3)

The combination of a sticky menu bar and off-canvas menu seems to have a bug in that the menu looses it's stickiness when the off-canvas menu is opened.
How to reproduce this bug:

Scroll down a little
Open off-canvas menu
Top menu disappears (moves up to the top of the page, instead of top of the window)

What should happen:
I think the sticky top menu should stay sticky at the top of the window, but move out to the side as it rightfully does with the rest of the main content
What happened instead:
It moves out to the side with the rest of the main content, but attaches to the top of the page instead of staying at the top of the window.
Test case:

CodePen with Foundation 6.3.0

Notes:
In a previous version (6.2.4) the page scrolled up to the top, when the off-canvas menu was opened, but that is not ideal if you want to use the off-canvas menu for tools etc.
I like that the main content stays where it is, but the sticky top menu should too.
I'm fairly new to Foundation, so there might be a setting that I have missed, if so, please let me know.

@brettsmason Is the new Off-canvas related to this bug ?

@ncoden I can confirm its a bug, but I'm pretty sure its to do with sticky rather than off canvas.
@kball will know more I'm sure.

So I looked into this some more. It looks like this is an issue with position: fixed (set on the .sticky element) along with css transform.
The only workaround I can find is using JS to set the top position to the current scroll offset.
See http://stackoverflow.com/questions/15194313/transform3d-not-working-with-position-fixed-children  for an explanation
Also see this CodePen with the suggestion added: http://codepen.io/brettsmason/pen/ygXJYK (edited)
@kball I'm not sure what the best way to fix this would be. We could change the off canvas behaviour to not use translateX/Y and use another method, but I chose that as it gives the best performance across devices.

@brettsmason I was thinking we could add an option to sticky for when it is being used with an off-canvas component and make it so that sticky behaves as you have it in your codepen only when that option is enabled. The option would be disabled by default. Thoughts?

@colin-marshall That sounds like a good solution. I guess maybe we don't name it specific for off canvas (or do we?) as it applies to any element that transforms, but maybe mention it in the description (and maybe a callout on the docs on both places).
I also noticed if you scroll fast on my CodePen the performance isn't the best - don't know if there's a better way to do it?

@brettsmason I agree a more universal name like absoluteMode, transformMode, or stickyAbsolute would be better. Have you tested the new off canvas with non-menu sticky components to see if there is any bugs in other use cases?
What device and browser were you seeing poor scroll performance with?

@colin-marshall Would it somehow be possible to check if a parent container is transformed? And then if so set the position using JS, otherwise fall back to the CSS only. This would avoid any confusion with people not being able to get it to work, and we only want the JS positioning when off canvas (or a transformed container) is open.
I haven't tested with any other types of sticky use case, but I'll get some pens setup so we can check.
It was in Chrome for Windows - with fast scrolling it didn't seem to stick to the top quite like position: fixed did - sort of "bobbed" up and down a bit very slightly.

@brettsmason you can check if the parent is transformed by just getting the CSS transform values for x and y and seeing if they are set to anything other than zero. The problem is that when off-canvas is opened and closed the menu is not actually becoming "unstuck" it just changes where it think it's supposed to be stuck at. So I'm not sure how it would know when to check if the parent is transformed.
This might be a good situation for the new mutation observers, but I need to learn how they work first. I have been meaning to get familiar with them so this poses a good opportunity for me to dig in to them.

@brettsmason it looks like if you add -webkit-transform: translateZ(0) to the sticky element it might get rid of the weird behavior you see in Chrome. The SO post you linked had a link to another post (http://stackoverflow.com/questions/11258877/fixed-element-disappears-in-chrome) where the accepted answer talks about adding that to a position: fixed element to fix some wonky behavior. One of the comments says it worked for absolute positioning as well. I can't reproduce on Mac or else I would test.
Comment regarding absolute positioning:
http://stackoverflow.com/questions/11258877/fixed-element-disappears-in-chrome#comment34523987_18764086

@colin-marshall When you have a bit of time can we discuss how we can get this into the next patch? 😄 👍

@brettsmason I can actually see the "buggy" scroll behavior now. I think it's happening because it has to keep setting it to position absolute with every scroll event and it can't keep up with scrolling. I think first we need to see if this even fixable before we go dive into the rest of it. I'll work on it a bit today and see if I can come up with anything.

@colin-marshall @brettsmason Would it be possible to change the positioning to use transform rather than x/y offset on absolute? That would prevent the browser from having to repaint every change and make it much easier to keep up.

@kball that's a good idea but it still doesn't keep up very well. The plus side to this solution is that it only can't keep up when the menu is opened while with absolute positioning it was always an issue.
Example: http://codepen.io/colin-marshall/pen/apEaJR
When you close the menu there's a second where it goes off screen due to not having separate events for before and after the off-canvas is closed.
Another possible solution is to move the sticky menu outside of the off-canvas container and then translateX on the sticky menu in sync with the off-canvas menu. That would require the sticky plugin to know the value of $offcanvas-size beforehand. I tested this out a couple weeks ago and it worked good except the sticky element was not clickable when off-canvas was open so you had to click below the title-bar to get it to close. Maybe that's just a z-index issue?

In your codepen I'm still seeing the top bar repaint as I scroll... if I add
.sticky {
   will-change: transform;
}

I can get rid of that. (see https://www.fourkitchens.com/blog/article/fix-scrolling-performance-css-will-change-property)
this doesn't help IE & Edge or old android (see http://caniuse.com/#feat=will-change) but may help for just about everything else... even turning on 'low-end device' level throttling in chrome devtools it appears to still keep up.

@kball you meant it was only repainting when the off-canvas was open, correct?
I tried the will-change property and don't see a difference in Chrome. It's still repainting (or looks like it is) when off-canvas is opened.

yes, it was repainting when the off-canvas was open... Can you verify if the repaint is happening using the dev tools? https://developer.chrome.com/devtools/docs/rendering-settings

Repaint only happens when it hits the top of the page. If I scroll using the keyboard it stays perfectly in place like it does with position: fixed but scrolling with the Trackpad makes it choppy.

@kball I was able to isolate the problem to my 2015 15" Retina MacBook Pro with a discrete AMD Radeon R9 M370X graphics card. When I hook it up to an external monitor it works great but on the laptop screen it's choppy. Forcing it to use internal graphics or discrete graphics doesn't make a difference either. So I guess this is an issue with my MacBook model more than anything else.

@kball @brettsmason I started trying to add an event to trigger after the off-canvas menu close animation completes and I think we might need to add something like the timer that Orbit uses to detect when a slide is done transitioning in order to achieve this. Or there might be some way to use a variable that tracks the translationX value of off-canvas content and triggers the event when it hits 0? What do you guys think?

@colin-marshall have you tried using Foundation.transitionend?

@kball that is exactly what I needed! I have it working pretty much flawless in Firefox and Safari. In Chrome, however, the burger icon jerks when the menu opens and you're not scrolled to the top of the page. When you close the off canvas in Chrome the title bar doesn't translate horizontally with the rest of the page content. It stays to the left and then snaps to the right when the transition finishes.
It was doing that before I added Foundation.transitionend it was just harder to notice because it jumped to the top first. I recorded a video of the behavior for you to see:
https://www.dropbox.com/s/en5knqkwo453yoi/Sticky Off Canvas.mp4?dl=0
Chrome is the last one in the video.

Hi, wondering if there's a solution to this issue yet?

hi guys
I can see that the bug is still alive!!!

hi guys
I can see that the bug is still alive!!!

Hi,
I have got a solution:
Move sticky/fixed div outside "off-canvas-content".

Then we need some CSS rules:
.fixed_div {
  position: fixed;
  top: 0;
  width: 100%;
  z-index: 10;
  transform: none;
  transition: transform .5s ease;
  backface-visibility: hidden;
}

.fixed_div.is-open-right.has-transition-push {
    transform: translateX(-250px);
}

.fixed_div.is-open-left.has-transition-push {
    transform: translateX(250px);
}

Last think that we need to do is add some JQUERY to ours app.js:
$('.menu_left').click(function() {
    $('.fixed_div').toggleClass('is-open-right has-transition-push has-position-right');
});
$('.menu_right').click(function() {
    $('.fixed_div').toggleClass('is-open-left has-transition-push has-position-left');
});
$('.close-button, .js-off-canvas-overlay').click(function() {
    $('.fixed_div').removeClass('is-open-right is-open-left has-transition-push has-position-right has-position-left');
});

and that is all :)

WrapTheCode nailed it. Fixed this issue for me

I had a similar issue with Reveal and when scrolled down and activated data-open the top-bar would disappear. Quick fix:
<path to data-sticky element > {
    position: fixed !important;
    width: 100%
}


Problem with Skype Web Control

Hi!
Skype Web Control Skype web control does not show icons

What could be the problem?

Thanks!

This repro is currently only taking Design Change Requests (DCR) issues. For submitting bug fixes and feature requests related to the skype channel, please go to the following repo [BotFramework-Services](https://github.com/Microsoft/BotFramework-Services).


Fixed typos introduced in PR #3783

This change is

@tedb Please sign the CLA when you get a chance. Thx


Look into resourceExists

Need to research the resourceHostgroupExists (or any resourceExists) and see if there is benefit to implementing this. From brief, initial reading, it sounds like a way to reduce number of reads performed which are more resource intensive. Could provide performance improvements but need to look at this in more depth

At this time I don't think this is needed so closing it out


Are mapped link URLs with query strings no longer supported?

I am updating an old 2.4 site which has a whole lot of MappedLink redirects from urls like /page.php?section=240. It seems this module used to redirect urls with querystrings but not anymore? Any reason why or is there a new way of doing it or?
This is the main bit of code that appears to have been removed from LinkMappingFrontController at some point before you created current new repo
if ($request->requestVars()){
    $queryString = '?';
    foreach($request->requestVars() as  $key => $value) {
	if($key !='url'){$queryString .=$key.'='.$value.'&';}
    }
    $queryString =  rtrim($queryString,'&');
}
$link = ($queryString != '?' ? $request->getURL().$queryString : $request->getURL());

Thanks,
Shea

This module has been superceded by the misdirection module, and is therefore no longer maintained.
https://github.com/nglasl/silverstripe-misdirection


Tabs reopen in random order

When I reopened my tabs, the tabs opened on my new phone were in an apparently random order compared to the tabs on my old phone.
Chrome 120 in both cases; transferring from a Pixel 3a running Android 12 to a Pixel 8 running Android 14.
Workaround: I can manually edit the tabs-reopen.sh file to fix this.

This is probably an issue with the underlying Chrome HTTP API endpoint, which is used to collect the open tabs.
This tool doesn't transform the received data in any way, except for iterating over the entries in order. If they're already coming back in a seemingly random order, I don't think anything can be done about it.
I will re-check with my own device(s) regardless. Thanks for reporting!

Added a new section in README.md addressing the tab order and groups.


Referencing issue #9928 of PrestaShop/PrestaShop

See my comment (https://github.com/PrestaShop/PrestaShop/issues/9928#issuecomment-447995410), to issue #9928 of PrestaShop/PrestaShop. Relates to issues with VAT number and EU VAT + B2B.

Thank you @borlum I also wanted to fix the core problem, actually the TaxManager is used in various places in the code, from the Product class to the Cart class, the issue is that the used Address is often generated with a few fields but not all of them https://github.com/PrestaShop/PrestaShop/blob/cb3663e22786254b5667a2ffe8011576223ba69c/classes/Product.php#L3411
Whereas it should fetch the user address to get all the informations.
I started to fetch the correct address in various places, but sometimes you simply don't know the customer so you don't have the information to fetch the correct Address, and even if you could I'm afraid sometimes you purposely don't want to use this customer Address so forcing it everywhere might create other unexpected bugs..
Your hot fix has the advantage only modify this module so at least we won't introduce any unexpected behavior for shop which don't use this module.
Our QA team is going to test your fix before we can merge it and upgrade the module.

Thanks @borlum  :)


Enable users to override client default API versions

...with code like this:
armsubscription.NewSubscriptionsClient(cred, &arm.ClientOptions{
	ClientOptions: azcore.ClientOptions{
		APIVersion: "42",
	}
})

To get this API for ARM clients, users can simply upgrade azcore--no code gen required. For data plane clients, we'll need to release new versions that tell the new pipeline policy which header/query param to set. It's therefore possible for a user to upgrade azcore and set the new option for a data plane client that won't respect it. In this case I have the policy's Do() return an error (a constructor error isn't possible). That's bad, but I like it better than silently ignoring configuration. Let me know if you see a better alternative.

Fixes https://github.com/Azure/autorest.go/issues/784

Also needs an entry in the changelog.

This should also address https://github.com/Azure/azure-sdk-for-go/issues/18688


booboo in HIPPO example

The line
 editor.free(key='Biso')
will not refine Biso, the correct key is "B_iso"...

This should not have been an issue since d['Biso'] = '_atom_site_B_iso_or_equiv' is a dictionary key. Are you sure it wasn't because of some tie or something else? I've confirmed    editor.free(key='Biso') does set the _atom_site_B_iso_or_equiv key to be refined.


[Document]: Provide a guide for service worker / web worker

What problem does this feature solve?
Write a guide for how to use service worker and web worker in Rsbuild.
What does the proposed API look like?
New document.

Outdated


Filter empty Content-Type and Content-Length in fromGlobals function.

As mentioned in issue #363. @GrahamCampbell
Perhaps an oldschool isset is faster than an array filter, but should matter much in the context of a full request. Added a test for good measure.

Ok after some research the conclusion actually is that stripping empty headers is a bad idea.
This issue is a good source of multiple other sources: https://github.com/eclipse/jetty.project/issues/1116


[DOC] Add document for the use of metrics system in Hudi.

What is the purpose of the pull request

Add document for the use of metrics system in Hudi. Add JmxMetricsReporter and MetricsGraphiteReporter. (Do not have add DatadogReporter since I don't have datadog.api.key)
Move deployment#metrics to the new section.

Brief change log
(for example:)

Modify AnnotationLocation checkstyle rule in checkstyle.xml

Verify this pull request
(Please pick either of the following options)
This pull request is a trivial rework / code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end.
Added HoodieClientWriteTest to verify the change.
Manually verified the change by running a job locally.

Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

@shenh062326 Thanks for you contributing! would you please clarify why put the metrics in a separate section?

@leesf This was discussed in https://github.com/apache/hudi/pull/1672#issuecomment-634841513

@shenh062326 Thanks for you contributing! would you please clarify why put the metrics in a separate section?

@leesf This was discussed in #1672 (comment)

@xushiyan ack, seems like we would also move Datadog here?

@leesf Yes, I will add document for Datadog.

@shenh062326 Thanks for you contributing! would you please clarify why put the metrics in a separate section?

@leesf This was discussed in #1672 (comment)

@xushiyan ack, seems like we would also move Datadog here?

Done.


Debugger out-of-memory when stepping

When the debugger is paused, no garbage is freed to avoid disturbing any heap inspection related pointers being queried by the debug client. Garbage accumulated during paused state (e.g. Eval) is intended to be collected when execution resumes (Resume, StepXxx, etc).
However, if you just keep on stepping and evaling values as you step, it may be that a voluntary GC is not executed in time: one might then be paused, Eval something, run out of memory, and fail to run GC because execution is paused.
This was originally an intentional decision to ensure resume/step wouldn't always need to trigger mark-and-sweep (which can be a bit slow for large heaps). But this has the unintended side effect described above.
The easiest fix is just to force a GC at some useful moment, e.g.:

When resuming (or stepping)
When becoming paused
Every time when debugger message loop is entered in paused state

This should be fixed in Duktape 1.5.x maintenance branch too because it impacts very low memory targets.

Somewhat related: for low memory targets that don't do heap inspection, having a debugger command to force a GC during paused state would be useful. This was part of the original heap inspection plan but was not implemented at the time.

For low memory targets the alternative design of keeping GC running in paused state and requiring an explicit GC lock when doing heap inspection might be cleaner. This would allow GC within an Eval, for example, which isn't possible with an explicit "force GC" command. So you can still run out of memory inside a single Eval.

Notes on IRC discussion:

Adding a "force GC" to Duktape 1.6.0 would be quite simple.
Adding a config option to enable/disable the automatic GC freezing during paused state would be possible (incompatible with heap inspection though). Maybe allow GC in paused state if heap inspection is disabled (there's already a config option for that).

As for the high level alternatives for GC and heap inspection interaction:

Keep current, add automatic GC on resume (or some other opportune place), and add a forced GC. Has the limitations described above (e.g. single Eval runs out of memory).
Keep current, but make GC locking explicitly requested by debug client. Heap inspection commands would fail with an error message (e.g. "gc not locked") until debug client did that. Reset GC locking on resume. This makes a single Eval behave better as it can GC while doing the eval.

@fatcerberus This issue (and its resolution) might interest you. I'd like to find a solution for 1.x, and if there's any change of model, for 2.0.0. This is one of the issues we discussed but decided not to do anything about it yet.
I would be fine with the explicit GC locking approach, provided that the dangerous commands (inspection) would error out until the debug client locked the GC.
Also adding a forced GC to resume/step paths would be a simple (but not ideal) fix for the basic stepping issue.

Despite my misgivings when we originally discussed this, I think I would be okay in general with an explicit GC locking command.  The downside is a bit of extra latency for step-eval-step workflows as the client has to send an extra command each time, but sacrifices must be made. :)
Maybe to be safe, Duktape could reject any heap pointers sent by the client, regardless of context, with a GC-not-locked error.  This way all potential for unsafe operations is cut off at the pass.

Regarding latency, there shouldn't be too much latency because the debug client doesn't need to actually wait for any responses. It can just e.g. send: Pause, LockGc, Eval, without waiting for responses before sending each command. Once it has the Eval result, it can do inspection; finally, when resuming it can send UnlockGc + Resume without waiting for results - or more likely, Resume would automatically unlock the GC. (There are some use cases for keeping GC locked through step/resume but not very many.)
Regarding safety, did you mean that the debug client would refuse to parse heap pointers when not locked? Or that relevant commands would do so? I was thinking more of the commands themselves but it could also be implemented in the value parsing too. There might be some future cases where that would be inappropriate (e.g. when just stringifying a pointer argument one way or another) but for now that should be OK.

Right, that's what I meant: Duktape would refuse heap pointers on the target side until the GC is locked.  But I'm sure if there are any cases where it's both useful and safe to accept them without a lock in place.

But do you mean the target would refuse to parse the heap pointer dvalues - or requests containing them?

Mostly I'm just thinking of how to reduce code duplication to minimize pitfalls when adding commands in the future.  I guess for that it would be enough to have a "read heap pointer, reject if GC not locked" helper.

By the way, for some reason all this time I thought Duktape did run a mark-and-sweep when resuming, but it seems that wasn't the case after all... :)

Would any solution work for the situation where multiple evals are issued while paused? As currently the vscode debugger will issue quite a few and by default they take a few k ram each time to run. Also as you hover over variables they will each call an eval, so if there is no GC when paused eventually memory runs out.  If the eval wasn't so expensive it wouldn't be such an issue.

@fatcerberus Re: running GC on resume, that was my recollection too - but I think we changed it not to do so.

@roceh Adding a ForceGc command that the debug client can issue would help in that Eval scenario. The debug client would need to guarantee that it won't hold any Duktape heap pointers across that command though, because any such pointers would be potentially invalidated.
Also an explicit LockGc + UnlockGc command pair would work: Duktape would run with GC enabled even when paused. All Evals would be GC'd etc. The debug client would issue LockGc only when doing heap pointer inspection and can then UnlockGc when it is done - again enabling automatic GC.

One important thing to stress in documentation is that, if one wants to inspect Eval results, GC must be locked BEFORE the Eval.  Which now brings us back to the issue of a single Eval running you out of memory...

Would it be possible to implement a mechanism where only the Eval result (and anything reachable from it) is excluded from collection?

Would it be possible to implement a mechanism where only the Eval result (and anything reachable from it) is excluded from collection?

The simplest way to do that would be to simply ensure it is reachable, e.g. keep a reference to the last Eval result somewhere (and lose the reference on resume). Anything else gets pretty complicated quite fast. But I'm not sure that would work going forward. For example, you might be inspecting weakly referenced values which are liable to be collected without notice even if the Eval result itself was strongly referenced.
For Eval it would also be possible to first run the Eval with GC enabled. When Eval is done, before losing the result reference, lock the GC. Once that's done, respond to the debug client and pop the result. This way GC would be used normally during eval but the GC would be frozen at the last minute without the Eval result itself being collected.
The downside of that is that GC locking and individual commands would have hard-to-understand interactions. You might also need a flag for Eval to "lock after Eval is done", etc.

Here's a more general-purpose idea that would also accomodate, e.g. debugger watch lists: Add some kind of "debugger stash" and commands for stashing/unstashing heap pointers.  Eval could then take a flag that says whether or not to automatically stash the result.  That's needed because in the absence of a global GC lock, it must be atomic.

Using a stash (or "scratch") based approach would also work with a debugger command set centered around the stash: most operations could write results to stash slots requested by the debug client, and there would be commands for inspecting stash slots, clearing them, etc. If the debug client didn't care about storing the results for longer term, it could just reuse the same slot for all Eval results for example.

@fatcerberus And that reminds me actually of one more approach that was on the table when the debugger was initially designed: allow the debug client to interact with the value stack when it is executing commands. I think we discussed this also when implementing application specific methods.
When paused, an Eval command would leave its result on the target's value stack. You would then have the ability to e.g. inspect the value stack at index -1 (the eval result), pop it off, etc.
This would have the upside of the value stack acting as a logical "scratch" and it would work the same way as the API works for C code. For example, if the debugger had a command for "protected call function", you could push the function and its arguments using whatever commands are best suited to your situation and invoke a ProtectedCall. For example, the function might be a setter you obtained from inspection, while the setter argument could be pushed using an Eval command.
It would also be logical and clear that the value stack would be cleared when you step or resume. The debug client would ensure you don't look beyond the initial stack, i.e. the stack top when you became paused, or at least pop off too many values.

For practical code changes there are two separate issues here:

Incremental improvement for 2.0 and 1.6 - something useful enough, but requiring only small changes to Duktape and debug clients.
Rethinking the inspection model for 3.0.

The value stack approach has its merits, however I think we would still need some sort of persistent stash that wouldn't be cleared automatically on resume.  For example, as alluded to above, a client might set up a watch list, and would need the watched objects' heap pointers to remain valid as long as they remain in the watch list.

Some of the pros/cons ultimately depend on what kind of debug client use cases are supported. For example, some debug clients might consist of relatively independent modules updating their own "panels" without much communication between them (this is what I would like to do, for example). The value stack approach doesn't work very well for this because the value stack would be shared - and since the commands are obviously not atomic w.r.t. the value stack, it requires client side coordination. For other kinds of clients this is not a limitation at all.
The most promising approaches at this point are IMO:

Some form of explicit or automatic locking which is good enough. This includes possibilities like locking after Eval is complete but before the result is GC'd.
Some kind of stash approach.

Locking doesn't work for the watch list use case though unless you keep GC locked for the duration of runtime, which would run you out of memory very fast :)

For a debugger stash one easy and intuitive approach is that a debugger stash is created when one becomes paused. The stash would then be GC'd when we resume (simply by setting the stash object to null and letting refcount do its job).
Adding separate support for persistent stashing (probably limited by debugger attached/detached session lifetime?) would be easy by adding a separate stash for that, tied to the session. But it would have impact on the debugger command syntax (to interact with both stashes) and wouldn't be the simplest model for the debug client.
Another approach is that there's a single stash but when one resumes there's some way to know which references need to be wiped. Maybe property attributes could be used for that purpose somehow. The debugger would require a command to mark a certain reference persistent.
GC pinning is not really a solution, because one needs book-keeping state to undo the pinning when e.g. a debugger session lifecycle ends. It's possible to implement it so that there would be an explicit "pinned by debugger" heap object flag so that it'd be possible to walk the heap and clear all the flags on a resume; this would be more lightweight than an actual stash. But somewhat awkward overall and inflexible if the pinning lifetime would need more flexibility later.

Locking doesn't work for the watch list use case though unless you keep GC locked for the duration of runtime, which would run you out of memory very fast :)

That's true - for the short term change (which this issue is really for) that's not a concern because that use case is not supported at all.
But I agree it'd be nice to solve in the longer term. Only some form of fine grained pinning / persisted reference would solve that.

Yeah, sorry, when issues like this come up, I tend to very easily lapse into thinking in the general case.  I have to get my head out of the clouds now ;)

Hehe, I don't mind at all. I have the same tendency ;)
Like I said above there are two issues here: one for the shorter term, and another for the longer. Heap object inspection (and the debugger protocol as a whole) is a "version 1" with some successful design choices and some less successful.
I don't mind fixing the less successful choices, but when that involves changing the basic structure it's good to be really sure the change is an overall improvement (and hopefully a simplification). Opened #1118 for that.


Major refactoring (removed dependency on annotations, completed tests)

This removes the dependency on annotations for serialization of objects (now using yaml mapping).
I've also added almost all of the tests that were (still) missing, and fixed a lot of hidden bugs.
todo:

[x] Stamp out as much bugs as possible
[x] Add the (missing) tests for all payloads and responses
[x] Add the missing tests for the models

Check out my last couple of commits on my master branch.
There appear to have been some recent changes to the postMessage/attachments structure:
https://api.slack.com/methods/chat.postMessage
https://api.slack.com/docs/attachments
I can add in the extra properties to the yaml (title, author*, etc.) once you merge in your above changes if that helps but I wasn't sure how you wanted to solve the below.
The thing I could figure out how to do nicely (see my third hacky commit) was to have the $payload->attachments property serialised as a JSON array (e.g. as a string) before it is actually sent to Slack. It looked like a HandlerCallback or a PreSerialization event was the way to go but I haven't really used the JMS/Serialization bundle much before.
It also looks like the $payload->attachments->fields needs to be converted to an ArrayCollection as well, as a field is no longer a key:value pair, but is now an array with three properties (title, value, short).

@deancsmith Thanks again for the feedback! :baby:
I've refactored it a bit further. Have a look at the updated Attachment and AttachmentField models, I've also updated tests accordingly.
I've included all properties that are currently documented for the Attachment object you linked to.
I'm currently finalizing this PR so if you see anything else out of the ordinary let me know, cheers!

Hey, great work on this! I still haven't had a chance to go back over my code and change my application to use attachments, rather than just a normal message with markdown as I did as a workaround.
Just looking at your code here I can't see how you got the attachments to be serialised as a string within the ChatPostMessage. From the documentation, and when I was playing around, it looked like the attachments property needed to be a string within the ChatPostMessage array rather than an array itself. If that makes sense? Did you test this against slack?
If not, I hope to have time to revisit this later in the week.


[Broadcaster] Move to the VP8

Depending on the OS and web browser, H264 might not be available. Hence, VP8 which is royalty-free and should always be available

Ahhh :c What a shame :( That could be a use case for negotiating more than one codec for sending :thinking:


[Android] Clear map block map

I'm submitting a ...  (check one with "x")

[ ] question
[x] any problem or bug report

OS:  (check one with "x")

[x] Android
[ ] iOS
[ ] Browser

cordova information:  (run $> cordova plugin list)
cordova-android-firebase-gradle-release 3.0.0 "cordova-android-firebase-gradle-release"
cordova-android-play-services-gradle-release 3.0.0 "cordova-android-play-services-gradle-release"
cordova-android-support-gradle-release 3.0.1 "cordova-android-support-gradle-release"
cordova-open-native-settings 1.5.2 "Native settings"
cordova-plugin-actionsheet 2.3.3 "ActionSheet"
cordova-plugin-advanced-http 2.1.1 "Advanced HTTP plugin"
cordova-plugin-camera 4.0.3 "Camera"
cordova-plugin-core-android-extensions 2.0.0 "CoreAndroidExtensions"
cordova-plugin-device 2.0.3 "Device"
cordova-plugin-dialogs 2.0.2 "Notification"
cordova-plugin-file 6.0.1 "File"
cordova-plugin-file-transfer 1.7.1 "File Transfer"
cordova-plugin-filepath 1.5.5 "cordova-plugin-filepath"
cordova-plugin-geolocation 4.0.1 "Geolocation"
cordova-plugin-googlemaps 2.6.2 "cordova-plugin-googlemaps"
cordova-plugin-headercolor 1.0 "HeaderColor"
cordova-plugin-inappbrowser 3.0.0 "InAppBrowser"
cordova-plugin-ionic-webview 1.1.16 "cordova-plugin-ionic-webview"
cordova-plugin-localization-strings 3.1.0 "Localization"
cordova-plugin-nativeaudio 3.0.9 "Cordova Native Audio"
cordova-plugin-network-information 2.0.3-dev "Network Information"
cordova-plugin-screen-orientation 3.0.2 "Screen Orientation"
cordova-plugin-splashscreen 5.0.2 "Splashscreen"
cordova-plugin-statusbar 2.4.3 "StatusBar"
cordova-plugin-transparent-status-bar 1.0.1 "Transparent status bar"
cordova-plugin-whitelist 1.3.4 "Whitelist"
cordova-sqlite-storage 3.3.0 "Cordova sqlite storage plugin - cordova-sqlite-storage plugin version"
cordova-support-android-plugin 1.0.1 "cordova-support-android-plugin"
cordova-support-google-services 1.1.0 "cordova-support-google-services"
cordova.plugins.diagnostic 5.0.0 "Diagnostic"
es6-promise-plugin 4.2.2 "Promise"
ionic-plugin-deeplinks 1.0.20 "Ionic Deeplink Plugin"
ionic-plugin-keyboard 2.2.1 "Keyboard"
phonegap-plugin-mobile-accessibility 1.0.5-dev "Mobile Accessibility"
phonegap-plugin-multidex 1.0.0 "Multidex"
phonegap-plugin-push 2.2.3 "PushPlugin"

If you use @ionic-native/google-maps, please tell the package.json (only @ionic-native/core and @ionic-native/google-maps are fine mostly)
@ionic-native/core : 4.4.0
@ionic-native/google-maps : 4.4.2

Current behavior:
Currently when change between pages the app call to clear map. Then the map is blocked 1 second and there is a ugly effect.
https://www.youtube.com/watch?v=nTzeFPnUvJQ
Expected behavior:
A behaviour more fluid.
https://www.youtube.com/watch?v=UsfPwrUrStg
Screen capture or video record:
With version 3.6.2: https://www.youtube.com/watch?v=nTzeFPnUvJQ
With our fork: https://www.youtube.com/watch?v=UsfPwrUrStg
Related code, data or error log (please format your code or data):
Commit that fix this error: https://github.com/mapsplugin/cordova-plugin-googlemaps/commit/b130a755a15a3fbc582c35d9a0e5ac5aef2bf773
With official version if keySet.size() is 0, the plugin wait a second... it is no sense. I think it is only a indent error.
Another related commit: https://github.com/mapsplugin/cordova-plugin-googlemaps/commit/98af0f0465aadc0edccc9b5363977186a5174d68

Hi!, I am a mate of @zarelint. We had update our app 2 weeks ago. And in the way we have found several bugs or details.
We had updated our apps (Android and iOS) from version 2.1.1 forked to last version forked: 2.6.2
Thanks a lot for this maravellous project! We can grow up thanks of you.
Links of our apps, if you want test or something (please move to Spain, France or Portugal):

https://play.google.com/store/apps/details?id=com.joinuptaxi.passenger&hl=es
https://apps.apple.com/es/app/joinup-pedir-y-reservar-taxi/id554668455

This is already fixed in the multiple_maps branch version.

@wf9a5m75 I think this bug is in multiple_maps branch too. I will confirm it.
Do you want the pull request from my fork to multiple_maps branch or master branch?

This as fixed in https://github.com/mapsplugin/cordova-plugin-googlemaps/pull/2694 and should be merged into multiple_maps right now 👍

Thanks @JordyLangen


Added option to ignore old items in the news feed module

Some RSS feeds from major news sites contain headlines that are rather old.
To prevent the news feed module from displaying outdated items over and over again, this pull request adds an ignoreOldItemsoption to the module. If this option is set to true, the module will only display headlines that have been published within the last 24 hours. The precise time interval can be adjusted via the ignoreOlderThan option.
This PR does not solve any related issues.

Nice one! Thanks!


Master

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Benny Mei seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Fix use of incorrect variable in peview

Fixes a very minor peview issue where the address range offset is being displayed, rather than the intended range count.

Ah apologies, do I have to sign my commits/any other requirements?

Ah apologies, do I have to sign my commits/any other requirements?

No other requirements.
Thanks for catching this 👍


Tray Publisher: Show last available version

Feature
Old standalone publisher showed last published version on selected context:

This is feature missing in Tray Publisher
[cuID:OP-6736]

This had been implemented and is available on demand in ayon+settings://traypublisher/simple_creators as allow_version_control attribute.


operator obi-stage (0.0.2)

New operator bundle
Name: obi-stage
Version: 0.0.2
Certification project: 660d2cc5bd1fec276a474e53
Test result URL: https://catalog.stage.redhat.com/api/containers/v1/projects/certification/test-results/id/660e461600be06826aff33b6
Test logs URL: https://catalog.stage.redhat.com/api/containers/v1/projects/certification/artifacts/id/660e4614bd1fec276a4762a2

\pipeline restart operator-hosted-pipeline


[2.0] Revert note on regression of CLI for dotnet run "-p" option

Note added with https://github.com/dotnet/docs/pull/1779

It can be a path to a csproj file or to a directory containing a csproj file

I'm keeping a version of this in the 1.0 side and removing from the 2.0 version since this is still broken for 1.x.


EventListener seems to miss collisions

I'm trying to detect collisions between certain objects using a class that extends EventListener. I pass an ID of an object into the mUserData variable when creating a ProxyShape.
Each frame, the listener saves the ID of the two objects colliding in the newContact method. These two IDs are then checked outside to see if they match (if the player has collided with an enemy for example).
The code seems to work sometimes in Debug mode (collisions between certain objects are not always picked up), and doesn't work at all in Release.
Apologies if I'm using the library wrong as I'm still rather new to using physics engines.
Thanks

 Fix Bug #46 - EventListener miss collisions

Thanks a lot for reporting this.
I have not been able to reproduce this issue on my side.
Note that when you create new bodies after some bodies have been destroyed, the new bodies can have the same Ids as the bodies that have previously been destroyed.
Are you able to produce a small piece of code with an EventListener that is not working correctly so that I can test it ?

The version v0.8.0 of ReactPhysics3D has been released. In this version, the way to report contacts with EventListener has changed. Take a look at the user manual here for more information. This issue might have been fixed in this version because of the refactoring.
I am closing this issue now but do not hesitate to reopen it if you still having this issue with the new version.


Add PyTorch to ONNX section to training notebooks

Description

Add PyTorch to ONNX section to the following training notebooks:

Phishing
Root Cause
Log Parsing
SID

Update Phishing and SID models to work with torch 1.13

Closes #892
Closes #529
Checklist
[x] I am familiar with the Contributing Guidelines.
[x] New or existing tests cover these changes.
[x] The documentation is up to date with these changes.

/merge


Reduce memory usage in agent due to kafka batches

As shown here in run11, this tuning drastically reduces memory used due to kafka batching, retrieving similar level than in 1.4 (even slightly better).
It should be verified on large-scale perf tests

I will test this once regression testing is complete, please attach and make a note of it in NETOBSERV-1470 so it can be properly tracked as discussed this morning, thanks

/approve


When displaying the line suggestion after modification, can we make it easier to tell the diff?

Example, in this screenshot, the result after the change is accepted is previewed as ghost text. I really just want it to wrap the variable data with: "JSON.stringify()" (which it does, correctly), but I can't tell at a quick glance it's doing it correctly without scanning both lines of text and mentally diffing. This is a simple example, but the line of code affected might be much more complicated. Can the additions/diff be highlighted somehow?

I'm not sure your setup is working correctly. This is how it looks for me:
Before suggestion:

After suggestion (I did not remove any text):

It "overlays" the suggestion ontop of the existing text. It does not show on the end of the line like yours.

I don't know why. But with your setup, I still can't tell what was the change/diff suggested. In your case, I would like that
tringify( and ) are highlighted different from studio

@hboon I think the idea is that you know what is written before the suggestion shows up, and then once you add something, it overlays on top. That has worked out pretty well for me, but I think it makes sense if there was an option to maybe highlight it.
I just wanted to let you know that something seems off about your setup compared to mine, unrelated to your request :)

@AlexanderArvidsson oh yes, I seem to get that behavior in some file types and the other in some other file types. Strange. Thanks for the heads-up :)


Fix home and doc urls

As noted at staged-recipes, the home is incorrect and the doc_url is incorrect. Both need to be updated to point to the repo instead and the recipe needs to be re-rendered after these changes.

Updated the meta.yml to point to the PyPi page in  #12. While the github repository is the home for development, it is not up to date in terms of releases, whereas the PyPi page is.

Thanks! 😄


Increase Tobira Worker Resilience When Opencast is Unreachable

If Opencast becomes unreachable, the Tobira worker crashes and causes the systemd service to fail because of unsuccessful retry attempts. This circumstance can be caused by network outages or updates from Opencast.
The expected behavior would be for the worker not to exit, handle the error, and, importantly, continue running.

Can you give more details? The worker should in fact not fail when Opencast is down. I regularly look at three long-running Tobira systems and there the worker never failed because of an unavailable Opencast. It just prints errors to the log but recovers automatically. So you have to give me more details to reproduce your error state. What Tobira version? What exactly are you doing?

Log:
Jun 04 06:42:47 oc-presentation-01.xyz systemd[1]: Started Tobira Worker.
Jun 04 06:42:47 oc-presentation-01.xyz tobira[157784]: 2024-06-04 06:42:47.155 INFO  tobira >  Starting Tobira ~~ cli_args=["/opt/tobira/tobira", "worker", "-c", "/etc/tobira/config.toml"]
Jun 04 06:42:47 oc-presentation-01.xyz tobira[157784]: 2024-06-04 06:42:47.155 INFO  tobira >  Loaded config ~~ source_file="/etc/tobira/config.toml"
Jun 04 06:42:47 oc-presentation-01.xyz tobira[157784]: 2024-06-04 06:42:47.155 INFO  tobira >  Starting Tobira worker ...
Jun 04 06:42:47 oc-presentation-01.xyz tobira[157784]: 2024-06-04 06:42:47.171 INFO  tobira::db >  Connected to DB! ~~ server_version="15.3" user="tobira" session_user="tobira" schema="tobira" database="tobira"
Jun 04 06:42:47 oc-presentation-01.xyz tobira[157784]: 2024-06-04 06:42:47.176 INFO  tobira::db::migrations >  All migrations are already applied: database schema is up to date.
Jun 04 06:42:47 oc-presentation-01.xyz tobira[157784]: 2024-06-04 06:42:47.246 INFO  tobira::search >  Connected to MeiliSearch at 'https://oc-index-02.xyz:7700'
Jun 04 06:42:47 oc-presentation-01.xyz tobira[157784]: 2024-06-04 06:42:47.287 ERROR tobira >  error synchronizing with Opencast
Jun 04 06:42:47 oc-presentation-01.xyz tobira[157784]:                                      >
Jun 04 06:42:47 oc-presentation-01.xyz tobira[157784]:                                      >  Caused by:
Jun 04 06:42:47 oc-presentation-01.xyz tobira[157784]:                                      >      0: failed to fetch API version
Jun 04 06:42:47 oc-presentation-01.xyz tobira[157784]:                                      >      1: API returned unexpected HTTP code 503 Service Unavailable (for 'https://xyz/tobira/version', authenticating as 'admin')
Jun 04 06:42:47 oc-presentation-01.xyz tobira[157784]: ▶▶▶ Error: error synchronizing with Opencast
Jun 04 06:42:47 oc-presentation-01.xyz tobira[157784]: Caused by:
Jun 04 06:42:47 oc-presentation-01.xyz tobira[157784]:  ‣ failed to fetch API version
Jun 04 06:42:47 oc-presentation-01.xyz tobira[157784]:    ‣ API returned unexpected HTTP code 503 Service Unavailable (for 'https://xyz/tobira/version', authenticating as 'admin')
Jun 04 06:42:47 oc-presentation-01.xyz systemd[1]: tobira-worker.service: Main process exited, code=exited, status=1/FAILURE
Jun 04 06:42:47 oc-presentation-01.xyz systemd[1]: tobira-worker.service: Failed with result 'exit-code'.
Jun 04 06:42:47 oc-presentation-01.xyz systemd[1]: tobira-worker.service: Scheduled restart job, restart counter is at 5.
Jun 04 06:42:47 oc-presentation-01.xyz systemd[1]: Stopped Tobira Worker.

Oh so you are saying the worker cannot be started while Opencast is down? But a running work does not go down with Opencast. Yes?

Sorry, I should have been a little bit more precise.


Uncaught TypeError: this.getRegexForProperty is not a function

Suddenly editing (not every) js with React content files.

Atom Version: 1.11.1
Electron Version: 0.37.8
System: Mac OS X 10.11.6
Thrown From: react package, v0.16.0
Stack Trace
Uncaught TypeError: this.getRegexForProperty is not a function
At /Applications/Atom.app/Contents/Resources/app.asar/node_modules/text-buffer/lib/text-buffer.js:871

TypeError: this.getRegexForProperty is not a function
    at LanguageMode.editor.languageMode.autoDecreaseIndentForBufferRow (/Users/lio/.atom/packages/react/lib/atom-react.coffee:47:38)
    at TextEditor.module.exports.TextEditor.autoDecreaseIndentForBufferRow (/Applications/Atom.app/Contents/Resources/app.asar/src/text-editor.js:3558:32)
    at Selection.module.exports.Selection.insertText (/Applications/Atom.app/Contents/Resources/app.asar/src/selection.js:499:21)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/text-editor.js:1063:29
    at /Applications/Atom.app/Contents/Resources/app.asar/src/text-editor.js:1102:29
    at TextBuffer.module.exports.TextBuffer.transact (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/text-buffer/lib/text-buffer.js:866:18)
    at TextEditor.module.exports.TextEditor.transact (/Applications/Atom.app/Contents/Resources/app.asar/src/text-editor.js:1519:26)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/text-editor.js:1096:24
    at TextEditor.module.exports.TextEditor.mergeSelections (/Applications/Atom.app/Contents/Resources/app.asar/src/text-editor.js:2497:18)
    at TextEditor.module.exports.TextEditor.mergeIntersectingSelections (/Applications/Atom.app/Contents/Resources/app.asar/src/text-editor.js:2459:35)
    at TextEditor.module.exports.TextEditor.mutateSelectedText (/Applications/Atom.app/Contents/Resources/app.asar/src/text-editor.js:1094:19)
    at TextEditor.module.exports.TextEditor.insertText (/Applications/Atom.app/Contents/Resources/app.asar/src/text-editor.js:1060:19)
    at TextEditor.object.(anonymous function) [as insertText] (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/underscore-plus/lib/underscore-plus.js:77:27)
    at TextEditorComponent.module.exports.TextEditorComponent.onTextInput (/Applications/Atom.app/Contents/Resources/app.asar/src/text-editor-component.js:482:26)
    at HTMLDivElement.<anonymous> (/Applications/Atom.app/Contents/Resources/app.asar/src/text-editor-component.js:3:61)

Commands
     -1:34.4.0 core:cancel (atom-text-editor.editor.is-focused)
     -1:33.9.0 core:move-left (atom-text-editor.editor.is-focused)
     -1:32.8.0 editor:consolidate-selections (atom-text-editor.editor.is-focused)
     -1:32.8.0 core:cancel (atom-text-editor.editor.is-focused)
     -1:32.3.0 core:move-down (atom-text-editor.editor.is-focused)
     -1:30.9.0 editor:consolidate-selections (atom-text-editor.editor.is-focused)
     -1:30.9.0 core:cancel (atom-text-editor.editor.is-focused)
     -1:29 core:backspace (atom-text-editor.editor.is-focused)
     -1:28.2.0 docblockr:parse-enter (atom-text-editor.editor.is-focused)
     -1:28.2.0 editor:newline (atom-text-editor.editor.is-focused)
  4x -1:27.2.0 core:undo (atom-text-editor.editor.is-focused)
  3x -1:25.1.0 core:redo (atom-text-editor.editor.is-focused)
  2x -1:23.6.0 core:undo (atom-text-editor.editor.is-focused)
  3x -1:22.2.0 core:redo (atom-text-editor.editor.is-focused)
     -1:20.3.0 core:undo (atom-text-editor.editor.is-focused)
  2x -1:19.3.0 core:save (atom-text-editor.editor.is-focused)

Config
{
  "core": {
    "packagesWithKeymapsDisabled": [],
    "telemetryConsent": "no"
  }
}

Installed Packages
# User
base16-ocean-dark, v1.2.0 (inactive)
docblockr, v0.8.5 (active)
emmet, v2.4.3 (active)
file-icons, v1.7.19 (active)
language-jade, v0.7.2 (active)
language-pug, v0.0.17 (active)
oceanic-next-italic, v1.0.1 (inactive)
react, v0.16.0 (active)
spacegray-dark-ui, v0.12.0 (inactive)
tool-bar, v1.0.1 (active)
tool-bar-main, v0.0.9 (active)
atom-dark-syntax, v0.27.0 (inactive)
atom-dark-ui, v0.52.0 (inactive)
atom-light-syntax, v0.28.0 (inactive)
atom-light-ui, v0.44.0 (inactive)
base16-tomorrow-dark-theme, v1.2.0 (inactive)
base16-tomorrow-light-theme, v1.2.0 (inactive)
one-dark-ui, v1.6.0 (active)
one-light-ui, v1.6.0 (inactive)
one-dark-syntax, v1.3.0 (active)
one-light-syntax, v1.3.0 (inactive)
solarized-dark-syntax, v1.0.2 (inactive)
solarized-light-syntax, v1.0.2 (inactive)
about, v1.7.0 (active)
archive-view, v0.61.1 (active)
autocomplete-atom-api, v0.10.0 (active)
autocomplete-css, v0.11.2 (active)
autocomplete-html, v0.7.2 (active)
autocomplete-plus, v2.31.1 (active)
autocomplete-snippets, v1.11.0 (active)
autoflow, v0.27.0 (inactive)
autosave, v0.23.1 (active)
background-tips, v0.26.1 (active)
bookmarks, v0.42.0 (active)
bracket-matcher, v0.82.1 (active)
command-palette, v0.38.0 (inactive)
deprecation-cop, v0.54.1 (active)
dev-live-reload, v0.47.0 (active)
encoding-selector, v0.22.0 (active)
exception-reporting, v0.40.0 (active)
find-and-replace, v0.201.1 (inactive)
fuzzy-finder, v1.4.0 (active)
git-diff, v1.1.0 (active)
go-to-line, v0.31.0 (inactive)
grammar-selector, v0.48.2 (active)
image-view, v0.59.0 (active)
incompatible-packages, v0.26.1 (active)
keybinding-resolver, v0.35.0 (active)
line-ending-selector, v0.5.0 (active)
link, v0.31.1 (inactive)
markdown-preview, v0.158.0 (active)
metrics, v1.0.0 (active)
notifications, v0.65.1 (active)
open-on-github, v1.2.0 (inactive)
package-generator, v1.0.0 (inactive)
settings-view, v0.242.2 (active)
snippets, v1.0.2 (active)
spell-check, v0.68.2 (active)
status-bar, v1.4.1 (active)
styleguide, v0.47.0 (active)
symbols-view, v0.113.1 (inactive)
tabs, v0.101.0 (active)
timecop, v0.33.2 (active)
tree-view, v0.209.3 (active)
update-package-dependencies, v0.10.0 (active)
welcome, v0.35.1 (active)
whitespace, v0.33.0 (active)
wrap-guide, v0.38.2 (active)
language-c, v0.52.1 (active)
language-clojure, v0.21.0 (active)
language-coffee-script, v0.47.2 (active)
language-csharp, v0.12.1 (active)
language-css, v0.37.1 (active)
language-gfm, v0.88.0 (active)
language-git, v0.15.0 (active)
language-go, v0.42.1 (active)
language-html, v0.45.1 (active)
language-hyperlink, v0.16.0 (active)
language-java, v0.23.0 (active)
language-javascript, v0.119.0 (active)
language-json, v0.18.2 (active)
language-less, v0.29.5 (active)
language-make, v0.22.2 (active)
language-mustache, v0.13.0 (active)
language-objective-c, v0.15.1 (active)
language-perl, v0.35.0 (active)
language-php, v0.37.2 (active)
language-property-list, v0.8.0 (active)
language-python, v0.45.0 (active)
language-ruby, v0.69.0 (active)
language-ruby-on-rails, v0.25.0 (active)
language-sass, v0.56.0 (active)
language-shellscript, v0.22.4 (active)
language-source, v0.9.0 (active)
language-sql, v0.23.0 (active)
language-text, v0.7.1 (active)
language-todo, v0.28.0 (active)
language-toml, v0.18.0 (active)
language-xml, v0.34.9 (active)
language-yaml, v0.26.0 (active)

# Dev
No dev packages

Solved updating to 0.16.1

What did you update?

React package

this

@elrumordelaluz Yes, thanks.

had to enable and disable the react package a few times, but things are back to normal again.

Still getting it...

Opened a file
Tried to type anything into the file
Got the issue

Atom Version: 1.11.1
Electron Version: 0.37.8
System: Mac OS X 10.12
Thrown From: react package, v0.16.1
Stack Trace
Uncaught TypeError: this.getRegexForProperty is not a function
At /Applications/Atom.app/Contents/Resources/app.asar/node_modules/text-buffer/lib/text-buffer.js:871

TypeError: this.getRegexForProperty is not a function
    at LanguageMode.editor.languageMode.autoDecreaseIndentForBufferRow (/Users/Bny/.atom/packages/react/lib/atom-react.coffee:65:44)
    at TextEditor.module.exports.TextEditor.autoDecreaseIndentForBufferRow (/Applications/Atom.app/Contents/Resources/app.asar/src/text-editor.js:3558:32)
    at Selection.module.exports.Selection.insertText (/Applications/Atom.app/Contents/Resources/app.asar/src/selection.js:499:21)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/text-editor.js:1063:29
    at /Applications/Atom.app/Contents/Resources/app.asar/src/text-editor.js:1102:29
    at TextBuffer.module.exports.TextBuffer.transact (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/text-buffer/lib/text-buffer.js:866:18)
    at TextEditor.module.exports.TextEditor.transact (/Applications/Atom.app/Contents/Resources/app.asar/src/text-editor.js:1519:26)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/text-editor.js:1096:24
    at TextEditor.module.exports.TextEditor.mergeSelections (/Applications/Atom.app/Contents/Resources/app.asar/src/text-editor.js:2497:18)
    at TextEditor.module.exports.TextEditor.mergeIntersectingSelections (/Applications/Atom.app/Contents/Resources/app.asar/src/text-editor.js:2459:35)
    at TextEditor.module.exports.TextEditor.mutateSelectedText (/Applications/Atom.app/Contents/Resources/app.asar/src/text-editor.js:1094:19)
    at TextEditor.module.exports.TextEditor.insertText (/Applications/Atom.app/Contents/Resources/app.asar/src/text-editor.js:1060:19)
    at TextEditor.object.(anonymous function) [as insertText] (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/underscore-plus/lib/underscore-plus.js:77:27)
    at TextEditorComponent.module.exports.TextEditorComponent.onTextInput (/Applications/Atom.app/Contents/Resources/app.asar/src/text-editor-component.js:482:26)
    at HTMLDivElement.<anonymous> (/Applications/Atom.app/Contents/Resources/app.asar/src/text-editor-component.js:3:61)

Commands
     -2:51.5.0 tool-panel:unfocus (ol.tree-view.full-menu.list-tree.has-collapsable-children.focusable-panel)
     -2:51.2.0 settings-view:open (atom-pane.pane.active)
     -1:42.1.0 editor:newline (atom-text-editor.editor.is-focused)
     -1:20.4.0 core:cancel (a.btn-issue.btn.btn-error)
     -1:19.9.0 core:close (atom-text-editor.editor.is-focused)
     -1:14.4.0 core:undo (atom-text-editor.editor.is-focused)
     -0:16 core:close (atom-text-editor.editor.is-focused)

Config
{
  "core": {
    "telemetryConsent": "limited"
  }
}

Installed Packages
# User
atom-beautify, v0.29.13 (inactive)
file-icons, v1.7.22 (active)
imdone-atom, vundefined (active)
imdone-atom-github, v0.1.11 (active)
linter, v1.11.18 (active)
minimap, v4.25.0 (active)
react, v0.16.1 (active)
atom-dark-syntax, v0.27.0 (inactive)
atom-dark-ui, v0.52.0 (inactive)
atom-light-syntax, v0.28.0 (inactive)
atom-light-ui, v0.44.0 (inactive)
base16-tomorrow-dark-theme, v1.2.0 (inactive)
base16-tomorrow-light-theme, v1.2.0 (inactive)
one-dark-ui, v1.6.0 (active)
one-light-ui, v1.6.0 (inactive)
one-dark-syntax, v1.3.0 (active)
one-light-syntax, v1.3.0 (inactive)
solarized-dark-syntax, v1.0.2 (inactive)
solarized-light-syntax, v1.0.2 (inactive)
about, v1.7.0 (active)
archive-view, v0.61.1 (active)
autocomplete-atom-api, v0.10.0 (active)
autocomplete-css, v0.11.2 (active)
autocomplete-html, v0.7.2 (active)
autocomplete-plus, v2.31.1 (active)
autocomplete-snippets, v1.11.0 (active)
autoflow, v0.27.0 (inactive)
autosave, v0.23.1 (active)
background-tips, v0.26.1 (active)
bookmarks, v0.42.0 (active)
bracket-matcher, v0.82.1 (active)
command-palette, v0.38.0 (inactive)
deprecation-cop, v0.54.1 (active)
dev-live-reload, v0.47.0 (active)
encoding-selector, v0.22.0 (active)
exception-reporting, v0.40.0 (active)
find-and-replace, v0.201.1 (inactive)
fuzzy-finder, v1.4.0 (active)
git-diff, v1.1.0 (active)
go-to-line, v0.31.0 (inactive)
grammar-selector, v0.48.2 (active)
image-view, v0.59.0 (active)
incompatible-packages, v0.26.1 (active)
keybinding-resolver, v0.35.0 (active)
line-ending-selector, v0.5.0 (active)
link, v0.31.1 (inactive)
markdown-preview, v0.158.0 (active)
metrics, v1.0.0 (active)
notifications, v0.65.1 (active)
open-on-github, v1.2.0 (inactive)
package-generator, v1.0.0 (inactive)
settings-view, v0.242.2 (active)
snippets, v1.0.2 (active)
spell-check, v0.68.2 (active)
status-bar, v1.4.1 (active)
styleguide, v0.47.0 (active)
symbols-view, v0.113.1 (inactive)
tabs, v0.101.0 (active)
timecop, v0.33.2 (active)
tree-view, v0.209.3 (active)
update-package-dependencies, v0.10.0 (active)
welcome, v0.35.1 (active)
whitespace, v0.33.0 (active)
wrap-guide, v0.38.2 (active)
language-c, v0.52.1 (active)
language-clojure, v0.21.0 (active)
language-coffee-script, v0.47.2 (active)
language-csharp, v0.12.1 (active)
language-css, v0.37.1 (active)
language-gfm, v0.88.0 (active)
language-git, v0.15.0 (active)
language-go, v0.42.1 (active)
language-html, v0.45.1 (active)
language-hyperlink, v0.16.0 (active)
language-java, v0.23.0 (active)
language-javascript, v0.119.0 (active)
language-json, v0.18.2 (active)
language-less, v0.29.5 (active)
language-make, v0.22.2 (active)
language-mustache, v0.13.0 (active)
language-objective-c, v0.15.1 (active)
language-perl, v0.35.0 (active)
language-php, v0.37.2 (active)
language-property-list, v0.8.0 (active)
language-python, v0.45.0 (active)
language-ruby, v0.69.0 (active)
language-ruby-on-rails, v0.25.0 (active)
language-sass, v0.56.0 (active)
language-shellscript, v0.22.4 (active)
language-source, v0.9.0 (active)
language-sql, v0.23.0 (active)
language-text, v0.7.1 (active)
language-todo, v0.28.0 (active)
language-toml, v0.18.0 (active)
language-xml, v0.34.9 (active)
language-yaml, v0.26.0 (active)

# Dev
No dev packages

had still the issue until I've updated atom to 1.11.2

Disabling and Renabling didn't fix this for me? What was the solution to this?

Update plugin to latest version and restart atom.
On Tuesday, 18 October 2016, Michael Mathew<EMAIL_ADDRESS>wrote:

Disabling and Renabling didn't fix this for me? What was the solution to
this?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/orktes/atom-react/issues/205#issuecomment-254600716,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAlAi10v3Fw77aJPrOn40uwtv57ISkcjks5q1RMFgaJpZM4KZnh2
.

--
Ystävällisin terveisin,
Jaakko Lukkari

Sweet that worked. Thanks for the help!

Update the react package from inside Atom with the "Update" button in the "react" package. (File > Settings > Packages > react > Update)

disable auto indent works for me 👍

Update the Package for react.
Worked for me.
Thanks.


Release Version 2.1.0

Use data migrations in version numbers (#2816)
Fixes #2784 - Data migrations framework (#2786)
Fixes #2817 - add jose to bot lambda layer (#2818)
Move "public" resources into R4 Project (#2591)
fix(auth/external): add some missing url params for external auth PKCE exchanges (#2812)
Experiment: remove prettier from ESLint config, try out Biome (Rome fork) (#2748)
Fixes #2808 - handle observation groups in DiagnosticReportDisplay (#2809)
Adding content for Titan case study (#2806)
QuestionnaireForm Cleanup (#2801)
UI Clone for Lab Order Questionnaire (#2787)
Lab order bot (#2791)
Blog Post: GraphQL vs. Rest (#2781)
Fixes #2761 - docs for bot logs and aws athena (#2779)
Adding EMPI documentation (#2754)
Example on Lab Ordering demo (#2716)
Fixed links on about page (#2777)
Adding blog material (#2776)
Fixes #2771 - handle numeric return values from bots (#2775)
New www 'about' page (#2770)

coverage: 94.165%. remained the same when pulling df30692f8a4d0ddf8abff20d75a2245d82a40c10 on version-2.1.0 into 08d11217b7b399c6232432f04389d4c66ce85f18 on main.

We see every step and every move of Medplum! and it´s great to see how strong and big growth...
Because Medplum Rocks!Rocks!
I´m Alejandro from Argentina! Co-Founder EPA Bienestar IA
Our team wish create a "Community of Medplum en Español
What you think? @reshmakh @codyebberson @rahul1
Latin America and the Caribbean population is equivalent to 8.28% of the total world population. The current population of Latin America and the Caribbean is 665,974,993 "Hablando en español".


[Question] Lences wide:

Hello, sorry for posting here in issue thread.

i really need this answer for quesion: if there any possibility to change lence device frame , eq make lence frame x2 wider with the same height, but to preserve lence from distortion. Also viewport and canvas width better tobe not toched, just to simple reason : objects must be not distorted (not be wider than needed).
Please look at this screenshot http://prntscr.com/py3fre
here white cursor is whider (ellypse form, need to stay circle), but lence should be this wide (width *2)
I've looked through most methods inside cardborad-vr-display and webvr-polyfill, but yet not found solution. How it can be achieved?

Has been kinda figured:
added into DeviceInfo.prototype.getLeftEyeVisibleScreenRect = function (undistortedFrustum) {
var viewer = this.viewer;
var device = this.device;
var dist = viewer.screenLensDistance;
var eyeX = (device.widthMeters - viewer.interLensDistance) / 2;
..
var left = (undistortedFrustum[0] * dist + eyeX) / device.widthMeters;
...
return {
x: left,
y: bottom,
width: (right - left ) * viewer.lenceWidthMultiplier,
height: (top - bottom) * viewer.lenceHeightMultiplier
};
};
also in cardboardViewer added
function CardboardViewer(params) {
this.lenceHeightMultiplier = 0.84;
this.lenceWidthMultiplier = 1.5;
but maybe you' have more elegant solution. please let me know.


The dledger cluster +controller component broker failed to start

The issue tracker is used for bug reporting purposes ONLY whereas feature request needs to follow the RIP process. To avoid unnecessary duplication, please check whether there is a previous issue before filing a new one.
It is recommended to start a discussion thread in the mailing lists or github discussions in cases of discussing your deployment plan, API clarification, and other non-bug-reporting issues.
We welcome any friendly suggestions, bug fixes, collaboration, and other improvements.
Please ensure that your bug report is clear and self-contained. Otherwise, it would take additional rounds of communication, thus more time, to understand the problem itself.
Generally, fixing an issue goes through the following steps:

Understand the issue reported;
Reproduce the unexpected behavior locally;
Perform root cause analysis to identify the underlying problem;
Create test cases to cover the identified problem;
Work out a solution to rectify the behavior and make the newly created test cases pass;
Make a pull request and go through peer review;

As a result, it would be very helpful yet challenging if you could provide an isolated project reproducing your reported issue. Anyway, please ensure your issue report is informative enough for the community to pick up. At a minimum, include the following hints:
BUG REPORT

Please describe the issue you observed:

The dledger cluster +controller component broker failed to start
Kirin system, dual network card
config:
brokerClusterName=RaftCluster
brokerName=RaftNode00
dLegerGroup=RaftNode00
listenPort=30911
namesrvAddr=<IP_ADDRESS>:9876;<IP_ADDRESS>:9876;<IP_ADDRESS>:9876
storePathRootDir=/data/logs/rocketmq/node
storePathCommitLog=/data/logs/rocketmq/commitlog
enableDLegerCommitLog=true
dLegerPeers=n0-<IP_ADDRESS>:40911;n1-<IP_ADDRESS>:40911;n2-<IP_ADDRESS>:40911
dLegerSelfId=n0
sendMessageThreadPoolNums=16
enableControllerMode=true
controllerAddr=<IP_ADDRESS>:9878;<IP_ADDRESS>:9878;<IP_ADDRESS>:9878
allAckInSyncStateSet=true
aclEnable=false
autoCreateTopicEnable=true
brokerIP1=<IP_ADDRESS>
brokerIP2=<IP_ADDRESS>
start fail
java.lang.NullPointerException
at org.apache.rocketmq.broker.controller.ReplicasManager.(ReplicasManager.java:101)
at org.apache.rocketmq.broker.BrokerController.initialize(BrokerController.java:757)
at org.apache.rocketmq.broker.BrokerStartup.createBrokerController(BrokerStartup.java:230)
at org.apache.rocketmq.broker.BrokerStartup.main(BrokerStartup.java:50)

What did you do (The steps to reproduce)?

What is expected to see?

What did you see instead?

Please tell us about your environment:

Other information (e.g. detailed explanation, logs, related issues, suggestions on how to fix, etc):

FEATURE REQUEST

Please describe the feature you are requesting.

Provide any additional detail on your proposed use case for this feature.

Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?

If there are some sub-tasks involved, use -[] for each sub-task and create a corresponding issue to map to the sub-task:

sub-task1-issue-number: sub-task1 description here,
sub-task2-issue-number: sub-task2 description here,
...

@yhp353134 The dledger cluster and controller mode cannot be used simultaneously, they are mutually exclusive.
https://github.com/apache/rocketmq/pull/6195
https://github.com/apache/rocketmq/discussions/6172

@yhp353134 The dledger cluster and controller mode cannot be used simultaneously, they are mutually exclusive. #6195 #6172

thanks


Why armeria prefer @Nullable to Optional?

It's not an issue but a question, so feel free to close it if it not fit your issue policy :P.

Armeria used Optional long long ago, and then change it to xxxOrNull style API. why you prefer this?
There're many @nullable variant in different library, like jsr305, jetbrains-annotations, could you, skillful developers, share your practice which and why to use one rather than another?

Big thanks!

Armeria removed Optional from the public API.
Please refer to the previous discussion and reason #2362 #2371
One of the reasons is that Armeria supports JDK languages well. Java is the main target language of Armeria. However, we don't want to limit the scope to Java.
Kotlin supports an awesome null-safety using ?. It does not go well with Optional. Kotlin understands nullable annotations for Java libraries. https://kotlinlang.org/docs/reference/null-safety.html
For example:
val b: String? = null
println(b?.length)

There're many @nullable variant in different library, like jsr305, jetbrains-annotations, could you, skillful developers, share your practice which and why to use one rather than another?

We are also considering to adopt jetbrains-annotations. #2793 You can leave your opinion on that thread. 😀

Armeria removed Optional from the public API.
Please refer to the previous discussion and reason #2362 #2371
One of the reasons is that Armeria supports JDK languages well. Java is the main target language of Armeria. However, we don't want to limit the scope to Java.
Kotlin supports an awesome null-safety using ?. It does not go well with Optional. Kotlin understands nullable annotations for Java libraries. https://kotlinlang.org/docs/reference/null-safety.html
For example:
val b: String? = null
println(b?.length)

Thanks for your reply. It makes sense. How about dealing with pure Java code?


JDK and Ant Installed but Dita Install Gives "Error: Transformation type not defined"

Tried the following on Windows 10.
First I installed htmlhelp.exe -- all went well.
Next, I installed the JDK and path is found in CMD (Using Windows 10). JDK worked.
Next, I installed Dita and created the environmental variable and path.
Then, I tried typing "dita" in CMD to check the Dita install.
I expected Dita to be installed but instead got this error:
"C:\WINDOWS\system32>dita
Error: Error: Transformation type not defined
Usage: dita -i  -f  [options]
or: dita --propertyfile= [options]
or: dita --install [=]
or: dita --uninstall
or: dita --help
or: dita --version
Arguments:
-i , --input=   input file
-f , --format=  output format (transformation type)
--propertyfile=       load all properties from file
--install []          install plug-in from a ZIP file
--install                   reload plugins
--uninstall             uninstall plug-in with the ID
-h, --help                  print this message
--version                   print version information and exit
Options:
-o, --output=          output directory
--filter=            filter and flagging files
-t, --temp=            temporary directory"
To fix this, I tried installing ant. Ant install was successful.
I reopened the CMD and tried "dita" but got the same error.
Do I need to uninstall Dita? Is the problem because I installed Ant after Dita?
What other possible solutions are there? Are there specifications for transformations that are required at install?
The versions I installed(or tried to) are:
htmlhelp.exe
JDK: jdk-11.0.1_windows-x64_bin.exe
DITA: dita-ot-3.0.4.zip
Ant: apache-ant-1.10.5-bin.zip

Hi Radu,
Thank you for the quick reply! I have an error in my post. I was trying to
install the Dita Toolkit. Should I use a different command in the CMD to
check the install? I have not worked on any .dita files yet.
Best,
Lauren
On Thu, Dec 27, 2018, 12:23 AM Radu Coravu<EMAIL_ADDRESS>wrote:

The "Error: Transformation type not defined" error means that you need to
pass various parameters to the "dita" command in order for it to work. You
need to tell it where the DITA Map is, where the output folder is located
and what output format you need to obtain from it.
So you need to run the "dita" command something like:
dita -i path/to/map.ditamap -o path/to/outputFolder -f htmlhelp
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dita-ot/dita-ot/issues/3173#issuecomment-450102088,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ArJ1Qri0u4JQEjT4whPJn7vBMYcd6wVyks5u9INmgaJpZM4Ziab4
.

I will try "bin\dita --version"
Thank you!
On Thu, Dec 27, 2018, 12:45 AM Lauren Kaplan<EMAIL_ADDRESS>wrote:

Hi Radu,
Thank you for the quick reply! I have an error in my post. I was trying to
install the Dita Toolkit. Should I use a different command in the CMD to
check the install? I have not worked on any .dita files yet.
Best,
Lauren
On Thu, Dec 27, 2018, 12:23 AM Radu Coravu<EMAIL_ADDRESS>wrote:

The "Error: Transformation type not defined" error means that you need to
pass various parameters to the "dita" command in order for it to work. You
need to tell it where the DITA Map is, where the output folder is located
and what output format you need to obtain from it.
So you need to run the "dita" command something like:
dita -i path/to/map.ditamap -o path/to/outputFolder -f htmlhelp
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dita-ot/dita-ot/issues/3173#issuecomment-450102088,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ArJ1Qri0u4JQEjT4whPJn7vBMYcd6wVyks5u9INmgaJpZM4Ziab4
.

The install calls an error. I tried and received the following in the CMD:
"C:\WINDOWS\system32>bin\dita--version
The system cannot find the path specified."
I added the path below to the Path system variable:
C:\Program Files (x86)\dita-ot-3.0.4\bin
What am I missing for the path? The paths for the JDK and other installs
are working.
Do I need to also install XSLT processor?
On Thu, Dec 27, 2018 at 12:52 AM Lauren Kaplan<EMAIL_ADDRESS>wrote:

I will try "bin\dita --version"
Thank you!
On Thu, Dec 27, 2018, 12:45 AM Lauren Kaplan<EMAIL_ADDRESS>wrote:

Hi Radu,
Thank you for the quick reply! I have an error in my post. I was trying
to install the Dita Toolkit. Should I use a different command in the CMD to
check the install? I have not worked on any .dita files yet.
Best,
Lauren
On Thu, Dec 27, 2018, 12:23 AM Radu Coravu<EMAIL_ADDRESS>wrote:

The "Error: Transformation type not defined" error means that you need
to pass various parameters to the "dita" command in order for it to work.
You need to tell it where the DITA Map is, where the output folder is
located and what output format you need to obtain from it.
So you need to run the "dita" command something like:
dita -i path/to/map.ditamap -o path/to/outputFolder -f htmlhelp
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dita-ot/dita-ot/issues/3173#issuecomment-450102088,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ArJ1Qri0u4JQEjT4whPJn7vBMYcd6wVyks5u9INmgaJpZM4Ziab4
.

That worked -- thank you!
On Thu, Dec 27, 2018 at 9:26 PM Radu Coravu<EMAIL_ADDRESS>wrote:

As you state you already have the "dita-dir\bin" folder in the OS path
system variable, you just need to run "dita --version" without prepending
it with "bin".
But your first step should be to "cd" to "C:\Program Files
(x86)\dita-ot-3.0.4\bin" and run the "dita --version" from there to see if
it works.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dita-ot/dita-ot/issues/3173#issuecomment-450292668,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ArJ1QteEXMKIbBAjAW9nZAP9kVxbH8Bvks5u9atrgaJpZM4Ziab4
.


Edit list items

Is your feature request related to a problem? Please describe.
In the next release (2019-09) it's possible to create lists and add new item. But there's no possibility yet to edit or delete list items or to reorder them.
Describe the solution you'd like
Update list-item-form to edit.
Additional context
This feature needs the implementation of the StringLiteral form component to support multi-language inputs. I already started with a prototype of this form in knora-ui-playground

In the list editor we read the project shortcode from the IRI. In some cases (e.g. BEOL) the IRI doesn't contain the shortcode and we get some 400-errors from the API. We have to improve the existing solution. (#57)

The input field of label has a default max length of 16. This should be fixed by implementing StringLiteral-input field

We have to clean up the file / component structure for the lists.

list.component contains a list of lists in expansion panels (mat-accordion module)
the mat-accordion contains the list-items.component done with recursive list-item.component and list-item-form.component to add / edit list items (an item is the same as node)
additional there should be a create / edit button to create the list or edit the list-info itself. list-info-form.component opens in mat-dialog.

Todo:

[ ] Fix issue with project id; we can't use the shortcode to create the iri Comment 524880326
[ ] list-info-form: implement stringLiteral and remove language selection
[ ] clean up file / component structure; make it simpler
[ ] update dialog component: remove unused list sections
[ ] language support for stringLiterals; at the moment we read the first item only
--> what's about one language selector at the top?

Edit list items (rename) is not yet possible: We have to wait for dhlab-basel/Knora#1387
Reposition of list item is not yet possible: We have to wait for dhlab-basel/Knora#1388
Delete list is not yet possible: We have to wait for dhlab-basel/Knora#1389

I suggest to prepare everything in Kuirl with status 'disabled' until Knora admin api supports the list editing. Don't forget to update the Knora-ui core module listsService

@kilchenmann should we move this issue to the next milestone 10-2019??

@flavens: Not sure. Let's see how fast @subotic will be with implementing the knora api part to edit list nodes. Otherwise we can still postpone it...

some tasks have been completed + there are some opened issues in knora-api related to this one and already on YouTrack #1387, #1388 and #1389