Contact JetBlue Customer Service +1-833-730-7587

Aka.ms link name
https://ai4earth.microsoft.com/forums/general-discussion/71341807-d04d-ef11-b4ad-6045bd03a369
Category (Optional. Select None to auto-select)
None

Changing your name on a JetBlue Airlines ticket involves specific steps to ensure accuracy and compliance. To request a name change, contact JetBlue Airlines customer service at +1-833-730-7587. Here's a brief overview of the process:
Contact JetBlue Customer Service: Dial the provided number and explain that you need to change the name on your JetBlue Airlines ticket.
Provide Booking Details: Have your booking reference number ready to provide to the customer service representative.
Submit Documentation: You'll likely need to submit official documentation supporting the name change, such as a marriage certificate or court order.
Pay Fees (if applicable): Depending on the fare rules and timing of your request, there may be fees associated with the name change.
Confirm Changes: Once the name change request is processed, ensure that your ticket reflects the updated name before your travel date.
Completing these steps promptly and accurately is crucial to avoid any issues or delays during your travel with JetBlue Airlines.
Add Passenger Name on JetBlue Ticket
To add a passenger name on a JetBlue ticket, contact JetBlue Airlines customer service at +1-833-730-7587. Provide your booking details and the accurate information of the additional passenger. Depending on JetBlue's policies, there may be fees involved, and you may need to submit documentation for verification.
+1-833-730-7587 JetBlue Airline Ticket Name Change Marriage · Customer Self-Service (microsoft.com)
+1-833-730-7587 JetBlue Airline Ticket Name Change Marriage · Customer Self-Service (microsoft.com)
+1-833-730-7587 JetBlue Airline Ticket Name Change Marriage · Customer Self-Service (microsoft.com)


⚠ ClamAV has degraded performance

In a97eedb, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 88 ms

Resolved: ClamAV performance has improved in 6ca5ee7.


[Feature Request] Product Data Variables

Split Product Data Variables into its own Jinja template for easier access across files

Issue is too related to #23. Closing as duplicate.


Remove force unwrap, for fix crush

Hi. I know you haven't updated the project in a while, but you seem to still be online. I found a crashing bug in my personal project and realized that it's due to incorrect unwrap optionals. I fixed the code. It will be great to see a new release of the SDDownloadManager.
Best regards Manzick

Hi @manzick, thanks for this PR!
I will review this and also do additional changes if needed to fix the crashes. It has been a while I have worked on this project, and your PR has motivated me to release it. 😅

I have released 2.0.0 which addresses the crashes and also has many improvements! Thanks


fix(workflow): remove test badge

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

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


Enable linux_aarch64

Hi! This is the friendly automated conda-forge-webservice.
I've started rerendering the recipe as instructed in #2.
If I find any needed changes to the recipe, I'll push them to this PR shortly. Thank you for waiting!
Here's a checklist to do before merging.

[ ] Bump the build number if needed.

Fixes https://github.com/conda-forge/cuda-tools-feedstock/issues/2

@conda-forge-admin , please re-render

Thanks John!


weekly rule DST issue

Hi,
I added some specs for the following edge case where the calculation of the next occurrences returns faulty values.
The base of this issue is IceCube::WeeklyRule.realign when an occurrence happens within a DST time switch. For example on 26th April 2024 00:00 -> 01:00. Realign will change the start_time of e.g. 22th May 2022 00:20 to 26th April 2024 01:20 and then the starting hour is wrong. The result is occurrences with the time 01:20 instead of 00:20.
Thanks
Lars

Hi @larskuhnt,
Thank you for your contribution ... this looks great! Just a couple of comments, but otherwise looks spot on. 👍🏻

Don't worry about fixing the linting issues ... that is resolved on #552 which I'll merge first.
I'm just waiting on @seejohnrun updating my access so I can actually fix things.

Hi @pacso,
your comment https://github.com/ice-cube-ruby/ice_cube/pull/551#discussion_r1580097086 was very helpful as it showed a flaw in my approach to fix this issue. I added some more specs now and decided to realign the time to a day before the DST switch for this special case to keep the timezone information. The only issue with this approach could be when the DST switch happens on a monday/sunday so that the realigned time is in the previous week. But I am not sure about that.

@larskuhnt - could you please pull master and see whether this fixes all of the tests?

@pacso I merged master and the specs are green on my side.

@larskuhnt - Could you resolve the linting errors?

@pacso all checks pass now

Amazing, thank you! I'll do a proper review either at lunch or after work and get this merged in 👍🏻


onBufferedAmountLow is annoying

I made a wrapper around dc.send that automatically schedule the message to be send once onBufferedAmountLow event received.
But the problem is that this event not always get invoked as I expected thus leaving messages not being able to send.
class DataChannelWrapper {
    private:
        int requestCount{};

        std::queue<std::string> messageQueue;
    public:
        std::shared_ptr<rtc::DataChannel> dc;

        void onBufferedAmountLow();

        bool send(std::string message);
};

inline bool DataChannelWrapper::send(std::string message) {
    if (dc)
    {
        if(requestCount == 0) {
            bool status = dc->send(reinterpret_cast<rtc::byte *>(message.data()), message.size());

            if(status) {

                requestCount++;
            }

            return status;
        } else {
            requestCount++;

            // Schedule
            messageQueue.push(message);

            return true;
        }
    } else {
        std::cout << "Shared Pointer is null" << "\n";

        return false;
    }
}

inline void DataChannelWrapper::onBufferedAmountLow() {
    std::cout << "onBufferedAmountLow reached" << "\n";

    if(messageQueue.empty()) {
        std::cout << "Empty Message Queue" << "\n";

        return;
    }

    auto message = messageQueue.front();

    dc->send(reinterpret_cast<rtc::byte *>(message.data()), message.size());

    std::cout << "Sent a message from Queue" << "\n";

    messageQueue.pop();

    requestCount--;
}

What can be done to fix this?

The WebRTC bufferedamountlow event does not actually work that way, as there is no guarantee it will be called after send(). It should actually be called when bufferedAmount goes back under bufferedAmountLowThreshold (default 0), as the WebRTC specification says:

bufferedamountlow: The RTCDataChannel object's bufferedAmount decreases from above its bufferedAmountLowThreshold to less than or equal to its bufferedAmountLowThreshold.

So in the end, it boills down to how the browser calculates bufferedAmount. In practice, a browser is free to implement sending as it pleases, so it may not increment bufferedAmount if the message can be sent immediately, therefore send() won't necessarily result in a bufferedamountlow event (which is subject to change, see this bug for instance).
Therefore, the correct usage of the onBufferedAmountLow callback is as follows (provided bufferedAmountLowThreshold is 0):

When a new message should be sent, put it in the queue and send queued messages until  bufferedAmount() > 0.
When the onBufferedAmountLow callback is called, send queued messages until  bufferedAmount() > 0 (if the number of messages to send is big enough, you might want to stop at some point and schedule sending more a bit later so the browser event loop is not stuck for too long).

@paullouisageneau
I understood your idea, but

When a new message should be sent, put it in the queue and send queued messages until bufferedAmount() > 0
When the onBufferedAmountLow callback is called, send queued messages until bufferedAmount() > 0

This sounds asyncish to me.  When I want to send a new message, I should put it in queue, but when should I front and pop from queue?
Stackoverflow posts also had mentioned the difficulty of onBufferedAmountLow   and they used setTimeout with specific ms to send messages and it looks like your idea goes same way.

This sounds asyncish to me. When I want to send a new message, I should put it in queue, but when should I front and pop from queue?

What do you mean by asyncish? You should pop from the queue both after you put a new message in the queue, and when onBufferedAmountLow is called.
The pseudo code is rather simple:
queue<string> q;

void flush() {
    while (!q.empty() && dc->bufferedAmount() == 0) {
        dc->send(move(q.front()));
        q.pop();
    }
}

void send(string message) { // call this when you want to send a message
    q.push(move(message));
    flush();
}

dc->bufferedAmountLowThreshold(0);
dc->onBufferedAmountLow(flush);

Stackoverflow posts also had mentioned the difficulty of onBufferedAmountLow and they used setTimeout with specific ms to send messages and it looks like your idea goes same way.

The JavaScript API is awkwardly designed, but it's not that difficult. Indeed, setTimeout can be a useful refinement in the specific case you want to send a big and synchronous source of data as fast as possible.
In that case, there is no "a new message should be sent" situation, you always want to send and everything is virtually in the queue from the start. Therefore, the "send queued messages until bufferedAmount() > 0" loop might freeze the browser event loop for a while if the queue is big and bufferedAmount never increases because the throughput is very high.
A solution to this issue is to limit the maximum amount of data the loop can send in one call, and schedule it to be called again after a short delay, giving a chance to the event loop to run.

According to your pseudo code, I don't see onBufferedAmountLow get chance to send any messages since the flush invocation of send method grab that chance.

the "send queued messages until bufferedAmount() > 0" loop might freeze the browser event loop for a while if the queue is big and bufferedAmount never increases because the throughput is very high.

By the way, I'm sending 64k chunks so is this kind of throttling needed here?

According to your pseudo code, I don't see onBufferedAmountLow get chance to send any messages since the flush invocation of send method grab that chance.

If dc->bufferedAmount() > 0, flush() will do nothing, an actual send will happen only when onBufferedAmountLow is called (it will happen when dc->bufferedAmount() == 0).

By the way, I'm sending 64k chunks so is this kind of throttling needed here?

It is irrelevant of the size of messages. It's needed only if your use case is sending a huge file as fast as possible.

@paullouisageneau  I used your code as-it's except with better variable names.  I see  that onBufferedAmountLow never get called and that only 1 message get out.
while(!messageQueue.empty() && dc && dc->bufferedAmount() > 0)
I suspect dc->bufferedAmount() > 0 might be causing this or dc->bufferedAmountLowThreshold(0)

onBufferedAmountLow get called if I send messages without your code. Just sending messages without queueing aka straightly.

@paullouisageneau
It works now and feel somewhat more performant. Any idea why It become faster?
Closing.

Any idea why It become faster?

Probably because using the callback properly like this ensures you send as soon as possible, so there is no idle time.


GitList don't work on php7.4 and php8

I've test with multiples docker image.
When I run php 7.4, and php8, Twig as a fatal error.
Maybe Gitlist need to update Twig in composer.json
Are you ok ?
Great Job, It work fine on php7.3 !

If you need details, here's the error :
PHP Fatal Error:
Unparenthesized `a ? b : c = d : e` is not supported. Use either `(a ? b : c) ? d : e` or `a ? b : (c ? d : e)` in /usr/share/webapps/gitlist/vendor/twig/twig/lib/Twig/Node.php on line 42.

In deed, I have the same pb

Aye, that has popped up once I got the folder permissions right (PHP 8.0.3).

Hi, this should be fixed in #880 . Looking forward to your feedback

Hi, for those interested, @fox34 mentioned #880 fixes the issue with PHP8

It should now: https://github.com/klaussilveira/gitlist/releases/tag/1.1.0


Consider bumping targetSdk to 33

Summary
It appears Amplitude's Android implementation reads the Advertising ID. With the release of Android 13, apps need to declare the com.google.android.gms.permission.AD_ID permission if they choose to read the Advertising ID.
Please see: https://developer.android.com/about/versions/13/behavior-changes-13#ad-id
However, according to that link:

If your app uses SDKs that declare the AD_ID permission in the library's manifest, then the permission is merged with your app's manifest file by default. In this case, you don't need to declare the permission in your app's manfiest file.

Motivations
If an app just happens to depend on Amplitude but not rely on the Advertising ID anywhere else in their app, I feel that the Amplitude SDK should take care of setting the proper permissions out of the box so that the consuming app should not have to worry about explicitly specifying the permission within their app's AndroidManifest.xml
For example, the Firebase Analytics library depends on com.google.android.gms:play-services-ads-identifier which happens to specify the permission in its AndroidManifest.xml. For an app that depends on the Firebase Analytics library, the generated merged manifest of the Application will include the permission implicitly declared by the Firebase Analytics library.

Hi @mhernand40, thanks for choosing Amplitude. The ad_id functionality is not needed for all customers hence the permission as well. When creating SDK we are trying to make as less assumptions for customers as possible. The permissions are not added to allow more flexibility.


How to remove --routines option from mysqldump?

System information:

Operating system (distribution) and version: Arch Linux Kernel 5.1.8-arch1-1-ARCH
DBeaver version 6.0.4

Connection specification:

Database name and version: Server MySQL 5.7 - Client MariaDB 10.3

Describe your question:
When dumping a database the client always adds the --routines flag to mysqldump.
This is problematic with the above client server combination, see https://jira.mariadb.org/browse/MDEV-17429
I found the corresponding code here: https://github.com/dbeaver/dbeaver/blob/6ebe0bcc6d531508bdc5dffaf16a50a7a3bade75/plugins/org.jkiss.dbeaver.ext.mysql.ui/src/org/jkiss/dbeaver/ext/mysql/tools/MySQLExportWizard.java#L161-L163
How can I remove the option from the command?

I agree. At the very least, there could be another Settings checkbox for No routines.

I opened an PR to add a settings option. See https://github.com/dbeaver/dbeaver/pull/36416


Updated example app so definitions appear rather than NULL

I dont get why it is needed, running example app and I dont see any NULL can you point out where NULL is shown?

After submitting this pull request I noticed this was also submitted as an issue: https://github.com/rochacbruno/flasgger/issues/29
If you run the example_app.py file as is, the issue appears on:
http://<IP_ADDRESS>:5000/apidocs/index.html?url=/v1/spec#!/users/post_v1_users

http://<IP_ADDRESS>:5000/apidocs/index.html?url=/v1/spec#!/users/get_v1_users_team_id

If the code is changes as submitted it shows:


Add CHANGELOG.md

It would be really helpful if there were a CHANGELOG to be able to see at a glance what was added / fixed / changed in each version. Thanks! :smiley:

Done, thanks for the suggestion!


Inlay hints does not work on Windows

I have tested the same configuration for windows with wsl2 and the inlay hints do not work. I am using the windows version of neovim from the release page in contrast to the appimage.
Configuration:
use "simrat39/rust-tools.nvim"
use "neovim/nvim-lspconfig"

require("rust-tools").setup({})

Windows:
NVIM v0.6.1
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Compiled by runneradmin@fv-az152-430

Features: -acl +iconv +tui
See ":help feature-compile"

   system vimrc file: "$VIM\sysinit.vim"
  fall-back for $VIM: "C:/Program Files/nvim/share/nvim"

Run :checkhealth for more info

WSL2 Ubuntu:
NVIM v0.6.1
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Compilation: /usr/bin/gcc-11 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DNVIM_TS_HAS_SET_MATCH_LIMIT -O2 -g -Og -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wmissing-prototypes -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fno-common -fdiagnostics-color=always -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -I/home/runner/work/neovim/neovim/build/config -I/home/runner/work/neovim/neovim/src -I/home/runner/work/neovim/neovim/.deps/usr/include -I/usr/include -I/home/runner/work/neovim/neovim/build/src/nvim/auto -I/home/runner/work/neovim/neovim/build/include
Compiled by runner@fv-az87-780

Features: +acl +iconv +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "
/home/runner/work/neovim/neovim/build/nvim.AppDir/usr/share/nvim"

Run :checkhealth for more info

Any fixes for this? Would prefer to continue using the Win version of neovim.

Inlay hints don't show up for me, either. I have no idea why. Everything else works great. But I am on a pure WSL2 setup (wsl directory, using all linux programs like linux nvim and linux rust-analyzer). I don't know what's going on. :(

Try and update both your rust analyser and plugins

Try and update both your rust analyser and plugins

I just tried that. Still doesn't work.
I just compiled rust-analyzer from source. and i updated all plugins. I am on pure WSL2. Should act the exact same as linux. What could be the problem?
@simrat39

nvim version
:version
NVIM v0.7.0-dev+1341-g79dcd045d
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Compilation: /usr/bin/gcc-11 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DNVIM_TS_HAS_SET_MATCH_LIMIT -DNVIM_TS_HAS_SET_ALLOCATOR -O2 -g -Og -g -Wall -Wextra -pedantic -Wno-unused-parameter -Ws
trict-prototypes -std=gnu99 -Wshadow -Wconversion -Wdouble-promotion -Wmissing-noreturn -Wmissing-format-attribute -Wmissing-prototypes -Wimplicit-fallthrough -Wsuggest-attribute=pure -Wsu
ggest-attribute=const -Wsuggest-attribute=malloc -Wsuggest-attribute=cold -Wvla -fstack-protector-strong -fno-common -fdiagnostics-color=always -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOUR
CE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -I/home/runner/work/neovim/neovim/build/config -I/home/runner/work/neovim/neovim/src -I/home/runner/work/neovim/ne
ovim/.deps/usr/include -I/usr/include -I/home/runner/work/neovim/neovim/build/src/nvim/auto -I/home/runner/work/neovim/neovim/build/include
Compiled by runner@fv-az243-580

Features: +acl +iconv +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/share/nvim"

I'm very new to the nvim/vim community with that being said, @lucypero do you get the commands that come with rust-tools for e.g :RustSetInlayHints?

I'm very new to the nvim/vim community with that being said, @lucypero do you get the commands that come with rust-tools for e.g :RustSetInlayHints?

yes. that one in particular doesn't do anything, though.

Debian is equally ineffective
Linux version 5.10.0-13-amd64<EMAIL_ADDRESS>(gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.106-1 (2022-03-17)

I'm very new to the nvim/vim community with that being said, @lucypero do you get the commands that come with rust-tools for e.g :RustSetInlayHints?

yes. that one in particular doesn't do anything, though.

from logs
[ERROR rust_analyzer::dispatch] unknown request: Request { id: RequestId(I32(120)), method: "textDocument/inlayHint", ...'

Due to rust-analyzer changes, please update it to the latest version (and the plugin as well) and see if the issue persists

@simrat39 updating rust-analyzer and rust-tools fixed this issue. P.S if having trouble installing rust-analyzer from source try updating cargo 😉

my current version is rust-analyzer 24cf95762 2022-04-24 devand still can't get it to work, very odd, even no logs, I need to debug


Add elixir based integration test

Elixir (erlang) seems to use suboptimal representation for the TCP send buffer. The buffer to read from in tcp_sendmsg is not in the first iov segment and it ends up being in the last segment. Tcp_recvmsg seems unaffected.
In a previous PR I added support for tracking other segments, this PR just adds a test.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 47.29%. Comparing base (c04a1e7) to head (f9ab1ec).

Additional details and impacted files
@@             Coverage Diff             @@
##             main     #938       +/-   ##
===========================================
- Coverage   75.74%   47.29%   -28.45%
===========================================
  Files         131      131
  Lines       10125    10125
===========================================
- Hits         7669     4789     -2880
- Misses       1938     4998     +3060
+ Partials      518      338      -180

Flag
Coverage Δ

k8s-integration-test
?

oats-test
?

unittests
47.29% <ø> (+0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Intro to Python Chaper

Purpose/implementation Section
What changes are being implemented in this Pull Request?
First draft of the "Intro to Python" chapter.
What was your approach?
I start with an introduction to Python, then touch on the main differences between R and Python, then talk about the major differences in Python for R users, which are mainly drawn from Primer on Python for R Users. Importantly, I briefly talk about OOP and classes, giving a small code snippet of a class in Python.
What GitHub issue does your pull request address?
This PR addresses https://github.com/datatrail-jhu/python/issues/2
Tell potential reviewers what kind of feedback you are soliciting.
Open to any feedback or comments!
New Content Checklist

[ ] New content/chapter is in an Rmd file with this kind of format and headers.

[ ] New content/chapter contains Learning Objectives and are in the correct format.

[ ] Bookdown successfully re-renders and any new content files have been added to the _bookdown.yml.

[ ] Spell check runs successfully in Github actions style-n-check).

[ ] Any newly necessary packages that are needed have been added to the Dockerfile and image.

[ ] Images are in the correct format for rendering.

[ ] Every new image has alt text and is in a Google Slide.

[ ] Each slide is described in the notes of the slide so learners relying on a screen reader can access the content. See https://lastcallmedia.com/blog/accessible-comics for more guidance on this.

[ ] The color palette choices of the slide are contrasted in a way that is friendly to those with color vision deficiencies.
You can check this using Color Oracle.

This looks great! I've left a few specific comments inline. A few additional questions:

I couldn't see the two png files being referenced in the markdown. Should they be removed?
Maybe we can expand on the reason for using Python or when to stick with R?

I was using VSCode for the writing part, but since have switched to RStudio as my IDE and created a .Rproj file to facilitate my workflow. I'll look into those two png files and see if they are necessary!
100%. I can incorporate the knowledge from this video into this chapter.

NOTE to myself:
Get rid of the curly brackets around the python.
Delete the R from .Rmd to make it a .md file
Delete all knitr code chunks
Replace the ottrpal image part with Till's syntax for including images.

@tillahoffmann I've made more changes to 03-intro-to-python.md and committed that file. However, I'm not sure where these files came from:

.ipynb_checkpoints/03-intro-to-python-checkpoint.md
docs/03-intro-to-python.md
02-chapter_of_course_files/figure-html/unnamed-chunk-2-1.png
02-chapter_of_course_files/figure-html/unnamed-chunk-3-1.png

Is it safe to delete these files?

Let's delete the .ipynb_checkpoints directory and add it to the .gitignore.
Let's delete the python.Rproj and add *.Rproj to the .gitignore.
Regarding the docs/03-intro-to-python.md, I'm not sure how that was created. Maybe @cansavvy has an idea?
Regarding the _bookdown_files, I'll also defer to @cansavvy.

Let's delete the .ipynb_checkpoints directory and add it to the .gitignore.
Let's delete the python.Rproj and add *.Rproj to the .gitignore.
Regarding the docs/03-intro-to-python.md, I'm not sure how that was created. Maybe @cansavvy has an idea?
Regarding the _bookdown_files, I'll also defer to @cansavvy.

Totally agree on getting rid of the .ipynb_checkpoints files and adding to the gitignore.
The .Rproj file is not something automatically generated (I don't think) so should just be able to delete and that will be it.
docs and _bookdown_files are what are ultimately published from for the website.

Following changes have been made:

Delete .ipynb_checkpoints/ and add it to the .gitignore
Delete python.Rproj and add to .gitignore


fix fix bug when replay restore with reserve dynamic partition cause OBSERVER down

when replay restore a table with reserve_dynamic_partition_enable=true, must registerOrRemoveDynamicPartitionTable with isReplay=true, or maybe cause OBSERVER can not replay restore auditlog success.
Proposed changes
cherry-pick : #https://github.com/apache/doris/pull/17326
Problem summary
Describe your changes.
Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run COMPILE


netty merge the ssl handshake message

When a link is set up between the client and the server, during the SSL handshake, Netty combines the SSL handshake messages and sends them.
Like this:

netty merge these message:
Server Hello/Certificate/Certificate Request/Server Key Exchange/Server Hello Done
But I use the jdk SSLServerSocket, these messages will send one by one:

The reason for this problem is that the client buffer is very small, and message merging causes SSL handshake failure.
Netty version 4.1.63
JVM version 1.8.0_302
OS version linux

Do I understand it right that the receive buffer on the client-side is too small to fit the merged messages from the server?

Yes. you are right.

Do I understand it right that the receive buffer on the client-side is too small to fit the merged messages from the server?

Yes. you are right. Is there a way to send messages separately?

I think your client is buggy.
The SslHandler does not have a configuration option for working around this.
You could insert a ChannelOutboundHandler in front of the SslHandler that will add a flush after every write, unless the SSL handshake has completed (you can add a listener to the SslHandler.handshakeFuture to flip an AtomicBoolean or something like that, for the purpose of notifying your outbound handler).
That should cause each message in the SSL handshake to be sent as an individual message.

I try to insert a ChannelOutboundHandler in front of the SslHandler, but didn't work.
Is it possible for the SSLhandler to provide a configurable parameter for this scenario?
It is too complicated to use the socket of JDK to implement the server. My client is an IoT device and has a small memory.

Like @chrisvest said this is a bug on the client side... It must be able to handle multiple records in one input buffer.


[NPM] Fix Dockefile

What does this PR do?
Fixes this warning when running inv process-agent.build-dev-image:
 1 warning found (use --debug to expand):
 - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 9)

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


This flow also seems to need a resource parameter, which is not documented on this page.

When following the guidelines on this page, following error occurs:
AADSTS900144: The request body must contain the following parameter: 'resource'
This 'resource' parameter is the ID of the app published in Azure AD, and should be added to the body.
(Or I missed something else, but this is not clear to me either then).

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: b3eac288-4ddd-1099-1c86-885aa42a566f
Version Independent ID: 190585ca-8337-0644-2182-75b77f53c175
Content: Sign in with resource owner password credentials grant - Microsoft identity platform
Content Source: articles/active-directory/develop/v2-oauth-ropc.md
Service: active-directory
Sub-service: develop
GitHub Login: @rwike77
Microsoft Alias: ryanwi

hpsin, I used the PowerShell Invoke-RestMethod commandlet to following URL:
https://login.microsoftonline.com/$TenantID/oauth2/token
$TenantID is a the PowerShell variable which holds the ID of our tenant.
The URL I keep in variable:
$RequestAccessTokenUrl = "https://login.microsoftonline.com/$TenantID/oauth2/token"
The Header for the request is:
$Headers = @{"Content-Type" = "application/x-www-form-urlencoded"}
The body of the request:
$Body = "client_id=$ClientId&scope=$Scope&username=$UserName&password=$Pwd&grant_type=password&resource=$ResourceId"
In this:
$ClientId: the Application ID of the published application (MS Graph API) in Azure AD.
$Scope: The scope (permissions) of the published application.
$Username and $Pwd: The user accessing the API
$ResourceID: The resource ID, for which I opened this issue :-) No description of this one in this document.
The actual request is then:
$Response = Invoke-RestMethod -Method Post -Uri $RequestAccessTokenUrl -Body $Body -Headers $Headers
The AccessToken I receive as:
$AccessToken = $Response.access_token
Hope this make things clear :-)

Ah - you're not using the v2 endpoint 😊
https://login.microsoftonline.com/$TenantID/oauth2/token
You need to use /oauth2/v2.0/token, per docs.

@Cubercoding , I believe your issue was addressed.  Closing this.  #please-close


Futures.addCallback deprecated

if this is already deprecated, why does the azure portal still give out code that is already deprecated? also, what should we do to replace the deprecated code?
Futures.addCallback(future, new FutureCallback<ServiceFilterResponse>() {
@Override
public void onFailure(Throwable e) {
resultFuture.setException(e);
}
            @Override
            public void onSuccess(ServiceFilterResponse response) {
                runOnUiThread(new Runnable() {

                    @Override
                    public void run() {
                        if (mProgressBar != null) mProgressBar.setVisibility(ProgressBar.GONE);
                    }
                });

                resultFuture.set(response);
            }
        });

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 7041142f-6df3-4e70-b1b9-22b2f13f4966
Version Independent ID: 4a9dc512-f04b-fd66-5c25-b2095522b497
Content: Create an Android app on Azure App Service Mobile Apps
Content Source: articles/app-service-mobile/app-service-mobile-android-get-started.md
Service: app-service-mobile
GitHub Login: @conceptdev
Microsoft Alias: crdun

Hi @zzulueta, thanks for the feedback! We are currently investigating and will update you shortly.

Hello, I'm getting some issues like this one of @zzulueta.
"error: cannot access ListenableFuture" is shown in my Android Studio, and when I come to investigate it says that the method getTable().insert() was deprecated too, but it's the exemple given in Azure's Quick Start Guide. I'm lost and can't find a great and clear documentation of how to implement Azure's cloud-based service. I need this to finish a college project (and graduate). I'm couting on you! Please, help me up!

can you send me a copy of your code via github? kinda hard to determine what the cause is without any background:)

@Grace - I have made the code from the azure server work for the ToDoItem sample. but I also did a couple of things to make the app run in my Samsung:

I updated the app gradle to the latest version
implementation 'com.microsoft.azure:azure-mobile-android:3.4.0@aar'
in the project gradle i added "google()" not only in the buildscript but also in the allprojects{}
the app wont compile and run and would give compilation errors. i went to stackoverflow and found this link: https://stackoverflow.com/questions/49512629/android-studio-error-default-interface-methods-are-only-supported-starting-with

I added this:
android {
...
compileOptions {
sourceCompatibility JavaVersion.VERSION_1_8
targetCompatibility JavaVersion.VERSION_1_8
}
...
}
But for some reason, once the app has run, I removed it and the issue is no longer there?!

@zzulueta , my code is literally the code on the quick start guide on Azure's menu.
TodoItem item = new TodoItem();
item.Text = "Awesome item";
mClient.getTable(TodoItem.class).insert(item, new TableOperationCallback() {
public void onCompleted(TodoItem entity, Exception exception, ServiceFilterResponse response) {
if (exception == null) {
// Insert succeeded
} else {
// Insert failed
}
}
});

No one will answer this anymore?

@zzulueta We are happy to hear that you ultimately got your project and we apologize for the inconvenience that you encountered trying to reach this point. Since your issue is resolved, we will archive this issue and move towards handling the issue further in issue #16158. We have requested the doc author to provide an update on that issue in case you want to follow along.

Gui - i mentioned my steps to run the code have you tried them ?
On Sat, 6 Oct 2018 at 6:05 AM GuiPelegrini<EMAIL_ADDRESS>wrote:

No one will answer this anymore?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/16111#issuecomment-427511181,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Anij6sZlm82ihSgiK588fWmTZ6wYTfIWks5uh9ePgaJpZM4XGNjb
.


Fixes for Markdown CSS

This overrides some of the global bokeh CSS properties for the Markdown pane ensuring appropriate padding and margins for tables and lists and improved styling for tables.
Fixes #323

Codecov Report

Merging #328 into master will increase coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #328      +/-   ##
==========================================
+ Coverage   89.53%   89.54%   +0.01%
==========================================
  Files          84       84
  Lines        6784     6792       +8
==========================================
+ Hits         6074     6082       +8
  Misses        710      710

Impacted Files
Coverage Δ

panel/pane/markup.py
93.75% <100%> (+0.69%)
:arrow_up:

panel/tests/test_interact.py
100% <100%> (ø)
:arrow_up:

panel/viewable.py
83.83% <100%> (ø)
:arrow_up:

panel/pane/tests/test_markup.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f90d5c2...8369937. Read the comment docs.

Codecov Report

Merging #328 into master will increase coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #328      +/-   ##
==========================================
+ Coverage   89.53%   89.54%   +0.01%
==========================================
  Files          84       84
  Lines        6784     6792       +8
==========================================
+ Hits         6074     6082       +8
  Misses        710      710

Impacted Files
Coverage Δ

panel/pane/markup.py
93.75% <100%> (+0.69%)
:arrow_up:

panel/tests/test_interact.py
100% <100%> (ø)
:arrow_up:

panel/viewable.py
83.83% <100%> (ø)
:arrow_up:

panel/pane/tests/test_markup.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f90d5c2...8369937. Read the comment docs.


Support for Atcoder

So, the workflow is pretty much the same.
Instead of Codeforces API i use, Kenokooo API for Atcoder to fetch all submissions, and then use BeautifulSoup to Scrape it.
Some of the changes i did

Added a AtcoderWorkflow which does the same job as of CodeforcesWorkflow
the get_user_submissions has an extra key now, which is "platform" because Readme can't be generated for all platforms in the same way, for e.g Atcoder lacks a Tag system for problems

Some more things like arguments etc, you can review them as well
Here is a sample repo

This is just amazing @s-i-d-d-i-s! Thank you so so much for working over it! Taking a look at the proposed changes :)

Hey @s-i-d-d-i-s! Thanks a ton again for contributing! The changes look all fine. I have some bandwidth to work on it today so I'll merge your changes and refactor things a bit to extract out a common workflow interface. I just might revert the changes for the Codeforces page limit at the moment to keep it in parity with the actual submissions page on Codeforces but will bring it back if more people complain, maybe with an additional --all argument. Hope that works?

yeah sure!


Multiple octomap views generated and octomap flipped

Hi!
So after solving this issue, I was able to run all the launch files/ nodes and started to analyze the Kinect fusion process. However, I am not able to understand why multiple octomaps in different views are being generated, and one view has an octomap which is flipped.
I am adding the different steps of the process and the views in Gazebo and RViz so you can get a better visualisation of the problem.

After launching Gazebo and moveit_planning_execution.launch
Note: The Octomap is straight and properly generated wrt to the object placed in Gazebo. The first Octomap isn't generated by the YAK package and was created separately to check if the Kinect camera is working in simulation properly.

After roslaunch yak launch_gazebo_robot.launch
Note: Multiple octomaps are generated in all 3 directions. Even though there is just one sphere in the view as shown in the earlier picture. Could this be because the tracking isn't working?

After roslaunch nbv_planner octomap_mapping.launch

Afterrosrun nbv_planner exploration_controller_node
Note-

The raycasting generates all the rays and hit rays near to the robot base itself. Is this how its supposed to happen?
The robot doesn't move as its supposed to when running the exploration_controller_node
I receive a warning message which is as follows:

[ INFO] [1530883513.318211330,<PHONE_NUMBER>00]: Unable to solve the planning problem
[ERROR] [1530883513.318379591,<PHONE_NUMBER>00]: Couldn't compute a free-space trajectory
[ INFO] [1530883513.318441594,<PHONE_NUMBER>00]: Pose index: 28
[ INFO] [1530883513.318512142,<PHONE_NUMBER>00]: Trying next best pose: position:
  x: -0.218574
  y: 0.793138
  z: 0.303502
orientation:
  x: 0.77676
  y: 0.211575
  z: 0.155896
  w: 0.572343

[ERROR] [1530883513.318788475,<PHONE_NUMBER>00]: Found empty JointState message
[ WARN] [1530883513.318873192,<PHONE_NUMBER>00]: It looks like the planning volume was not specified.

On the MoveIt! terminal i get the following error message [ WARN] [1530883644.819044064,<PHONE_NUMBER>00]: The weight on position constraint for link 'camera_depth_optical_frame' is near zero.  Setting to 1.0.

I apologise for the long message. Just wanted to describe stuff in a better way as I am not able to pinpoint what exactly is causing this error.
Thanks in advance,
Aaditya Saraiya
@Levi-Armstrong

Thanks for this write-up!  I will review this and get back to you.

@AustinDeric Thanks a lot. Looking forward to your comments on the same.

Are the redundant octomaps all created at the same time, or sequentially? If the pose of the TSDF reconstruction volume changes after mapping starts then it behaves as if objects in the scene have moved and might start mapping new voxels as occupied. If they're being drawn simultaneously then it's very mysterious: haven't seen that behavior before!
(re: 1) The origins of the rays are supposed to be placed in a spherical pattern around the center of the volume. You should be able to control where they're created by moving the volume, though based on your picture it looks like they might not be related to the pose of the volume correctly.
(re: 2, 3, and possible 4) The motion planning problem is kind of weirdly constrained, as a workaround to prevent the robot from pointing the camera away from the volume to be reconstructed while moving between poses. It creates a point some distance away from the front of the camera (about 50cm, offhand), then tries to keep that point within the boundary of the volume. Since the motion planning uses a RRT strategy, at best it finds a solution after a fairly long time, and at worst it completely fails to plan the motion and throws errors like the first few shown, though I'm not 100% sure what's going on with the last two. It should iterate through candidate poses in order of which ones expose the most unknown voxels in the volume until it finds a motion it can accomplish.

Hi @schornakj. Thanks for your response.
Are the redundant octomaps all created at the same time, or sequentially?

Yes, there is like a 2-3 seconds pause before these are created. I won't say they all are created at the same time. Why would the TSDF reconstruction volume move though? I mean, I was not moving the interactive marker in RViz manually during this example.
The origins of the rays are supposed to be placed in a spherical pattern around the center of the volume.

So I would conclude that the pattern formed by the rays is similar to the geometry of the object which is placed in front of it in all cases? I have gone through the Kinect fusion paper and the UW CSE Lecture slides. Any other suggestion which would help me get a deeper intuition into this process?
Since the motion planning uses a RRT strategy, at best it finds a solution after a fairly long time, and at worst it completely fails to plan the motion and throws errors like the first few shown, though I'm not 100% sure what's going on with the last two

This confirms that the behavior which I was seeing wasn't something abnormal. I was also having cases where the motion could not be planned. After a while it used to take up candidate poses and in some cases it used to state that The planning problem has been solved or solution has been found. However, there were constraints which were preventing it to move to that location. Will update after checking what happens when those candiate poses are being tried.
[ERROR] [1530883513.318788475,<PHONE_NUMBER>00]: Found empty JointState message

After searching on ROS Answers, this error doesn't seem to have any major importance. So as of now, I am going to ignore it.

Thanks again!

EDIT: On further observation, just a few more warning messages.
[ WARN] [1530986762.138799683,<PHONE_NUMBER>00]: Unable to transform object from frame 'candidate0' to planning frame '/world' (Lookup would require extrapolation into the past.  Requested time<PHONE_NUMBER>00 but the earliest data is at time<PHONE_NUMBER>00, when looking up transform from frame [candidate0] to frame [world])

I get this above error for all 64 candidates. Seems similar to my previous issue. But adding a try-catch block as before does not solve this error as it did before.
This is one more warning.
[ WARN] [1530986530.323626313,<PHONE_NUMBER>00]: Failed to fetch current robot state.
[ INFO] [1530986530.324177460,<PHONE_NUMBER>00]: Combined planning and execution request received for MoveGroup action. Forwarding to planning and execution pipeline.
[ WARN] [1530986530.324308021,<PHONE_NUMBER>00]: The weight on position constraint for link 'camera_depth_optical_frame' is near zero.  Setting to 1.0.
[ INFO] [1530986530.324483190,<PHONE_NUMBER>00]: Planning attempt 1 of at most 1
[ WARN] [1530986530.325945894,<PHONE_NUMBER>00]: The weight on position constraint for link 'camera_depth_optical_frame' is near zero.  Setting to 1.0.
[ INFO] [1530986530.326051436,<PHONE_NUMBER>00]: Path constraints not satisfied for start state...
[ WARN] [1530986530.326549565,<PHONE_NUMBER>00]: The weight on position constraint for link 'camera_depth_optical_frame' is near zero.  Setting to 1.0.
[ INFO] [1530986530.326762763,<PHONE_NUMBER>00]: Position constraint violated on link 'camera_depth_optical_frame'. Desired: -0.300000, -0.300000, 0.800000, current: 0.816647, 0.204373, 0.491472
[ INFO] [1530986530.326923292,<PHONE_NUMBER>00]: Differences -1.11665 -0.504373 0.308528
[ INFO] [1530986530.327083872,<PHONE_NUMBER>00]: Planning to path constraints...
[ WARN] [1530986530.327393233,<PHONE_NUMBER>00]: The weight on position constraint for link 'camera_depth_optical_frame' is near zero.  Setting to 1.0.
[ WARN] [1530986530.327645776,<PHONE_NUMBER>00]: The weight on position constraint for link 'camera_depth_optical_frame' is near zero.  Setting to 1.0.
Debug:   Starting goal sampling thread
[ INFO] [1530986530.328125348,<PHONE_NUMBER>00]: Planner configuration 'manipulator' will use planner 'geometric::RRTConnect'. Additional configuration parameters will be set when the planner is constructed.
Debug:   The value of parameter 'longest_valid_segment_fraction' is now: '0.0050000000000000001'
Debug:   RRTConnect: Planner range detected to be 7.539822
Info:    RRTConnect: Starting planning with 1 states already in datastructure
Debug:   RRTConnect: Waiting for goal region samples ...
Debug:   Beginning sampling thread computation
Debug:   RRTConnect: Waited 0.431969 seconds for the first goal sample.
Info:    RRTConnect: Created 4 states (2 start + 2 goal)
Info:    Solution found in 0.475992 seconds
Debug:   Attempting to stop goal sampling thread...
Debug:   Stopped goal sampling thread after 2 sampling attempts
Info:    SimpleSetup: Path simplification took 0.026644 seconds and changed from 3 to 2 states
[ INFO] [1530986530.925958530,<PHONE_NUMBER>00]: Planned to path constraints. Resuming original planning request.
[ WARN] [1530986530.926477926,<PHONE_NUMBER>00]: The weight on position constraint for link 'camera_depth_optical_frame' is near zero.  Setting to 1.0.
[ WARN] [1530986530.926728899,<PHONE_NUMBER>00]: The weight on position constraint for link 'camera_depth_optical_frame' is near zero.  Setting to 1.0.
[ WARN] [1530986530.927186930,<PHONE_NUMBER>00]: The weight on position constraint for link 'camera_depth_optical_frame' is near zero.  Setting to 1.0.
Debug:   Starting goal sampling thread
Debug:   Waiting for space information to be set up before the sampling thread can begin computation...
[ INFO] [1530986530.927598462,<PHONE_NUMBER>00]: Planner configuration 'manipulator' will use planner 'geometric::RRTConnect'. Additional configuration parameters will be set when the planner is constructed.
Debug:   The value of parameter 'longest_valid_segment_fraction' is now: '0.0050000000000000001'
Debug:   RRTConnect: Planner range detected to be 3.778261
[ WARN] [1530986530.928493559,<PHONE_NUMBER>00]: The weight on position constraint for link 'camera_depth_optical_frame' is near zero.  Setting to 1.0.
[ INFO] [1530986530.928766280,<PHONE_NUMBER>00]: Allocating specialized state sampler for state space
Info:    RRTConnect: Starting planning with 1 states already in datastructure
Debug:   RRTConnect: Waiting for goal region samples ...
Debug:   Beginning sampling thread computation
[ INFO] [1530986559.116059745,<PHONE_NUMBER>00]: Position constraint violated on link 'camera_depth_optical_frame'. Desired: -0.300000, -0.300000, 0.800000, current: -0.187025, 0.287808, 0.549807
[ INFO] [1530986559.116579113,<PHONE_NUMBER>00]: Differences -0.112975 -0.587808 0.250193
[ INFO] [1530986559.162846369,<PHONE_NUMBER>00]: Position constraint violated on link 'camera_depth_optical_frame'. Desired: -0.300000, -0.300000, 0.800000, current: -0.187081, 0.287793, 0.549915
[ INFO] [1530986559.167912790,<PHONE_NUMBER>00]: Differences -0.112919 -0.587793 0.250085
Error:   RRTConnect: Unable to sample any valid states for goal tree
         at line 215 in /tmp/binarydeb/ros-kinetic-ompl-1.2.1/src/ompl/geometric/planners/rrt/src/RRTConnect.cpp

There isn't any feedback from the TSDF reconstruction to the placement of the candidate poses and the casting of the rays. As a simplification I had assumed that if the camera got a chance to look at all the different parts of the object, then the TSDF surface would be reasonably complete. Currently poses are selected by randomizing pitch and yaw relative to some nominal center of the object to be explored, and then randomly varying the camera distance within a range. A constant number of rays are cast from each pose, and the poses are ranked by how many rays hit "unknown" voxels in the octomap. Basically it's trying to generate a variety of poses that are likely to be reachable and likely to expose new regions of the surface, but without having very much specific knowledge of the characteristics of the surface
You could try removing some of the constraints on the motion planner. The constraint that keeps the camera pointed at the object was added to solve a problem with using Iterative Closest Point to find the pose of a real camera from the current depth image and the surface in the TSDF volume, which is that ICP gets lost if it can't find any part of a previously-seen surface in the current camera image. If you're providing it with current poses from tf then it shouldn't be as much of an issue. ICP might give weird results for a smooth simulated surface, but it's not something I've tried personally.
I'll get back to you on the other topics shortly.

Thanks a lot, @schornakj. This makes a lot of sense, especially recognizing that the TSDF reconstruction and the placement of poses are decoupled.
Currently poses are selected by randomizing pitch and yaw relative to some nominal center of the object to be explored, and then randomly varying the camera distance within a range

I had read the yaw part while reading the code, and this clears my confusion about what exactly that part was trying to achieve.

You could try removing some of the constraints on the motion planner.

Will give this a try and will update you with results.

If you're providing it with current poses from tf then it shouldn't be as much of an issue

I agree that relaxing these constraints could make sense for a simulated Gazebo object. However, it (relaxing the constraints) wouldn't really work with real objects.

ICP might give weird results for a smooth simulated surface

Why exactly would ICP give weird results? Is this again because it being a simulated camera and we already have the current tf? Shouldn't it actually give smoother results compared to a real camera?

Why exactly would ICP give weird results? Is this again because it being a simulated camera and we already have the current tf? Shouldn't it actually give smoother results compared to a real camera?
I should have used a clearer word than "weird". ICP is responsible for calculating the pose of the camera relative to the observed surface, and it does this by trying to align the current depth image with previously observed ones. For this to work well, the surface should have variations like corners, edges, curves, and rough textures.  I was thinking about what would happen if the camera could only see part of the sphere or the plane. I would expect that ICP would have difficulty finding the correct camera pose, since the problem of fitting a section of a plane to a flat surface or a piece of a sphere to a sphere is very ambiguous.

  I was thinking about what would happen if the camera could only see part of the sphere or the plane.
That's true, even I had similar concerns while I was starting out with Gazebo. This paper suggests the use of 3-D CAD models as a reference to align real-time data using ICP with a similar task of 3-D reconstruction. However, the behavior of ICP with Gazebo models is definitely questionable.

While I was analysing further, I realised a few things.

Multiple octomaps

So regarding the problem with multiple octomaps, I observed that as I shift the interactive volume marker to the left and right, only the fake octomap moves in the direction where the volume marker box is being moved which leads to the following artifact. The actual octomap does not move at all. Any clues on why this could be happening?

Regarding TSDF volume

I switched the sphere model with a dumpster just for the sake of having a few more edges, corners and color differences (don't know if its exactly helpful though). This is how the raycasting looks them being pointed towards the point cloud published on the my_unknown_point_cloud topic. The reconstruction will need the exploration_node to work properly.

Note: I created a new issue for the lack of robot motion as there seems to be some weird behavior regarding TF.

Issue seems to be solved-
After the latest update in the no robot motion issue, turns out that whenever I clear the Octomap using the Clear Octomap button provided in the RViZ- MoveIt! GUI, only the original octomap remains.

I think I can fairly conclude that the additional Octomap is created when the transforms aren't available at that current moment as seen in the following console output.
[ WARN] [1531746745.094836517, 1461.507000000]: Interactive marker 'EE:goal_camera_link' contains unnormalized quaternions. This warning will only be output once but may be true for others; enable DEBUG messages for ros.rviz.quaternions to see more details.
[ WARN] [1531746748.409081126, 1464.476000000]: No transform available between frame 'map' and planning frame '/world' (Could not find a connection between 'world' and 'map' because they are not part of the same tree.Tf has two or more unconnected trees.)
[ WARN] [1531746748.409159262, 1464.476000000]: No transform available between frame 'volume_pose' and planning frame '/world' (Could not find a connection between 'world' and 'volume_pose' because they are not part of the same tree.Tf has two or more unconnected trees.)
[ INFO] [1531746780.152752017, 1489.571000000]: Clearing octomap...
[ INFO] [1531746780.166161388, 1489.584000000]: Octomap cleared.

@schornakj If you can confirm that this is a fair enough reason, I will close the issue. However, I am still trying to figure out why the following message comes up even after fixing it for one case in my previous issue.
No transform available between frame 'map' and planning frame '/world' (Could not find a connection between 'world' and 'map' because they are not part of the same tree.Tf has two or more unconnected trees.)


Implement Custom Transformer to Model Deployment

This PR allows users to deploy their Transformer Docker image that contains pre/post-processing code.
Changes:

[x] API

[x] Append Transformer Spec to InferenceService Spec
[x] Update Model Version Endpoint API (Deploy, Redeploy, Get, List)
[x] Add unit test
[x] Update Swagger spec

[x] UI - Update Model Version Deployment page to include Transformer configuration
[x] SDK - Update deploy() function to accept new optional arg: transformer

[x] Add E2E test

Model version deployment page preview:

You'll need to include end to end test to the to do list

You'll need to include end to end test to the to do list

Yes. The e2e tests will be included in Python SDK test

After a model+transformer is deployed, is there a way to see the configuration in UI?

After a model+transformer is deployed, is there a way to see the configuration in UI?

Great question. There's no special page for displaying model version configuration, but we can use the redeploy page to display it. Something like this:

We can have separate PR for dedicated model version page.

After a model+transformer is deployed, is there a way to see the configuration in UI?

Great question. There's no special page for displaying model version configuration, but we can use the redeploy page to display it. Something like this:

We can have separate PR for dedicated model version page.

Can you create an issue for this?

LGTM


Go to file resource if are relationship type

Thanks, good addition but please keep in mind that not all the relationship have a corresponding resource. Maybe the files are stored in relationship model but the model has no Nova resource. In this case the link will give 404 error.
The idea of <a> tag does not follow the Nova UI, I mean would be better to have an icon SVG like the view one that is used to view a resource detail page.

Maybe a link something like that?

Yes the eye icon is better but still you need to check if the relationship resource exists.

Righ but the icon is to show the document in the navigation according with the other one PR
In this case I represented it like a relationship with link in the name

I think the eye icon is better for the show resource details while for the open in browser PR use this SVG https://github.com/tailwindlabs/heroicons/blob/master/optimized/outline/external-link.svg

@ahmedkandel changes are ready

@ahmedkandel

Hey, @andresilvagomez I am thinking about a much wider usage of this feature. Not only a link or a button to model resource But a feature/method to allow the user to create links or buttons e.g. ->linkTo('/nova/videos/{id}') then the package replace {id} with the model id we may also support other routes paramters. Also, think about support for Vue Router in order not to reload pages if the link goes to an internal nova route.
What do you think?

@andresilvagomez no need for new releases just sync your fork with the upstream. Please close this PR and create a new clean one with the updated feature.

@andresilvagomez no need for new releases just sync your fork with the upstream. Please close this PR and create a new clean one with the updated feature.

@ahmedkandel no is really create a new release tag. to start using new features available in the projects

@andresilvagomez you can start using the new features without waiting for a release by installing the dev-master branch as following composer require "ahmedkandel/nova-s3-multipart-upload:master".
We are currently working on other updates and once they are ready will release a new version.

@ahmedkandel I agree with you :) totally, but then could you release a new tag with the last PR, and I will work in this feature today!!

@andresilvagomez are you working already on this or shall I?


Implement  params in Telegram Agent

Hi,
Please consider implementing more snedMessage parameters into agent such as:

disable_web_page_preview
disable_notification

Thanks

This would likely be an easy change if you'd like to add it @ali-sattari.

Let us know if you need a hand!

I did use a workaround for the time being and configured PostAgent with Telegram API params.
Here is the gist for any one looking for similar issue: PostAgent Options

Nice solution :)


Functions that depend on the current C locale

Some LibC funs, like strtod in String#to_f64?, and snprintf in Float::Printer#internal, depend on the currently active C locale. This means some oddities could happen if a different locale is active:
lib LibC
  LC_ALL = 6

  fun setlocale(category : Int, locale : Char*) : Char*
end

"1,23".to_f64? # => nil
1.23.to_s      # => "1.23"
1.23.to_s.to_f # => 1.23
"%g" % 1.23    # => "1.23"                   # `String::Formatter#float` also uses `snprintf`
1e23.to_s      # => "9.9999999999999992e+22" # Grisu failure case, triggers the `snprintf` path

# the decimal and thousands separators in german are swapped
LibC.setlocale(LibC::LC_ALL, "de_DE.UTF-8")

"1,23".to_f64? # => 1.23
1.23.to_s      # => "1.23"
1.23.to_s.to_f # Invalid Float64: "1.23" (ArgumentError)
"%g" % 1.23    # => "1,23"
1e23.to_s      # => "9,9999999999999992e+22"

All programs start with the C C locale, but third-party shards might nonetheless change it, leading to those hard to debug scenarios. To my understanding the entire Crystal standard library should be locale-independent.
Is there anything we could do here apart from reimplementing all of LibC's locale-dependent functions in Crystal? (There are probably other kinds of global state in the C runtime to avoid too.)

Here is a list of non-Windows functions I could find that depend on the C locale:

dprintf: Affects floating-point formatting specifiers (%a %e %f %g). Appears in Crystal::System.print_error, which is used in many places but does not have any floats. Locale-dependent behavior might affect compiler specs but I don't think there is a big need to replace this one.
printf: Similar to above. Appears when failing to raise an exception and when the GC outputs a warning; formatting specifiers are not used at all. (dprintf is probably more suitable here, as those errors really should belong in STDERR rather than STDOUT.)
snprintf: Similar to above. Sees the most uses:

Crystal::System.print_error on Windows
Float::Printer#internal, when Grisu3 fails. Indirectly affects Float32#to_s and Float64#to_s. #10913 removes this usage.
String::Formatter#float, whenever a floating-point formatting specifier is used. The PR above does not touch this yet (even then it would cover only %f and some cases of %g).

strtod, strtof: Affects String#to_f32? and #to_f64? respectively. As a result of using these functions, conversion from hexfloats is actually possible:"0xa.bp+5".to_f # => 342.0

Some numeric specs in the standard library use a custom hexfloat parser instead of this undocumented feature.
strerror: Appears in Errno#message. Might affect specs, and is also a public API, unlike dprintf.

On Windows it has been noted that FormatMessageW, which appears in WinError#message, is also locale-dependent.

It is at least questionable that "1,23".to_f64 could ever succeed just based on the current user's locale, which is something the developer might never have expected.
So for anyone else affected by this like me, LibC.setlocale(LibC::LC_ALL, "en_US.UTF-8") somehow did not fix this to treat . always as the decimal seperator. Instead, this is what made it:
fun main(argc : Int32, argv : UInt8**) : Int32
	LibC.setenv("LC_ALL", "en_US.UTF-8", 1)
	Crystal.main(argc, argv)
end

so essentially just overwriting the users locale.

Some libc implementations have implementations liks strtod_l that allow specifying a locale, but they're missing on many platforms. So it wouldn't be a real solution.
I suppose the best solution is to move to native implementations for locale-based algorithms.

s2d.c and s2f.c from the Ryu repository seem to contain replacements for strtod and strtof. I do not know whether they have their own names, or whether they are indeed somehow different from other C runtimes' implementations apart from locale support

Another alternative is https://github.com/fastfloat/fast_float


http: do not add content-length: 0 to 101 responses on upgrade

Per RFC 7230 Section 3.3.2, 101 responses should not contain
either a content-length or transfer-encoding. This change
removes the forced addition of a Content-Length: 0 header in
this case. Upstreams that return 101 or 204 responses with
Content-Length or Transfer-Encoding continue to be forwarded
downstream.
Risk Level: low
Testing: updated tests
Docs Changes: n/a
Release Notes: n/a
Signed-off-by: Stephan Zuercher<EMAIL_ADDRESS>

/retest


Read Vshield/vpatch heuristic id available in trivy bolt db

This commit adds the ability to get the heuristic id from boltdb which is
modified & enhanced by cybercenter vshield/vpatch tracker required for
trivy integration in CSP.

The boltdb bucket will now have additional field named 'hid' short for heuristic-id per CVE
e.g.
Path: alpine 3.10 → ansible → CVE-2018-10875
Key: CVE-2018-10875
Value:
{
"FixedVersion": "2.6.3-r0",
"hid": 319114
}

This should not be implemented in OSS


[Question] Dart implementation - ACL

I can see a lot of interdependencies between modules(node-casbin reference). Just wanted to ask if there's an efficient way to start implementing ACL. The barebones are already set-up.

@santhoshivan23 can you be more specific? I don't know Dart a lot, but it's inconvenient for Dart to implement the interdependencies?

@santhoshivan23 can you be more specific? I don't know Dart a lot, but it's inconvenient for Dart to implement the interdependencies?

I will also involve the original code author here: @KNawm

I will also involve the original code author here: @KNawm

@hsluoyz I meant it would be great if we have a chronological sequence of modules that's to be followed for ACL. How was it initially implemented in jCasbin or node-casbin?
@KNawm I can see that the barebones are more like a replica of node-casbin implementation. Willing to know your thoughts as well on how to begin!

@hsluoyz I meant it would be great if we have a chronological sequence of modules that's to be followed for ACL. How was it initially implemented in jCasbin or node-casbin?
@KNawm I can see that the barebones are more like a replica of node-casbin implementation. Willing to know your thoughts as well on how to begin!

@santhoshivan23 you can definitely regard the git history of jCasbin or Node-Casbin as the "chronological sequence of modules". Basically, you need to implement "request", "policy", "matcher", "effect" to have a basic ACL model support.

@santhoshivan23 you can definitely regard the git history of jCasbin or Node-Casbin as the "chronological sequence of modules". Basically, you need to implement "request", "policy", "matcher", "effect" to have a basic ACL model support.

@hsluoyz I meant it would be great if we have a chronological sequence of modules that's to be followed for ACL. How was it initially implemented in jCasbin or node-casbin?
@KNawm I can see that the barebones are more like a replica of node-casbin implementation. Willing to know your thoughts as well on how to begin!

Like @hsluoyz said, the Git history is a great starting point. The structure of the project is taken from the node-casbin implementation but I would suggest also taking a look at other implementations for inspiration. If you look closely you will find some things that are different from the node-casbin implementation, most of those things are like that because of the differences in the language so beware of that. If you need more help just ping me I'm happy to help!

@hsluoyz I meant it would be great if we have a chronological sequence of modules that's to be followed for ACL. How was it initially implemented in jCasbin or node-casbin?
@KNawm I can see that the barebones are more like a replica of node-casbin implementation. Willing to know your thoughts as well on how to begin!

Like @hsluoyz said, the Git history is a great starting point. The structure of the project is taken from the node-casbin implementation but I would suggest also taking a look at other implementations for inspiration. If you look closely you will find some things that are different from the node-casbin implementation, most of those things are like that because of the differences in the language so beware of that. If you need more help just ping me I'm happy to help!

@KNawm Sure. I'll look into it!

@KNawm Sure. I'll look into it!

@KNawm I've opened a PR with some basic barebones and some enhancements specific to Dart. It would be really great if you can review it!

@KNawm I've opened a PR with some basic barebones and some enhancements specific to Dart. It would be really great if you can review it!

@KNawm sorry to inform you so late but the GSoC idea submission deadline is in nearly 4 hours, can you add your idea about Dart-Casbin to this repo: https://github.com/casbin/SummerOfCode2021 via PR? Thanks!

Already done: https://github.com/casbin/SummerOfCode2021#casbin-for-dart


Using for Point datatype unclear

[Enter feedback here]
For this line of code
public Point Location { get; set; }

When I include it in my project Point is not defined.  I'm assumming
using System.Drawing;
but really I don't know
thanks

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: c2dcf82b-f177-e91b-96a5-67f2f57bd6c4
Version Independent ID: 89c0803f-570f-07a6-6dc2-285678712c86
Content: Spatial Data - EF Core
Content Source: entity-framework/core/modeling/spatial.md
Product: entity-framework
Technology: entity-framework-core
GitHub Login: @bricelam
Microsoft Alias: avickers

The namespace (NetTopologySuite.Geometries) is mentioned earlier in the article

thanks Brice
On Mon, May 3, 2021 at 5:22 PM Brice Lambson @.***>
wrote:

The namespace (NetTopologySuite.Geometries) is mentioned earlier in the
article
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dotnet/EntityFramework.Docs/issues/3235#issuecomment-831544158,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMU35IYC7RY54K6HX4OMNW3TL4HZDANCNFSM44BKT2PA
.


identify sites by name

Is there a way to search in our database for sites that match a particular name (e.g., French Broad) and/or to find the name of a site from its site ID?

Not at present, but probably something dataRetrieval might be able to do? @ldecicco-USGS

Fun river!

Oh, and, you can definitely get the name from the site id:
library(dataRetrieval)
sites <- readNWISsite(c('05114000','09423350'))
sites$station_nm
[1] "SOURIS RIVER NR SHERWOOD, ND" "CARUTHERS C NR IVANPAH CA"

You can't query directly by station name. So, you can figure out a way to get a set of sites, then search from there (so, maybe North Carolina, or a bounding box, or huc):
siteInfo <- readNWISdata(stateCd="NC", parameterCd="00060",
                         hasDataTypeCd="iv", service="site")
fbSites <- siteInfo[grep("FRENCH", siteInfo$station_nm),]
head(fbSites[,1:3])
    agency_cd  site_no                            station_nm
194      USGS 03439000      FRENCH BROAD RIVER AT ROSMAN, NC
196      USGS 03443000    FRENCH BROAD RIVER AT BLANTYRE, NC
198      USGS 03447687  FRENCH BROAD RIVER NEAR FLETCHER, NC
202      USGS 03451500   FRENCH BROAD RIVER AT ASHEVILLE, NC
204      USGS 03453500    FRENCH BROAD RIVER AT MARSHALL, NC
205      USGS 03454500 FRENCH BROAD RIVER AT HOT SPRINGS, NC

Great! Thanks.

this should be done first in mda.streams, then ported here. see https://github.com/USGS-R/mda.streams/issues/122


Fix DeepLabV3Plus encoder depth

Hi, @qubvel. Thanks for your great work!
This PR fixes #377 and is used to be PR #561, which staled and closed before.
I ran into the issue #377 again to find that the PR can still be effective.

So, I made some maintenance and rebased on edadc0d.
Update

Fix the feature index mismatch which occurs when encoder_depth is 3 and 4.

Please refer to the attached file to see the combination of tensor shapes in each cases: tensor_shapes.md.

Modify the docstring for upsampling argument to state the condition to preserve input-output shape.

In case (encoder_depth, encoder_output_stride) = (3, 16), upsampling should be set to 2.

Modify a type hint and add a value check.

Type hint error: Squence[int, ...] should be Squence[int].
Value check: add a validation to make sure encoder_depth is either 3, 4, or 5.

Test Code
from itertools import product

import torch
import segmentation_models_pytorch as smp

input_shape = (10, 3, 192, 128)
input_tensor = torch.zeros(input_shape)
for up, depth, stride in product((2, 4), (3, 4, 5), (8, 16)):
    net = smp.DeepLabV3Plus(
        encoder_name="timm-mobilenetv3_small_minimal_100",
        encoder_weights="imagenet",
        encoder_depth=depth,
        encoder_output_stride=stride,
        upsampling=up,
        classes=1,
        activation=None
    )
    print(f"encoder_depth={depth}, encoder_output_stride={stride:2}, upsampling={up}")
    output_shape = tuple(net(input_tensor).shape)
    preserved = all(input_shape[i] == output_shape[i] for i in (0, 2, 3))
    print(f"  output shape: {output_shape}, preserve shape: {preserved}")

output
encoder_depth=3, encoder_output_stride= 8, upsampling=2
  output shape: (10, 1, 96, 64), preserve shape: False
encoder_depth=3, encoder_output_stride=16, upsampling=2
  output shape: (10, 1, 192, 128), preserve shape: True
encoder_depth=4, encoder_output_stride= 8, upsampling=2
  output shape: (10, 1, 96, 64), preserve shape: False
encoder_depth=4, encoder_output_stride=16, upsampling=2
  output shape: (10, 1, 96, 64), preserve shape: False
encoder_depth=5, encoder_output_stride= 8, upsampling=2
  output shape: (10, 1, 96, 64), preserve shape: False
encoder_depth=5, encoder_output_stride=16, upsampling=2
  output shape: (10, 1, 96, 64), preserve shape: False
encoder_depth=3, encoder_output_stride= 8, upsampling=4
  output shape: (10, 1, 192, 128), preserve shape: True
encoder_depth=3, encoder_output_stride=16, upsampling=4
  output shape: (10, 1, 384, 256), preserve shape: False
encoder_depth=4, encoder_output_stride= 8, upsampling=4
  output shape: (10, 1, 192, 128), preserve shape: True
encoder_depth=4, encoder_output_stride=16, upsampling=4
  output shape: (10, 1, 192, 128), preserve shape: True
encoder_depth=5, encoder_output_stride= 8, upsampling=4
  output shape: (10, 1, 192, 128), preserve shape: True
encoder_depth=5, encoder_output_stride=16, upsampling=4
  output shape: (10, 1, 192, 128), preserve shape: True

Hi @munehiro-k ,
I also found this problem. I think I can contribute another PR and solve problems about DeeplabV3 and Deeplabv3+ in different encoder depths.


compatibility with sound physics remastered

it would amazing to have compatibility with sound physics so the whistle echos in caves and so other players can hear echos of whistles like when im playing with friends
https://modrinth.com/mod/sound-physics-remastered

it would amazing to have compatibility with sound physics so the whistle echos in caves

Oh, does that not work? That might be because the sound doesn't actually have a location.
Located sounds have that annoying issue where it doesn't properly sync up with the player's exact position, so you can e.g. hear you own sounds behind you when walking.
I'm not sure if there's a good fix for that.
Maybe only use positioned sound when Sound Physics Remastered is installed? Gonna need to do some testing with that.

so other players can hear echos of whistles like when im playing with friends

Ah, that part's hard to answer.
I intentionally made the whistle sounds client-only for two main reasons:

To keep IndyPets a vanilla-client compatible server mod
Whistling was never intended for player communication, just as a fun feedback that you called your pets

I get the idea though, it would be fun to hear the whistling.
Though then one would most likely want a whistle option that doesn't call your pets, which honestly would make more sense as a separate mod.
Still not entirely sure what to do here.

oh well i dont care much for the other players being able to hear you i just want echos it doesnt bother me really if the sound is not synced up it just breaks the immersion when every sound echos apart from whistling! i hope you can find a way to fix it

if you could make the sound positioned and just have a setting to turn it on and off that would be good

It was indeed that the sounds weren't positioned.
I added a config option for positioned whistle sounds.
New versions are up!

it sounds so amazing!!! thank you!!


Fork in sidechain block production

See https://github.com/litentry/litentry-parachain/issues/1524 for the compete logs.
It doesn't happen very often, actually it's the first time we've seen this. But it has a very bad consequence that two workers will diverge and never run in sync again.
I've investigated it (see https://github.com/litentry/litentry-parachain/issues/1524#issuecomment-1483959498) and the root cause seems to be:

[2023-03-24T11:12:30Z] worker0 claimed aura slot 279942725 and produced sidechain bn 13283 based on parentchain bn 10024
[2023-03-24T11:12:36Z] in the last second of aura duration (6s in our case), it finished composing and broadcasted it to worker1
[2023-03-24T11:12:36Z] the broadcast took time and worker1 started to claim slot 279942726 and built its own version of sidechain bn 13283, but with parentchain bn 10025 (that's the latest parentchain header worker1 synced)
[2023-03-24T11:12:44Z] worker1 failed to produce the block as it took too long
[2023-03-24T11:12:44Z] worker1 got the sidechain block from worker0 and attempted to import it. However it couldn't verify the block because it couldn't find the matching parentchain block header in its parentchain import queue.
[2023-03-24T11:12:44Z] the block was discarded by worker1 and from this point on, they couldn't sync with each other anymore.

My questions:

there're two cases/timepoints where the blocks in the parentchain import queue will be popped:

when a worker composes a sidechain block
when a worker imports a sidechain block from the peers
the queue can't be popped twice (reminds me of double-free), otherwise the desired parentchain header can't be peeked. It seems we can easily run into this situation when a worker fails to produce blocks but the queue is already popped. Then the worker can't import a block that was composed based on an older parentchain bn anymore. Have you already got an idea regarding the solutions?

what if worker1 succeeded in producing block bn 13283 on its slot? Then we have two valid sidechain blocks with different parentchain bn backings. Worker0 will probably reject the block from worker1 as it was already imported, what about worker1? Is the order of block import guaranteed (that it will first import the block from worker0, then worker1 itself)? What if under a very bad network situation where worker1 couldn't get the block from worker0 in time?
When broadcasting the blocks to peers, I see it's broadcasted to the same endpoint multiple times:

[2023-03-24T11:13:11Z DEBUG integritee_service::worker] Broadcasting block to peer with address: "ws://<IP_ADDRESS>:2001"
[2023-03-24T11:13:11Z DEBUG integritee_service::worker] Broadcasting block to peer with address: "ws://<IP_ADDRESS>:3001"
[2023-03-24T11:13:11Z DEBUG enclave_runtime::top_pool_execution] Sending sidechain block(s) confirmation extrinsic..
[2023-03-24T11:13:11Z DEBUG integritee_service::worker] Broadcasting block to peer with address: "ws://<IP_ADDRESS>:2001"
[2023-03-24T11:13:11Z DEBUG integritee_service::worker] Broadcasting block to peer with address: "ws://<IP_ADDRESS>:2001"
[2023-03-24T11:13:11Z DEBUG integritee_service::worker] Broadcasting block to peer with address: "ws://<IP_ADDRESS>:2001"

why was that? Shall we use set instead of vectors in the peers or urls collections?

Thanks @clangenb

yea I agree - I can try to modify the code. The slot proposer does need the parentchain block to be able to compose a sidechain block upon it, so basically I think there're two ways of keeping the queue state unchanged if it fails to produce a block:

pop -> compose the block -> push the popped blocks back to front if composing fails (if the queue is Deque)
note the blocks that should be popped and only pop them when the composing succeeds => have to check the code it would affect any peeked parentchain header
Do you have any preference?

I see where you are coming from, thanks
it might come from the litentry-specific part, I'll have to check our code. But in general I believe the peer updating mechanism could be improved: https://github.com/litentry/litentry-parachain/issues/1546
Do you see the same?

Sorry for the delayed response here.

I am currently looking at the codebase myself to see what could be done. Then I will be able to tell my preference, or see if I have a solution in mind.
I absolutely agree.

On another note, if I analyse the logs correctly, worker1 failed to produce the block because the import of the parentchain block took too long. This must not be the case: https://github.com/integritee-network/worker/issues/1275.


Debugger controls duplicate

If you debug more then one project at a time. I see duplicate buttons on the debugger controls. Debugger controls duplicate when you drag it.

@JasonFoglia I can not reproduce this. Here's me debugging two programs at the same time:
What are you doing specially? Can you reproduce if you disable all your extensions?
Do you have exact repro steps?

I'm unable to reproduce myself. I simply shut down and restarted.


RTL Editing Doesn't Work at All!

The only thing that happens when you switch the language to Hebrew, is that the document direction changes from left to right, but this is where it stops.
Nothing else works, you can't select a word or a sentence to edit, line breaks are all over the place.
Once you start a new line, the line above it is no longer editable.
The YML front matter panel is in more bad shape than the text editor as there is a mix of English and Hebrew.
I translated prose.io in its entirety to Hebrew and I hope you'll take the time to fix this issue so people can really start using it. If there is anything I can do to contribute, let me know.

Similar problems for Arabic. Let me know how I can help.

@AmrEldib if you can contribute an Arabic translation, that would be very much appreciated. There are instructions in contributing.md. You'll want to know the prose transifex site as well.
@medicart I'm looking into the Hebrew translation.

Possible these bugs stem from unresolved issues in CodeMirror https://github.com/codemirror/CodeMirror/issues?utf8=✓&q=is%3Aissue+is%3Aopen+rtl

@mikemorris yeah I think you're right. Thought it was the transifex translation at first, but that file is completed and deployed.
CodeMirror has a direction branch that is trying to address this, but isn't being worked on and is now way behind the master.
Open to suggestions here.

@dereklieu I'd love to help with the localization. I've submitted a request to be a member of the team.
@dereklieu @mikemorris would testing the direction branch help merge (and then using it in Prose)? I see at least one comment welcoming testing. Another more recent comment is more specific.
What do you think?

@AmrEldib I haven't looked into the CodeMirror internals much, so I'd be interested in knowing just how much work this task would involve.
The version of CodeMirror that Prose uses is outdated as well, and needs an update.

@dereklieu I just submitted a request to join Persian translation team. However, there seems to be multiple join requests waiting there. Are you looking at transifex join requests at all?

@mehdisadeghi Hrm, just checked and it looks like something got screwed up in Transifex during a redesign or something - I stopped receiving request notifications, and I'm no longer able to approve requests for some reason. I did however add @dereklieu as a maintainer - hopefully he'll be able to get this sorted out.

Thanks for the checking @mikemorris. I'll wait for @dereklieu to approve it.

Hm, also can't approve people. @tristen I think it has to be you (or possibly add me as an admin?). I can't access the "Teams" tabs that's in the Transifex top nav.

Hmm @dereklieu I see you as a "maintainer" on prose and I don't see any option to make you an "admin" or even whether I'm an "admin" or not. I've sent a change ownership to your "derrrrrrr" account!

Hello - are there any plans to add RTL support for content editing?

It seems to me that the only thing that needs to be added for successful rtl text editing is
.CodeMirror {
    direction: rtl;
}

when the direction is rtl.

@nikonikoniko can you submit a PR? I don't know if this has changed, but prior when we had discussed this issue, CodeMirror didn't really support rtl text editing.

Yes, we can work on that.  Thanks for responding!

Hey @nikonikoniko best if we can avoid adding an extra button. IMO, the ideal behavior would be, if the user switches from English to Hebrew, the class is applied which flips the CodeMirror editor right to left, and when the user switches back to English (or other left-to-right language) the class is removed.
Happy to provide any additional feedback is helpful.

"switches to hebrew" - does this mean here? https://prose.io/#chooselanguage
for multilingual markdown repositories, this is quite hidden, but ok, we can do that.

(also just checking - there are no arabic interface translations at the moment?)

I believe so

Hi there
I'm interested in helping with this issue too; I sent a request to join the Arabic translating team on transfix.

There is now a pull request.  Thanks for taking a look!

Just a gentle reminder about my pull request which brings RTL support when choosing the Arabic interface.

Howdy folks, brand new maintainer just stepping in to say that I'm working on this! We're not 100% there in terms of functionality, but what @tareefdev has proposed is much better than what we currently have. Just working through git challenges to get their changes merged in. I'm working to try and bring this project back from the dead so bear with me. We should have this issue sorted within the next week.
Additionally, I'm aware that Arabic translation has dropped off the main site. I'm working with other maintainers to get that back, just an issue with Transifex changing it's auth requirements. As soon as I have access I'll restore that functionality.
If anyone has the time to pitch in and help with a more robust RTL editing solution I'm happy to welcome all contributions!
Sorry this slipped into limbo for so long!
شكرا / תודה


use of existing Dockerfile

Prerequisite

https://github.com/openshift/odo/issues/5109

User Story
As a developer I want to be able to build image for my application using my already existing Dockerfile and deploy it to the cluster.
Scenario
git clone myproject
# project already contains Dockerfile

odo push
# autodetect language
# build image
# push to cluster using devfile deploy command

Acceptance Criteria
/kind user-story

/blocked
on #5109

I think this will be taken care of by #5192. @kadel @feloy WDYT?

No, this is something bit different

@kadel can you please help refine this one?
/triage needs-information

With odo deploy implemented and with outerloop support in devfile it is easy to create a devfile for this use case. I've created simple example https://github.com/kadel/devfile-nodejs-deploy/blob/2b7058af5cdac5a43ded2b6c44454add7cf82161/devfile.yaml#L56


bump to hie-bios 0.2.0 and bump *lsp packages

 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.You have signed the CLA already but the status is still pending? Let us recheck it.


TypeError: can't pickle _thread.RLock objects

File "/media/huaxin/tcl2/nlp/dumingyu_project/bertlk/web_service/advanced_deploy_api.py", line 76, in
streamer = Streamer(model.predict, batch_size=8, max_latency=0.1, worker_num=1)
File "/media/huaxin/tcl2/nlp/dumingyu_project/bertlk/web_service/service_streamer.py", line 296, in init
self._setup_gpu_worker()
File "/media/huaxin/tcl2/nlp/dumingyu_project/bertlk/web_service/service_streamer.py", line 311, in _setup_gpu_worker
p.start()
File "/media/huaxin/tcl2/nlp/anaconda3/lib/python3.6/multiprocessing/process.py", line 105, in start
self._popen = self._Popen(self)
File "/media/huaxin/tcl2/nlp/anaconda3/lib/python3.6/multiprocessing/context.py", line 284, in _Popen
return Popen(process_obj)
File "/media/huaxin/tcl2/nlp/anaconda3/lib/python3.6/multiprocessing/popen_spawn_posix.py", line 32, in init
super().init(process_obj)
File "/media/huaxin/tcl2/nlp/anaconda3/lib/python3.6/multiprocessing/popen_fork.py", line 19, in init
self._launch(process_obj)
File "/media/huaxin/tcl2/nlp/anaconda3/lib/python3.6/multiprocessing/popen_spawn_posix.py", line 47, in _launch
reduction.dump(process_obj, fp)
File "/media/huaxin/tcl2/nlp/anaconda3/lib/python3.6/multiprocessing/reduction.py", line 60, in dump
ForkingPickler(file, protocol).dump(obj)
TypeError: can't pickle _thread.RLock objects

@Meteorix @pku-wuwei Same Error, please give some help, thanks a lot!
Traceback (most recent call last):
File "asr_api.py", line 92, in
streamer=Streamer(model.predict,batch_size=4,max_latency=0.01)
File "/media/huaxin/tcl1/asr/yujiangling/lib/python3.6/site-packages/service_streamer/service_streamer.py", line 267, in init
self._setup_gpu_worker()
File "/media/huaxin/tcl1/asr/yujiangling/lib/python3.6/site-packages/service_streamer/service_streamer.py", line 280, in _setup_gpu_worker
p.start()
File "/media/huaxin/tcl1/asr/anaconda3/lib/python3.6/multiprocessing/process.py", line 105, in start
self._popen = self._Popen(self)
File "/media/huaxin/tcl1/asr/anaconda3/lib/python3.6/multiprocessing/context.py", line 284, in _Popen
return Popen(process_obj)
File "/media/huaxin/tcl1/asr/anaconda3/lib/python3.6/multiprocessing/popen_spawn_posix.py", line 32, in init
super().init(process_obj)
File "/media/huaxin/tcl1/asr/anaconda3/lib/python3.6/multiprocessing/popen_fork.py", line 19, in init
self._launch(process_obj)
File "/media/huaxin/tcl1/asr/anaconda3/lib/python3.6/multiprocessing/popen_spawn_posix.py", line 47, in _launch
reduction.dump(process_obj, fp)
File "/media/huaxin/tcl1/asr/anaconda3/lib/python3.6/multiprocessing/reduction.py", line 60, in dump
ForkingPickler(file, protocol).dump(obj)
TypeError: can't pickle LockType objects


pre-release-commit-message template replacements don't seem to work

Hi there!
I'm trying to adapt cargo-release to work for nextest. The nextest workspace consists of several crates, each with their own independent versioning.
If I'd like to update one of nextest's crates, I'd like to be able to do:
cargo release -p nextest-filtering 0.2.2 --execute

and have a commit be created with the requisite version bumps and the message:
[nextest-filtering] version 0.2.2

and a signed tag created on this commit called nextest-filtering-0.2.2 with message:
nextest-filtering version 0.2.2

Here's my first attempt at configuring that, based on the reference:
https://github.com/nextest-rs/nextest/blob/main/release.toml
However, when I run:
cargo release -p nextest-filtering 0.2.2 --execute

the commit that gets created is:
commit 49aaac68f9fae149b957ed79508e3551cd20d816 (HEAD -> main)
Author: Rain<EMAIL_ADDRESS>Date:   Fri Oct 14 12:23:50 2022 -0700

    [{{crate_name}} version {{version}}

which indicates that template replacements aren't working.
Any idea how to make them work?
% cargo release --version
cargo-release 0.21.4

consolidate-commits = true

This tells cargo-release to use a single commit for all version bumps which means there is not a specific crate name or version to use in case you run cargo release --workspace or cargo release -p one -p two (and we don't want it conditioned on how you run as that might cause problems).

Note: in the next version, I'm looking at making consolidate-commits = true the default which is why I suggested still explicitly setting it.  The focus on the next release is to better scale up with large workspaces.

Got it, thanks! Just managed to debug this myself as well.

BTW I did a writeup of how nextest uses cargo-release: https://github.com/nextest-rs/nextest/blob/main/internal-docs/releasing.md

For each changed crate, in topological order (internal dependencies like nextest-filtering first, cargo-nextest last), run cargo release -p  . For example, cargo release -p nextest-runner 0.28.0. This will perform a dry run.

In the upcoming version of cargo-release, my hope is that this will change to

In "Prepare releases", people run cargo release version -p <crate> <version> -x
In "Create and push tags", people run cargo release

This is part of an effort to support two-phase release (#119) which I hope will help with auto-release (#117) and alternative workflows (#528)

PUBLISH_GRACE_SLEEP=5

Please don't tell me you ran into issues with this.  It should be waiting for you though I'm looking forward to https://github.com/rust-lang/cargo/pull/11062 being merged

Ooh that looks really good as a way to do things. How would that distinguish between when to tag + push and when to publish crates?
Ah, I didn't realize cargo release already waited a bit. This is a replacement for a very simple script I had locally that slept for 5 seconds in between publishes.

Oh never mind, misread that! You were talking about steps I and II.

Also, you might be able to replace release-publish.toml with cargo release publish --publish
--publish is telling the cargo release publish command to override the config and do a publish anyways.  Its not a --force because I kept the flags the same between cargo release and the step subcommands.

Thanks @epage! Looks like it does work and simplifies things tremendously.

I've updated the documentation on this.  I've also added #604 and am reconsidering #116, including erroring when a variable is present.

@epage thanks for updating that, just curious why this user error is almost invisible behind debug! logs.
Furthermore, now that dev-version=true support is gone, what is there to be split/consolidated about commits? And what makes it impossible to have the to-be-released version in the pre release commit?

consolidate-commits did not deal with dev-version but consolidating commits between workspace members.  When releasing more than one crate, they might be using different versions, so we have no version to put in the replacement.  When you tell cargo-release they are using the same version, we do support the version in replacements.
consolidate-commits should only be defaulted to true in a workspace so this shouldn't affect single-crate cases.

Ah right, the crate I had this problem with "is a single crate", but has workspace members for examples (which could have just been regular examples/...rs files). Thanks, now I at least know what to write when setting this back to true :)
But that also means there's no per-crate version for releasing multi-crate workspaces with one release per commit?

Could you re-frame that question., I'm not quite sure what you are asking.

I may have simply misunderstood while writing that: when in a workspace, and consolidate-commits = false, {{version}} automatically becomes available again. No question to be asked, just me getting lost in the options - apologies for the noise.
All that remains is finding a more user-friendly system for filling in or rejecting {{version}} with the default of consolidate-commits = true, before pushing out the borked commit to git.


build(deps): bump chroma github.com/alecthomas/chroma/v2 to 1235bbf2ceaf

Ahead of https://github.com/alecthomas/chroma/issues/942 being addressed to release a new version of chroma, we bump to the current tip version of chroma via a pseudo-version.
This contains an important fix for the CUE language:
https://github.com/alecthomas/chroma/commit/898d467079907643cedd78e7ae813dd352017c51

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

This would resolve https://github.com/gohugoio/hugo/issues/11862 as well.

I'm happy to return to this PR to look at the build failures, but if in the meantime someone more familiar with what's failing wants to take it over that's fine with me.

@jmooring - the build failures look like a genuine bug to me, and appear to have been introduced by https://github.com/alecthomas/chroma/commit/6dd9f269efaa029531b198c3c803f07dc7343c77. Thankfully the CUE change I need is the commit immediately prior to that, so I'll use that as the basis for the pseudo-version for now.

@jmooring - I've force-pushed a revised commit for this PR, and raised https://github.com/alecthomas/chroma/issues/945 for what I think is a bug in chroma.

https://github.com/alecthomas/chroma/issues/945 is now resolved; I totally missed/messed up my analysis, and somehow failed to see the line in the actual output, only with a minor space difference. So I've now revised this PR to use a pseudo version for the current tip of chroma.
@jmooring - this PR is now ready for the workflows to be re-run, and for review please!

Thanks, for future reference, please read our commit message guidelines.


'package:flutter/src/widgets/framework.dart': Failed assertion: line 1960 pos 12: '_elements.contains(element)': is not true.

Steps to Reproduce

Run flutter create bug.
Update the files as follows: ...
...

Expected results:
Actual results:

Logs

Hi @zjl801,
When opening an issue, please provide some or all information mentioned in issue template.

issue template
If you are looking for support, please check out our documentation
or consider asking a question on Stack Overflow:
- https://flutter.dev/
- https://api.flutter.dev/
- https://stackoverflow.com/questions/tagged/flutter?sort=frequent

If you have found a bug or if our documentation doesn't have an answer
to what you're looking for, then fill our the template below. Please read
our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports

Steps to Reproduce

Please tell us exactly how to reproduce the problem you are running into.

Please attach a small application (ideally just one main.dart file) that
reproduces the problem. You could use https://gist.github.com/ for this.

If the problem is with your application's rendering, then please attach
a screenshot and explain what the problem is.

1. ...
2. ...
3. ...

Please tell us which target platform(s) the problem occurs (Android / iOS / Web / macOS / Linux / Windows)
Which target OS version, for Web, browser, is the test system running?
Does the problem occur on emulator/simulator as well as on physical devices?

Target Platform:
Target OS version/browser:
Devices:

Run your application with `flutter run --verbose` and attach all the
log output below between the lines with the backticks. If there is an
exception, please see if the error message includes enough information
to explain how to solve the issue.

Run `flutter analyze` and attach any output of that command below.
If there are any analysis errors, try resolving them before filing this issue.

Finally, paste the output of running `flutter doctor -v` here.

Closing, as no information is provided.