Unable to Access Console/My Account After Changing Hostname with MySQL as Primary DB

Describe the issue:
After changing the hostname and MySQL set as the primary database, unable to access the console and My Account.
This issue occurs even though the process works as expected with the default pack.
How to reproduce:
1.
Configure the hostname as follows in <IS_HOME>/repository/conf/deployment.toml.
hostname = "wso2.com"

Change keystore necessary commands
go to repository/resources/security

mv wso2carbon.jks /home/ubuntu/m7/test
keytool -genkey -alias wso2carbon -keyalg RSA -keysize 2048 -keystore wso2carbon.jks -dname "CN=wso2.com, OU=Home,O=Home,L=SL,S=WS,C=LK" -storepass wso2carbon -keypass wso2carbon
keytool -export -alias wso2carbon -keystore wso2carbon.jks -file test.pem
keytool -import -alias carbon1 -file test.pem -keystore client-truststore.jks -storepass wso2carbon

Change Default DB as MYSQL - toml
[user_store]
type = "database_unique_id"

[database.identity_db]
#type = "mysql 5 7"         # Infers the local H2 DB connection details for 'DEV' pattern. SHOULD BE CHANGED TO PRODUCTION READY DB FOR PRODUCTION
url = "jdbc:mysql://localhost:3306/alphamysql?useSSL=false"
username = "root"
password = "root"
driver = "com.mysql.jdbc.Driver"
[database.identity_db.pool_options]
maxActive = "80"
minIdle ="5"
testOnBorrow = true
validationQuery="SELECT 1"
validationInterval="30000"
defaultAutoCommit=false

[database.shared_db]
#type = "mysql 5.7"         # Infers the local DB connection details. SHOULD BE CHANGED TO PRODUCTION READY DB FOR PRODUCTION
url = "jdbc:mysql://localhost:3306/alphamysql?useSSL=false"
username = "root"
password = "root"
driver = "com.mysql.jdbc.Driver"
[database.shared_db.pool_options]
maxActive = "80"
minIdle ="5"
testOnBorrow = true
validationQuery="SELECT 1"
validationInterval="30000"
defaultAutoCommit=false

add relevant mysql jdbc jar to (/repository/components/lib)
Error
 [d984d726-2af8-48a3-a52d-93cabd3f8f34]  WARN {org.wso2.carbon.identity.oauth2.authz.validators.AbstractResponseTypeRequestValidator} - Provided Callback URL does not match with the registered one.

References : https://is.docs.wso2.com/en/latest/deploy/change-the-hostname/

Similar to https://github.com/wso2/product-is/issues/10514

Similar to #10514

This is not related to offset changes, this is based on changing hostname

Tried with postgress, this is not working as expected ( latest jenkin build) #4938


Add generate_cover (default false) and execute (default true) options

I haven't added any documentation or tests yet, but I can along with revising the details of the implementation.
This PR addresses two issues.

Currently examples are given an initial run in case they generate images. I am not sure this should be the default behaviour. I did a quick check and the majority of the listed users do generate images, however I believe that many potential users would not given many examples do not generate a single identifiable image as part of their execution. I think this behaviour makes sense as opt-in because you already have to arrange for the image generation, so opting in at this point seems reasonable. I realise this is a breaking change, but I thought it was worth bringing up.

Library
Cover

AlgebraOfGraphics.jl
Generated

Augmentor.jl
Generated

Bokeh.jl
Static

FractionalDiffEq.jl
Static

LeetCode.jl
None

Images.jl
Generated

ImageMorphology.jl
Generated

ReinforcementLearning.jl
Generated

Plots.jl
Generated

PSSFSS.jl
Generated

Currently examples are always executed. In the case of some examples including interactive examples that e.g. readlines() execution doesn't really make much sense. This can also be the case for interactive plots. So the PR adds a single option execute which is true by default. Setting it to false disables all execution, but of course users can still execute the script or notebook on their machine or on binder.

BTW, for pages with non-cover images, we'd probably need to provide a theme template for people to use. I only provided the "None" theme version, but maybe you have other ideas?

Okay! I've updated this. Sorry for the long gap. I didn't quite initially understand your feedback on the first read and promptly forgot about this PR.
I've changed the default for generate_cover to depend on whether cover is specified. Now it won't try to generate a cover if one is specified explicitly, otherwise it will.
The stuff about ugly blank covers/inappropriate templates is understood now. I'm putting together other PRs for that so hopefully they can be merged independently.


do you have a plan to support hf_hub_ctranslate2 ?

Is there a reason we should? I’ve never heard of this before today.

There's a trend quantified models are more likely to be used in practice. Like GPTQ, Ctranslate2 is another quantification framework, and hf_hub_ctranslate2 is for connecting Transformers on HuggingfaceHub with Ctranslate2 . Guess it should be a good feature.

You are welcome to open a PR submitting this.

Closing because we don't currently have support for this library on the roadmap, but we would welcome a contribution integrating this library as an LM type!


[WATCH@LIVE]UPDATES=] Sinner vs Fritz LIVE Ｂｒｏａｄｃａｓｔ Ｆｒｅｅ ＯＮ Ｔｖ Ｃｈａｎｎｅｌ 08．０9．２０２４

[WATCH@LIVE]UPDATES=] Sinner vs Fritz LIVE Ｂｒｏａｄｃａｓｔ Ｆｒｅｅ ＯＮ Ｔｖ Ｃｈａｎｎｅｌ 08．０9．２０２４
US Open Tennis 2024 Men's Final: TV Schedule, Start Time and Live Stream By defeating Frances Tiafoe, Taylor Fritz became the first American man to reach a Grand Slam men's singles final since 2009.
On Sunday, he'll aim to break one more long drought: No American man has won a major final since 2003, when Andy Roddick won on these same courts.
Fritz will face top seed Jannik Sinner, who has breezed through competition to advance to his second grand slam final of the year.
Here's everything you need to know about Sunday's final.
Location: Arthur Ashe Stadium in Flushing, New York
Time: 2:00 p.m. EST
TV: ABC
Streaming: ESPN+, ESPN Deportes
Prize Money: $3,600,000 (winner), $1,800,000 (runner-up)
Taylor Fritz erased a two-set to one deficit to reach his first Grand Slam final.
Down the stretch, the No. 11 seed was able to outlast his opponent, who, following the fourth set, felt a sudden wave of fatigue.
In the final, the 26-year-old American will face the hardest task in all of men's tennis.
Jannik Sinner has won 33 of 35 matches on the hard-court surface this year, including hoisting his first Grand Slam title at the Australian Open and winning two ATP Maters 1000 hard-court tournaments (Miami Open, Cincinnati Open).
An American crowd eager to see a champion for the first time since 2003 will motivate Fritz, but it's unclear if this will have a significant impact.
The top-seeded Italian is performing significantly better right now, and in order for Fritz to stay in this match, he'll have to rise to the physical occasion and avoid playing defense.


add Serialize to internal structs

minor change, but could serde::Serialize be included with all PokeAPI structs?  I'd like to be able to export the data I retrieve from the library to other tooling/libraries

@GregHanson Hey there!
Thanks for your contribution, it is much appreciated!
Since you're the second one to ask for this feature, I'm willing to accept it.
However, I'd prefer if it was behind a feature gate that is opt-out by default

done! I think I did that right since my import of the branch compiles

Thanks!
I'll look into it as soon as possible when I come back from vacations!

Hey @GregHanson !
Thanks for the contribution ! I reviewed it, it works and it's a nice addition to the crate, thanks !
You didn't put Serialize on every struct though, is there a reason for that ?
Do you mind adding this to all structs that are already Deserialize ?
I can merge it as is if you want, and I'll do it myself if you prefer.
Please let me know !

you are right! that was my mistake.  I think I got them all now


running examples - where is login.html, and index.html?

Just as the subject states, running the examples and it is complaining about no login.html and index.html?
Let me know if I'm missing something, thanks.

I've the same question. The templates are missing apparently!


:book: Adding OLM V1 architecture document

The documentation contains description of the components and a diagram. Removed the components.md file as the architecture doc contains the same information
Fixes : #1124

Description

Reviewer Checklist

[ ] API Go Documentation
[ ] Tests: Unit Tests (and E2E Tests, if appropriate)
[ ] Comprehensive Commit Messages
[ ] Links to related GitHub Issue(s)

I think we should also call out the CRs each component reconciles (with links to the API description).

I think we should also call out the CRs each component reconciles (with links to the API description).

@perdasilva I do not want to go to that low level in this document as it would impact the readability of the doc. We can have another doc (as follow up) which can talk about this. So that folks want to go little low level can move to those docs after going through the architecture doc.

I get that. I just would have expected the API the users use to not really be a low level thing. It's the front door XD

@perdasilva We already have https://github.com/operator-framework/operator-controller/pull/1230 and https://github.com/operator-framework/operator-controller/pull/1240.
So I am not entirely sure what you are looking for.  If you can create an issue with more details/context I can take a look to fix it.


feat(longhornctl): add examples to help menu and doc

Which issue(s) this PR fixes:

Issue longhorn/longhorn#8992
What this PR does / why we need it:
Add examples to the help menu and doc.
Special notes for your reviewer:
None
Additional documentation or context
None

@mergify backport v1.7.x


rfc: Change Electron Fuse Security Defaults

We've talked about this a bit internally, but I think it would be good to formalize this as a proposal. This is less API discussion and more "proposing a breaking change" but I still felt it fits the RFC process a bit better than discussing in a PR somewhere.

I'm generally in favor of this RFC as switching Electron to secure by default settings is a good idea. We should also consider discussing @dsanders11's feedback in an API WG meeting.
@MarshallOfSound is there still interest in pushing forward this effort? If so, would you like to schedule a discussion for it next month?


Imported 4965 songs, then failed

This is amazing!
I only got the problem above when importing a 30,000 songs list. The script created 31 playlists with the naming "Thu May 26 2016 Part XY". However only parts 1-4 were fully populated. Starting from list #5, after song #4965, only like one in every 20 songs was recognized and put into the respective lists 5 to 31. I have attached the results playlist.
What could be wrong here? BTW the CPU got very hot for like 10 seconds. Maybe the script was overloaded by the number of songs?
playlists_import.zip

that is quite a list.
searches look in two spots, in google music and in your own library.  google music searches are usually quick, but don't return results for music you may have uploaded etc. library searches are not currently indexed so searches there are a bit slower.
how many songs are in your library? number found at Music Library > Songs
if you have a bunch of songs in your library (i have about 4k) you can try commenting out the line that looks in the library.
processes.push(gmusic.getLibrary().then(
function(slist){songs = songs.concat(slist.songs);}));
the lists are looped over in chunks to give javascript a chance to breathe and update the display. lowering the chunk size might help it process things better (although itll take longer to get through the lists). would like to have this dynamicly determined, but for now it hardcoded. look for
this.chunk = 50;

Hi  soulfx and thanks for your answer!
Actually I don't have any song files, only playlists.
I have now started to uplad the list in chunks of like 6000. The script seems to always get until about 5000 and then the recognition fails.
What happened yesterday, it seemed that Google Music itself broke down after a couple of list uploads! Several times after the script ran, Google Music would stop working and give me a 404 server error. On another browser (without being logged into my account), the Google Play Music shop would seemingly work, but was also unable to play any song -- and gave a cryptic error message instead.
So maybe we are (the script is) somehow too fast for the Google API, with long lists...?

Oops, I crashed Google again.

Forbidden
Error 403
Google Music, that is.

It seems that everything works when not more than 4000 songs are uploaded at a time. More than 4000, and it doesn't get the additional songs, and then crashes on the next upload.

it could be possible that google doesnt like all the simultaneous search requests from a single client
the script doesn't batch the search requests. if you load up a list of 30,000 songs without google ids it'll make 30,000 simultaneous search requests to google, and probably trigger a denial of service attack detection and mitigation routine.

there was a song in the list around the 4600 mark that was causing a request loop when attempting to resolve a search suggestion that pointed back to itself.  i pushed in a fix for that under b3863ed
with the request loop fixed and a few other improvements I was able to get in 10k songs.  google does have a limit in the amount of requests it handles in a certain period of time, so I would just take the upload in small sections.  if you get the 403 error, just have to wait a bit for it to reset.


Fix button size in safari/on responsive screens

Not sure to what this issue refers, and we may have it covered in this issue in the forked repo, so closing.


Add picture of tablet to README

Requirements

[ ] Capture picture of tablet.
[ ] Add section README detailing functionality.

No longer needed as the tablet is infrequently used.


#588 - Add missing repository rbac roles for porch controllers

This change adds missing repository rbac roles for the porch controllers.
Context -
The use cases are working, but after someone creates a PVS or PV and points to a repo, the controller logs are populated with errors saying the controllers cannot 'get' the repositories.

Could you add some context around this PR please?

Could you add some context around this PR please?

just updated the PR description

/approve
Looks fine to me but let's get some more reviews.

/lgtm

/approve

/approve

/lgtm


QUESTION supporting GPTQ quantized model

Hi there! I noticed that you guys have already added many new models in v0.2.0, which helps a lot.
As of my current understanding, it seems that the quantized model registered in json are GGML version, is that true?
I am working on deploying a coding assistant LLM on one single GPU, and I tried starchat-beta. Unfortunately my VRAM is not large enough for FP16 precision. I found that TheBloke on huggingface also published a GPTQ quantized version of starchat-beta: https://huggingface.co/TheBloke/starchat-beta-GPTQ. So if Xinference supports GPTQ quantized model in addition to GGML ones?

Hi! The format of a custom model can be GGML or PyTorch. GPTQ is not supported yet, but is definitly on our roadmap.
Do you think Starchat-beta GGML works for you? It should be easy to add GGML support since we have already supported it in PyTorch.

Oh, I would be more than happy that GPTQ version also adding to your model list~ Otherwise I will have to try adding it by myself

it seems that the quantized model registered in json are GGML version, is that true?

GGML models support many quantization methods. At the same time, Pytorch model also supports 4-bit and 8-bit quantization.
If you use linux system and have gpu environment, you can try to use 4-bit quantized Pytorch model first. Otherwise you can try 8-bit quantization.
please refer to: https://inference.readthedocs.io/en/latest/models/builtin/starchat-beta.html#models-builtin-starchat-beta

it seems that the quantized model registered in json are GGML version, is that true?

GGML models support many quantization methods. At the same time, Pytorch models also support 4-bit and 8-bit quantization.
If you use linux system and have gpu environment, you can try to use 4-bit quantized Pytorch model first. Otherwise you can try 8-bit quantization.
please refer to: https://inference.readthedocs.io/en/latest/models/builtin/starchat-beta.html#models-builtin-starchat-beta

I run
xinference launch --model-name starchat-beta --size-in-billions 16 --model-format pytorch --quantization 8-bit

and the transformers module starts to cache the original starchat-beta model weights.
I think after all the downloading processes are finished, I still have to utilize my own device to fit the GPTQ quantized model...
Let me see if my GPU device is able to fit that post training quantization. I'll update this post after I try it out.

I am able to launch the model after setting --quantization 8-bit. Thanks a lot.


Jcastets/improve service

will do the updates
Regarding the tests, I will add some eventually — but not now. I want tests to help me develop faster and have a better reliability. Since I broke the backward compatibility in some ways, and I'm likely to break it again, adding tests won't help yet. But I will, I promise!


Add and deprecate incubator/artifactory

What this PR does / why we need it:
Why - The incubator version of artifactory is shown in the new helm hub (https://hub.helm.sh/charts/incubator/artifactory). It should not be shown.
What - Add a deprecated incubator/artifactory (was moved to stable long ago) in order to fix https://github.com/helm/hub/issues/17.
Which issue this PR fixes

fixes https://github.com/helm/hub/issues/17

Special notes for your reviewer:
None
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped

Should I also fix the circleci linting error (this chart is old)?

/approve

@eldada It needs appVersion.

@rimusz - have a look

/lgtm

/assign @unguiculus @prydonius

/ok-to-test
/assign

/lgtm


Change default ports when Thruster is present

Over the weekend, I realized that the exposed port dockerfile-rails generated when Thruster is present is insufficient to make Thurster work transparently. I summed up my findings here but long story short:

Thruster's default port is 80
Thruster's default Puma port is 3000
dockerfile-rails exposes 3000
Services like Traefik, which checks for EXPOSE directives to route traffic to the correct port, will bypass Thruster completely in these cases

I think the easiest solution is to keep exposing 3000 for the sake of backward compatibility (and everyone expects Rails to expose 3000 anyway) but bind Thruster to 3000 and Puma to e.g. 3001, something like this:
if thurster?
 ARG TARGET_PORT=3001
 ARG HTTP_PORT=3000

 EXPOSE ${HTTP_PORT}
end

I can take a stab at a PR for it unless you have a better idea

hmm, Rails will expose 80 apparently, so that's probably easier...


Allow environment to specify location of clang

When using dexters clang builder, it'd be useful to be able to specify
the location of the clang binary to use (a development or historic version
for example). Rather than passing it through the tool, specify it in the
environment as in this patch .

LGTM.  I'll add the same thing to the Windows version.


Adding Schema migration in Sql Migration extension

This PR adds schema migration to the sql migration extension in the database backup page.
There is a a hyperlink button for each source-target database mapping setup for migration. Pressing this button sends an async call to the schema migration nuget. This is setup to be responsive to multiple schema migration calls in quick succession with no ui blocking. The extension is updated based on a callback function that is called when the migrationservice backend sends the corresponding schemamigrationcomplete event back.
Schema migrations can be started as long as it's in failed/notstarted state. Not started maps to showing the 'Migrate' button. Allowing for another migration when in failed state allows for retrying.
Currently there is no display for errors. TODO work is to show where the schema migration nuget is locally logging the progress.
There's an additional bugfix in this PR related to custom getter for targetServerName in statemachine.ts. The previous iteration used a switch statement without breaks. Because of this if you entered the statement from one of the first two cases it would run code for the next two. This was causing migrate button to onyl work on the second press because it needed to set targetServerName to skip the switch statement. Fix is adding breaks.

Can populate the error message on the top?

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 42.319%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
30801

Relevant Lines:
67599

💛  - Coveralls

Sounds good.

Can populate the error message on the top?

I think initially want to just add a message to the local logging path on failure. Haven't had a chance yet though. Will likely use error message construction on top to say check path/to/log for errors since can have many error messages.

Sounds good

why are we doing hyperlink buttons for each source-target database mapping setup.
imo that is a bad design, i.e. if there are a 100 DBs, we will require cx to press 100 buttons to start migrations. think we should have customers to pick which dbs to migrate schema via checkbox and then add a single Migrate Schema

why are we doing hyperlink buttons for each source-target database mapping setup.
imo that is a bad design, i.e. if there are a 100 DBs, we will require cx to press 100 buttons to start migrations. think we should have customers to pick which dbs to migrate schema via checkbox and then add a single Migrate Schema

Yeah I agree with you that was my first plan to go with a checkbox list and a single button click. The current way I was just keeping consistent with the need to click the edit button for every single mapping already. Should be easy to test out a checkbox method though.


[GOT-70] Create a practical plan on how to implement the blue-green deployment strategy

Study the tools that are required to implement the blue-green in GCP and create a plan
From SyncLinear.com | GOT-70

@avichal are you working on this? how's the timeline looking?

sounds good! i moved the ship issues to 5a, and adjusted the project timeline to match on the roadmap.


Added the other not highlighted in yellow tribal locations

Briefly describe your changes
Checklist before requesting a review

[x] My pull request was branched from and targets the test branch
[x] I have performed a self-review of my code
[x] I have manually tested all packages affected (bonus points for automations)
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[x] I have checked to ensure there aren't other open pull requests for the same change

Did you test your feature in the following environments?

[x] Standalone Component
[ ] Standalone Full Editor
[ ] CDC Internal Checks

Posted this as a draft since it might be held until the next release.


Feature request: noatime /etc/fstab

Hello:
I'm writing this because is a 0 effort change and because it's a change that it should be done.
/etc/fstab, should have the noatime option. Here's it why:
https://opensource.com/article/20/6/linux-noatime
https://stackpointer.io/unix/linux-io-performance-tuning-noatime-nodiratime-relatime/388/
This is a direct change (just to add the noatime for the ext4 filesystem).
exfat filesystems, seem to also support this parameter: https://www.systutorials.com/docs/linux/man/8-mount.exfat-fuse/
Modern SSDs are very fast and most distros relay on default values (meaning a relatime value). In the past it was an important thing to consider. We are booting from SD card and the change is worth.
Thank you so much

Hello,
Did you check /etc/fstab?  It's already included for the main sd card 😉

Correction, I didn't add noatime it to the default ext4 partition for the system.  Although Ubuntu 19 mounts partitions using relatime which is not much less performant than noatime, it will save on unneeded writes to the Linux ext4 partition.  I will add this in the next update.  Thanks,


Attempt to make tar work on Windows

The tar commandline requires changes to the path for it to work on Windows. As a result I moved CompressSpecificFilesInDir and DecompressFileToDir into separate Windows and non Windows build files. I also split the tests into separate Windows and non Windows build files, so that they will be able to run build specific tests. All the tests in fileutil are passing on Windows.
I'm still new to Go, so please let me know how I can improve this.
As tar isn't available on Windows by default, so #9 is still advised, but these changes should enable the version of tar that comes with Git to work.

@Fydon Thanks for the PR.  This isn't documented (and probably should be), but we added Windows support to bosh-utils in order to support the bosh-agent, which includes a BSD tar compiled for Windows (note: you will also need zlib.dll).  I believe the source comes from libarchive - we have a story to start building tar in our CI.
We do not use the tar bundled with Git as it does not work with Windows file paths and the Unix paths it accepts are not valid Windows paths.  It breaks interoperability with the Windows API and Go's standard library.  For example:

Path
Windows API
BSD Tar
Git Tar

/Windows/Temp/foo
valid
valid
invalid

/c/Windows/Temp/foo
invalid
invalid
valid

C:\Windows\Temp\foo
valid
valid
invalid

We cannot support one without breaking the other and supporting both would require deducing the version/flavor of tar at runtime, which is not viable.
I think the best solution is for us to improve the documentation around tar on Windows, build tar in our CI and make that tar publicly available (and pointed to in the bosh-utils and bosh-agent docs).

Closing as this PR makes bosh-utils dependent on the tar installed with git-bash and breaks compatibility with cygwin-tar and libarchive-tar (which correctly handles Windows paths.
We created a story to document tar on Windows: 139998715.

i think we are not quite ready to close this PR. the reason why Fydon is making these changes is to make bosh-cli v2 work on windows (not on top of windows stemcells) which cannot rely on a specific tar being present. but you do bring a good point about bosh-utils also being used by the agent (which is good) which does run on a deterministic window image. so the question remains how do we get this to work on top of windows stemcells and arbitrary windows machines -- i think the answer to that is we need to use go std library to do the unpacking for windows impl (and possibly switch linux impl at some point as well).
Sent from my iPhone

On Feb 15, 2017, at 6:38 PM, Charlie Vieth<EMAIL_ADDRESS>wrote:
Closed #11.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Didn't realize this was related to the bosh-cli (it's mentioned in https://github.com/cloudfoundry/bosh-utils/issues/9, but not here).
I would rather not re-open this PR as it would make the bosh-agent and bosh-cli dependent on the tar bundled with git-bash (GPL-2.0).  This would also likely break the bosh-cli for those using the popular cygwin terminal.  Maybe https://github.com/cloudfoundry/bosh-utils/issues/9 or the bosh-cli is a better place for this issue.
Using Go's archive/tar lib would be great, but the lib is spartan.  Maybe we could explore bundling the bsdtar provided by libarchive with the bosh-cli or bosh-utils.

How about using [archiver]?

Merge story #152974592


Investigate github-todos

There is a project that creates issues from todo comments, worth looking into https://github.com/naholyr/github-todos

I'm not entirely sure this is worth it as you'd need to go through them all over again to assign milestones etc.

I think it'll be useful as long as we check the issues after it runs.

I don't like making issues for TODOs, it's duplication. Also, many TODOs are not immediately actionable and they could just pile up. For example: // TODO remove this hack when X is sorted out.
If someone wants to work on TODO things, grep -R TODO . is pretty easy.

Alright guys. Closing this.


Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

I am using https://github.com/ccerhan/LibSVMsharp as a wrapper
When i call LibSVM inside task this error happens after second task started.
If i call libsvm inside main thread, no error happens ever.
If i only start 1 task the error does not happen
As can be seen at the very first image the error is not related to my application or my functions. It is caused by either wrapper or the libSVM.dll itself i dont know which one.
I am using windows 8.1, x64, visual studio 2013, WPF .net 4.5.1 application, 32 gb ram memory on this computer
First here error message

Second error message

Third what works and what causes error

I really need help ty very much

cross-posted (and possibly solved) here:
https://github.com/ccerhan/LibSVMsharp/issues/7

@kritzikratzi how is that solving the problem?


Add "hello world" type example

What article is affected?
Cookbook README
What part(s) of the article would you like to see updated?
I would love to see a super basic example of how to make a hello world on the /local endpoint without using the 'full option' of pulling contracts and generating types.
"Hello world" could look like this gist
Additional information
No response

I think this is what is I wanted to see: https://github.com/kadena-community/kadena.js/pull/167


Newline support?

Hello,
Is there a way to render newlines?
 is the only thing that seems to be working for me. https://www.markdownguide.org/basic-syntax/#line-break-best-practices  suggests ending a line with two spaces should create a new line.

Thanks for the quick response. I was thinking more along the lines of adding extra newlines for added whitespace between lines. For example, if I wanted 4 newlines between two blocks of text.

I understand, however this "issue" is actually part of Markdown specifications.
Carta uses Marked to turn Markdown into HTML, so you'd need to modify it to enable multiple newlines support.
Here is some threads you may find useful:
StackOverflow: Create two blank lines in Markdown.
Marked: Multiple newlines replace with single newline outside of markdown #726.

Thanks again for the update. I originally thought even blank lines with spaces added worked with markdown.
I think I can use some sort of workaround (I am using the input as part of a sveltekit form post), using some reactivity to modify the input that is submitted so that \n isn't stripped. But using CartaEditor, I haven't found a way to separate the input value vs the preview value. Or turn off the preview part and use a custom display instead.
Is this possible?

I'm not sure I understand what you mean when you say you want to prevent the newlines characters \n to be stripped: the value of <CartaEditor > does include the newlines, exactly as they were typed; the fact is that they are not rendered.
Anyway, is here how you can separate the input from the renderer. It is kind of hacky but it works as intended:

	<CartaEditor bind:value mode="tabs" theme="my-theme" {carta} />

	{#key value}
		<CartaViewer theme="my-theme" {value} {carta} />
	{/key}

This is used in the Math Stack Exchange example.

The newlines get stripped when submitting as a form: https://bytesfromkrayon.hashnode.dev/preserving-line-breaks-in-svelte-form-submissions
I think I can probably use the code you showed above. I'm thinking it might be more viable if there was a CartaEditor mode for completely disabling the preview?

Ok, I get that the newlines get stripped when using the default form POST requests, but I don't understand how separating the two editor and the viewer would prevent that

It doesn't by itself, but I was able to use editor and custom process the value before submitting a form. I can then also use carta ssr rendering with my custom process to display the end result.
I could do the same with the editor if I could disable the preview and display my own custom preview instead.

If you think that's the way to go, than you can do it the way mentioned away.
Still, I think it's best to use things as they were supposed to, using a custom endpoint, but that's up to you.
I think I cleared all the doubts regarding the use of this library, so I'll close the issue.
Feel free to open other issues if you come up if any question.


Custom query with join returns too many rows when where references rows in the joined table

The following query, which works as expected in Supabase:
select * from profiles join team_roles on profiles.id = team_roles.profile_id where team_roles.role_id ='ebb25d59-c23f-40f3-8c1c-9cd546d0adb8' and team_roles.team_id = '38324877-b9f9-473c-9a68-5be3f407dc86'
is implemented using createCustomQuery with the query as follows:
        $query = [           'select' => '*',           'from' => 'profiles',           'join' => [             [               'table' => 'team_roles',               'tablekey' => 'profile_id'             ]           ],           'where' => [             'team_roles.role_id' => 'eq.ebb25d59-c23f-40f3-8c1c-9cd546d0adb8',             'team_roles.team_id' => 'eq.38324877-b9f9-473c-9a68-5be3f407dc86'           ]         ];
What happens is that the query returns all the rows from the profiles table rather than just the ones it should. However the ones that it should have returned, do have teams_roles in there with the data from the columns of the joined table. This is good so I can use this to at least get the correct set of rows, but it does seem like a bug that it is returning all the other rows.

Hello Adrian,
It's a pleasure to talk to you.
This problem that you're having is common, because SupaBase doesn't pay much attention to PHP and therefore I end up having to think about several adaptations.
What's happening in your case is that the team_roles table works as a secondary table in the query, and then (I don't know why) Supabase does something like a LEFT JOIN, instead of an INNER JOIN.
My suggestion to try to solve this problem would be to invert the order of the tables, so that it looks like this:
$query = [
    'select' => '*',
    'from'   => 'team_roles',
    'join'   => [
        [
            'table' => 'profiles',
            'tablekey' => 'id' //PUT THE "PROFILES" PK HERE
        ]
    ],
    'where' => [
        'role_id' => 'eq.ebb25d59-c23f-40f3-8c1c-9cd546d0adb8',
        'team_id' => 'eq.38324877-b9f9-473c-9a68-5be3f407dc86'
    ]
];

The fields of the team_roles table will be returned normally, as well as a key called profiles that will contain an array with the profiles returned. Finally, instead of doing a foreach in $listResult, do it in $listResult->profiles.
Try it and see if it works.
Cheers


Page does not address question proposed in title.

This page does not answer the question in the title. It provides a nice analogy about adjustable wrenches but does not explain the pros and cons of using dynamic memory vs. manually resizing with Runtime Memory Resize. Both use cases describe using Runtime Memory Resize. There is no use case showing wen dynamic memory is best.

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

ID: 31043600-8af6-331f-0723-d09332336e3d
Version Independent ID: 883ae7c2-2c19-7721-ca7a-8a2bcc365585
Content: When to use Hyper-V Dynamic Memory versus Runtime Memory Resize
Content Source: virtualization/community/team-blog/2015/20150526-when-to-use-hyper-v-dynamic-memory-versus-runtime-memory-resize.md
Product: virtualization
GitHub Login: @mattbriggs
Microsoft Alias: mabrigg

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


Expose up_info metric with label for potential errors

up is obviously somewhat special. While it's possible to navigate to /targets, wait for the target list to load, and then search for the job/instance having issues, that's hardly a nice way to get at what's the underlying issue. /api/v1/targets exists as well, but that also lives outside of what PromQL can access.
It would be simpler to have an up_info or similar which could expose the current error state and use that as part of alerting.
This comes close to event logging, but I would argue that this is a somewhat special case as it's built into Prometheus so it's hard to get context, otherwise.
https://github.com/RichiH/OpenMetrics/issues/3 is somwhat related to this FR.

This is event logging, which doesn't belong as a metric. There's also a really high bar for adding any metric to be ingested on any scrape, and a metric with unbounded cardinality is not likely to meet that bar.
This was already discussed on #2317

It's not unbounded as the source is Prometheus and it's only fixed strings.

It's unbounded as it may contain arbitrary urls and error messages. This is something for logging and/or tracing.

Given our recent discussions in OpenMetrics about ENUM and STATESET, it is probably possible to find some middle ground in this use case.
I would love to get a somewhat wider discussion regarding this going, but maybe it's best to add something like this to the dev summit.

OpenMetrics doesn't change anything, this is still event logging with unbounded cardinality. This can't be represented as an enum.

You are thinking of the maximally flexible case, whereas I was, and still
am, thinking of having a limited set of information which can be encoded.
For example, no one would require this system to carry dynamic URLs or
return text. Storing HTTP return codes might make sense, but is still
relatively large in space. Library integrations signalling state and
Prometheus using this and other information to categorize would be even
more curated.
On Mon, May 28, 2018 at 10:17 AM Brian Brazil<EMAIL_ADDRESS>wrote:

OpenMetrics doesn't change anything, this is still event logging with
unbounded cardinality. This can't be represented as an enum.

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.

You are asking it to return dynamic text and URLs, as that's what the error from a failed scrape looks like.
I see what you are trying to do, but metrics are fundamentally not suitable for this use case. The only thing it is sane for us to expose as part of every single scrape that happens is up, anything beyond that is debug information which belongs elsewhere such as the Prometheus UI or logs.

There's no information that wasn't considered originally, so closing again.


Support API key or Token in plugin

In backend of translation service, API key or Token is supported. It controls who can access translation interface and the limit for translation.
However, in Web plugins, users cannot input API key or Token now.
API key or Token can be set in the same UI for translation endpoint just like mobile APP.

Done.


add support for custom dump format handlers

Added support for modifying or adding additional format handlers for dumper base

Exactly
On Tue, Jul 24, 2018 at 10:08 AM Ori Hoch<EMAIL_ADDRESS>wrote:

@OriHoch commented on this pull request.
In tests/cli/pipeline-spec.yaml
https://github.com/frictionlessdata/datapackage-pipelines/pull/133#discussion_r204644579
:

parameters:

 url: ../data/datapackage.json

 resource: my-spiffy-resource

run: duplicate

parameters:

 source: my-spiffy-resource

 target-name: my-spiffy-xlsx-resource

 target-path: my-spiffy-resource.xlsx

run: dump.to_path

parameters:

 out-path: custom_formatters

 force-format: false

 counters:

   resource-hash: ''

 file-formatters:

   xlsx: [custom_formatters, XLSXFormat]

sure, and then split on the last dot ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/frictionlessdata/datapackage-pipelines/pull/133#discussion_r204644579,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAQMdaINvPImib3sVrcAuK7Zf4tcz9Kzks5uJsfjgaJpZM4VZ8RJ
.


feat: update edge-agent

closes #577

frontend now served under /wallet/: trustbloc/edge-agent#368.  Users must logout, clear storage, then log back in.
backend has new endpoint /oidc/login: trustbloc/edge-agent#368
@hyperledger/aries-framework-go copied over into agent-js-worker: trustbloc/edge-agent#373
fixed security vulns: trustbloc/edge-agent#371, trustbloc/edge-agent#345, trustbloc/edge-agent#336
blinded routing configuration: trustbloc-edge-agent#367
UI dashboard improvements: trustbloc/edge-agent#365
upgrade to Go 1.15: trustbloc/edge-agent#359
internal enhancements: trustbloc/edge-agent#351, trustbloc/edge-agent#347, trustbloc/edge-agent#338
sidebar: show only wallet-related pages in default mode: trustbloc/edge-agent#349
block access to CHAPI frame for invalid session: trustbloc/edge-agent#344

Signed-off-by: George Aristy<EMAIL_ADDRESS>

@llorllale, I am getting a build failure when compiling using Go v1.15.2 in here. I did a similar changes to the sandbox and fixed them with the following code:
string(rune(DatabaseTimeoutDefault))

@aholovko

@llorllale, I am getting a build failure when compiling using Go v1.15.2 in here. I did similar changes to the sandbox and fixed that particular issue with the rune func:
string(rune(DatabaseTimeoutDefault))

The sandbox hasn't been upgraded to Go 1.15. This PR is about update edge-agent (and related docs).

Opened #579 to upgrade the sandbox to Go 1.15.


Help in running code

Hi. Can  I run this code on our own dataset

Hi @Rabia-Raja sure you can. Just send your dataset in and it should work.

But your code seems very complex. I  tried to understand where I can fix my
.csv file but seriously I did not get any idea. Can you please help me
regarding data fitting
On Sat, Apr 10, 2021 at 9:08 PM Jordi Corbilla @.***>
wrote:

Hi @Rabia-Raja https://github.com/Rabia-Raja sure you can. Just send
your dataset in and it should work.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/JordiCorbilla/stock-prediction-deep-neural-learning/issues/1#issuecomment-817159704,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJK6FSOTWCEF2G4R2EWABYLTIBZZNANCNFSM42WIGQIA
.

@Rabia-Raja sorry for my late reply, do you still need help here?


Add contract id to the position

At the moment we are assuming the user only ever has one "active" position in the database. e.g. proposed, rollover, closing, etc. But due to bugs it can happen that the user ends up with multiple positions in proposed, etc.
In other words our approach on identifying the position related to the dlc channel is very failure prone.
In order to prevent that I propose we add the contract id to the position. That way we can easily find the position based on a dlc message / dlc channel and know with certainty that we are working on the correct position.

E.g. We have 3 open positions by a single user (@bonomat). I presume we ended up in this state as he successfully rejected his subchannel offer and managed to open a new positions. Since we did not update the failed positions to Failed, all positions remained Proposed and have been set to Open once the last order was successfully processed.

Proposal: we tackle this in two iterations:

we add the contract id, e.g. during rollover
we redesign our approach and add the contract id during creation

@holzeis : please copy in the diagram

Adding the contract id is unfortunately not as easy as we would like it to be for several reasons. For one there is no unique id that can always be trusted to identify a dlc channel or contract.

Problem: No real connection between a dlc channel / contract and a position.

Connection is only based on an assumption.

The position is a logical extension of a contract

The dlc channel is merely a vessel to move / transaction on a contract / position.

In the discussions we concluded that the trade is far under developed, with the position model having taking over far too many responsibilities. That lead to the original reason for opening this ticket.

The positions should not have a state. Its are view on the history of trades or contract transactions. And should always be reconstructable from that data.

Below diagram illustrates some thought processes on how a 10101 can better reflect the rust-dlc states. Goal is to be able to imply all 10101 states from the underlying rust-dlc data models.
Challenges

Have a unique id linking 10101 and rust-dlc data.

Closing this ticket in favor of smaller more concrete tickets.


Logic to assign colors for alignment predicates

Overview
Looking at the wireframes, we can see the predicate labels in colored boxes. The color varies between the different labels. There is no indication of how should the colors be applied to the different predicate labels.

Solution proposals
Proposal 1
One logical thinking would be to add colors depending on the weight, that can be read from the skos file and at the moment of loading the "Synthetic Spine Property Mapping By Category" screen, is available as an attribute of each predicate object.
Proposal 2
Another different way of achieving this would be to add a hexadecimal color code to the skos file, so we can read and use it by simply adding it to the "background-color" CSS rule.
Proposal 3
We could avoid touching the skos file or even adding logic to it by simply hardcoding the color values in the predicates model now. This solution may work but need technical input for sure if we need to modify it. But this also can be included in the second stage so we can add it to the administrative dashboard as an option to let the users modify the color by selecting it from a color palette.
Preferred solution and why:
Proposal 3. We can solve the issue rapidly and be perfectly prepared to let the user modify it when the administrative dashboard is implemented.
Please let me know your thoughts @stuartasutton.

I agree that adding any logic to the SKOS file to handle this should be left to Phase 3 if done at all and could be part of  the functions of the administrative dashboard to allow the administrator to select colors after the mapping predicate SKOS file has been uploaded.
For now, here are the colors Nate's viewer provides:

PR #74 under review

Covered with PR #74


Feature request: ability to disable sounds

I think it could be nice if we could disable the new sounds for upcoming events.
Right now the only option, as far as I can tell, is to disable alerts entirely for each calendar.

I will add a new setting to disable them 👍🏻


Only select enabled activities on the dashboard

Description
There is a problem sometimes with Models that are not configured or enabled in the twill.dashboard.modules config.
The activity is logged for every model regardless of whether or not this Model is displayed in the dashboard. And this is a good thing.
The problem is when the last 20 activities are from an not configured model. When that happens nothing is displayed in the activity section.
This PR changes how the activities are selected by only selecting those which are enabled.

Hey @smeeckaert,
Thank you for your contribution. I have looked at it and applied your changes to this 3.x branch: https://github.com/area17/twill/pull/1787
One thing that was missing was the implementation for morph maps. I will backport that change then this will be good to go.
Kind regards,


Support JPEG XL images

As I see it, JPEG XL is going to be the dominant image format on the web, and probably also outside the web. It would be nice to start the process of supporting it now, so that it is completely ready and stable when people start using it.
The libjxl package makes it very clear that it isn't secure yet, but I don't see that as a major issue, because:

It will be running completely sandboxed
Given that it is very new and not really used yet, it is not a target (and should be secure when it becomes a target)
If users need high security, they can tell vips to disable any call to the libjxl package, or write their own guards against JPEG XL files

The goal of this PR is to build a working implementation that can handle >90% of images without crashing. libjxl is still under major development, so ironing out all bugs and optimizing speed could be a complete waste of time. We can always do that later when the package stabilizes a bit more.
Things to do:

[x] Get it to compile
[x] Build dependencies correctly
[x] Resolve build time errors
[x] Make it not crash at runtime
[x] Make tests
[x] Polish everything

Things that are not included in this PR:

benchmarking suite
advanced tests

Everything compiles now, and wasm-vips can be launched and will handle all other image formats normally. Anything that requires libjxl to spin up will result in an infinite loop :)

Great! I still need to think about whether to distribute JPEG XL support by default. Issue https://github.com/libvips/build-win64-mxe/issues/40 might also be relevant here.
I had a look at the build, and fixed a few things, see:
https://github.com/atjn/wasm-vips/compare/libjxl...kleisauke:wasm-vips:libjxl-atjn
The hwy_list_targets target still seems to fail, and building with:
-DCMAKE_CROSSCOMPILING_EMULATOR="$EMSDK_NODE;--experimental-wasm-threads;--experimental-wasm-simd"

Doesn't seem to work. I think it's safe to ignore that error for now. emsdk probably needs to update its Node version to 16.4.0 or higher to match the final SIMD opcodes (see https://github.com/emscripten-core/emsdk/issues/1064).

jxlload is now working with commit https://github.com/kleisauke/wasm-vips/commit/8a6e02d3309b5836277bdc6fa8b40b11d74fb5e6. Here's an playground link to test with.
jxlsave produces broken images, but I was able to reproduce that on Linux as well, I just opened issue https://github.com/libvips/libvips/issues/2987 for this.

Wow, that is some nice and speedy work you made here! Feel free to commit all those changes to this branch. I can also do it, but I think it might attribute the changes to me.

I still need to think about whether to distribute JPEG XL support by default.

I would strongly argue for distributing JXL support by default. However, I do think it would be completely reasonable to disable JXL parsing by default, but make it possible to turn it on at runtime through the API somehow. Or you can count on the user to disable JXL themselves if they feel it is a safety issue for them.
My reasoning:
All browsers support methods of delivering JXL images today, so that when browsers eventually support it by default, it will instantly be used (see picture, image-set). I already use JXL on some sites today to gather experience before they are supported by default.
You could argue that we can just wait and enable support the moment that the first browser supports JXL, but it is very likely that some systems will be using wasm-vips as a dependency of a dependency of a dependency which might not be able to update to a newer version immediately. However if older versions already supported JXL with a runtime flag, tools could enable that flag and immediately enable support.
By using a flag, you are also able to keep that flag well after JXL has been supported in browsers, in case you still don't think that it is mature in wasm-vips.
There is also the case of non-browser workflows. Some software already supports JXL, and I have heard of places where JXL is the new standard. If somebody wants to build a quick webapp that handles these images, wasm-vips would be a great solution, but only if it support JXL.

The hwy_list_targets target still seems to fail

Yeah, highway recommends using the V8 engine directly to build it exactly because SIMD isn't supported in node 14. Another solution is to force a newer node version. I thought the same as you; if it compiles and works, then just let it be and wait for the inevitable upstream patch that solves this problem.

Feel free to commit all those changes to this branch.

I just pushed it to the branch associated with this PR.

IMO the best path forward would be to include libjxl by default and then support vips_block_untrusted_set and vips_operation_block_set. These functions allow people to easily block all untrusted operations (including anything that uses libjxl) with:
vips.blockUntrustedSet(true);

Or specifically disable JPEG XL features with:
vips.operationBlockSet("VipsForeignLoadJxl", true);
vips.operationBlockSet("VipsForeignSaveJxl", true);

You could even apply the JXL-specific block by default, and tell people to disable the block in their code if they want to have JXL support.
I will see if I can figure out how to make a PR for supporting those two functions.

I think exposing vips_block_untrusted_set() and vips_operation_block_set() is good idea anyway.
Another concern with enabling JPEG XL support by default is that the binary size (vips.wasm) would increase by ~44% (~2.1 MB). This is fine for non-web/CLI usage (the pre-built binaries provided by sharp are ~16 MB in comparison), but for web usage it's probably a bit too big, especially if a user doesn't use jxlload* and jxlsave*.
To fix this, we could enable the GModule implementation and build a dynamically loadable module for libjxl (vips-jxl.wasm). JPEG XL support is then enabled on the web once the dynamic module is served, and on non-web environments it's enabled by default when you install wasm-vips via the package manager.
If you want, I can look into this next week, it would probably require dropping this patch:
https://github.com/kleisauke/wasm-vips/blob/5e3b052fb6cdfc1a04d4e791f7bd56935fd00565/build/patches/glib-emscripten.patch#L169-L189

we could enable the GModule implementation and build a dynamically loadable module for libjxl

If you are willing to spend the time on it, I think that would be awesome! It would also allow us to support much less used formats like AVIF, SVG and JPEG 2000 without worrying about file size ballooning.
With that said, I don't think it is strictly necessary for the libjxl implementation. It will only increase load times ~400ms -> ~530ms over the global medium mobile speed. Over a state-of-the-art connection, it is more like ~35ms -> ~46ms. And it's not just for a gimmick, everything is pointing towards JPEG XL becoming the universal standard for web encoded images.

Commit 995eba0242b674332107dc91087371aaec9916f6 builds this as a shared module. JPEG XL support is still enabled by default on all environments, but you can choose to opt-out by doing:
const vips = await Vips({
  // Disable dynamic modules
  dynamicLibraries: []
});

Awesome!

v0.0.4 is now available. Dynamic modules can be disabled on the playground by passing the ?disableModules query string.
https://wasm-vips.kleisauke.nl/playground/?disableModules
Also, /playground-jxl is now being redirected to /playground, to ensure that the above URLs still work.

@kleisauke Do I understand right that JPEG-XL is built only when building with dynamic modules support? If so, can "Compiling jxl" be skipped when using --disable-modules? Or is it switched to static linking in that case?

As I see it, JPEG XL is going to be the dominant image format on the web, and probably also outside the web.

By the way, ICYMI: Chrome removes the experimental JPEG-XL in upcoming versions, and other browsers never shipped it. That makes a lot of people unhappy, but the chances for it to become a common format seem pretty low if this goes through as currently expected. https://bugs.chromium.org/p/chromium/issues/detail?id=1178058

Do I understand right that JPEG-XL is built only when building with dynamic modules support? If so, can "Compiling jxl" be skipped when using --disable-modules? Or is it switched to static linking in that case?

The --disable-modules build parameter will disable the build of dynamic  modules and load-time dynamic linking. When this parameter is passed, modules are instead being statically linked in vips.wasm. Note that JPEG XL load/save can also be disabled at runtime using:
vips.blockUntrusted(true);
// Or:
// vips.operationBlock('VipsForeignLoadJxl', true)
// vips.operationBlock('VipsForeignSaveJxl', true)

(see commit https://github.com/google/oss-fuzz/commit/890953f0a0029ef889c8c866c674bb8609f90bd0)
This libvips binding is the first to ship with JPEG XL support by default, and I intend to maintain/release this as a dynamic module in further releases. We could argue for having this opt-out by default on web (see modules-web-pre.js), but I imagine this library is also suitable for use as a polyfill.
I'm happy to accept a PR that adds a --disable-jxl build parameter or something similar, most people will not need to run the build script, but it might be an convenient way to reduce the binary size (https://packagephobia.com/result?p=wasm-vips).

Chrome removes the experimental JPEG-XL in upcoming versions

It looks like Google already changed its tone from "we will remove it" to "no support at this time".
https://www.thehindubusinessline.com/info-tech/google-chrome-removes-jpeg-xl-image-support/article66094598.ece

It looks like Google already changed its tone from "we will remove it" to "no support at this time".
thehindubusinessline.com/info-tech/google-chrome-removes-jpeg-xl-image-support/article66094598.ece

I'm not sure 3rd-party publisher's interpretation should be taken for a source of truth. I didn't see change in tone on the public communication on the bug.

I'm not sure 3rd-party publisher's interpretation should be taken for a source of truth.

You're right, I should probably link CNET's article here, which includes the same statement from Google.
https://www.cnet.com/tech/computing/chrome-banishes-jpeg-xl-photo-format-that-could-save-phone-space/

I didn't see change in tone on the public communication on the bug.

Indeed, it's a bit curious that it was communicated this way.

Indeed, it's a bit curious that it was communicated this way.

I think it's just "business-speak" language.


Switch from ImmutableOpenMap to Map in AliasExistsMatcher

Description
Addresses comments raised here: https://github.com/opensearch-project/security/pull/2715#discussion_r1177857146
There is a compilation error in AliasExistsMatcher and this fixes the issue.

Category (Enhancement, New feature, Bug fix, Test fix, Refactoring, Maintenance, Documentation)

Maintenance
Check List

[ ] New functionality includes testing
[ ] New functionality has been documented
[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #2725 (8d63c02) into main (6ace852) will increase coverage by 0.03%.
The diff coverage is n/a.

:exclamation: Current head 8d63c02 differs from pull request most recent head 8e05b2c. Consider uploading reports for the commit 8e05b2c to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff              @@
##               main    #2725      +/-   ##
============================================
+ Coverage     61.48%   61.52%   +0.03%
- Complexity     3394     3398       +4
============================================
  Files           272      272
  Lines         18743    18743
  Branches       3285     3285
============================================
+ Hits          11524    11531       +7
+ Misses         5616     5613       -3
+ Partials       1603     1599       -4

see 2 files with indirect coverage changes


bug: Chrome://inspector is not remove

Type: bug
Ionic Version: 1.x
Platform: all
I am unable to remove chrome://inspect remote debugging after final release version of apk! Anyone any idea how make it possible for security reason?
Thanks

Hello! Thanks for opening an issue with us! As this seems like more of a support question i will urge that you ask this question on our forum. Thanks for using Ionic!


Excel OpenSpout exporter

Thanks for merging the previous PR! I forgot to add a couple additional requested features to the export, namely a freeze row and AutoFilter.
So that's in this PR.
If this PR is good like this, could you make a new release? Then we can start using the new exporter.
Thanks in advance!

Thnx!


Various fixes and improvements

Q
A

Branch
master

Bug fix?
yes

New feature?
yes

BC breaks?
no

Deprecations?
no

Fixed tickets

License
MIT

Various improvements and fixes. plus some new stuff. Yes, I should have written some tests 🙄  but I'm already behind on everything. and I hope to do some major improvements later. 🙂
At least the commits are atomic.

Style problems.. sure, why not. 💀


[WIP] Cache Refactor Branch

Overview
This PR makes a few big changes:

Removes scaffeine and heap backed memcached client inside the tile server
Removes TTLs on tiles
Makes request for scene data only when the web tile intersects the extent of the web tile
Introduces separate execution contexts for cache and attribute store interactions + separates out blocking operations inside the tile server with a blocking execution context
Adds settings for various knobs via environment variables for caches
Various cleanup on formatting

Checklist
~- [ ] Styleguide updated, if necessary~
~- [ ] Swagger specification updated, if necessary~
~- [ ] Symlinks from new migrations present or corrected for any new migrations~
Demo
See https://github.com/azavea/raster-foundry/issues/2306#issuecomment-317564849 for various benchmarks
Notes
Opened https://github.com/azavea/raster-foundry/issues/2304 to deal with new Hikari issue. Tile server should like be refactored to work in similar fashion to the API server for consistency.
Testing Instructions

Start servers
Verify that things get cached -- there are still initial timeouts on thumbnails; however, that likely requires additional work. I think we are just making too big of a request for tiles that we are resampling anyway.

Closes #2306

@pomadchin Good points all around. I think we got the tile server into a good spot without having to sacrifice all caching. This should be good to review now.
Some notes on timings with new settings are available https://github.com/azavea/raster-foundry/issues/2306#issuecomment-317564849


[BUG]

The possition of the feed is not saved and automatically returns to the most recent tweet

I'm not 100% sure from the description, but this is a duplicate of either #57 or #237, so closing for now.
If this is a duplicate of #237, then a fix has been made and released in the latest version (v2.14.1), which is available to download from GitHub releases, or from F-Droid in a few days!


TypeLookup Service [6285]

This PR adds the TypeLookup Service feature, described in the XTypes 1.2 document and some cool features like the possibility to be notified on type discovering and registering the remote type automatically (negotiating at background using the new TypeLookup service).

Build status:

Linux
Mac
Windows

Build status:

Linux
Mac
Windows

Build status:

Linux
Mac
Windows

Build status:

Linux
Mac
Windows

Build status:

Linux
Mac
Windows

Build status:

Linux
Mac
Windows

Build status:

Linux
Mac
Windows

Build status:

Linux
Mac
Windows

Build status:

Linux
Mac
Windows

The DDS/DynamicHelloWorldExample throws the following error:
[DYN_TYPES Error] Error building type. The current descriptor isn't consistent. -> Function build

When you try to run the publisher before launching the subscriber

I cannot reproduce this problem.

Maybe reported problems with the example and the tests were solved by the requested changes?

Build status:

Linux
Mac
Windows

Build status:

Linux
Mac
Windows

Build status:

Linux
Mac
Windows

DDSSimpleCommunicationTypeDiscovery failed on Windows (see here)

DDSSimpleCommunicationTypeDiscovery failed on Windows (see here)

Yes, it is unlikely but possible. It is due to a data race in RTPSParticipantImpl. See #6557 for further information.

Build status:

Linux
Mac
Windows
Performance

Build status:

Linux
Mac
Windows
Performance

@LuisGP There is one warning on Windows

Build status:

Linux
Mac
Windows
Performance

Build failures are unrelated.


Redundant legends for collapsed buildings

When exploring the M4.9 Georgia Strait scenario, I was looking at the number of collapsed buildings at the CSD level. The legend has 20 different colours to represent 0-1 and 1-1 casualties. This is confusing because it's obviously way too many legend colours, such that I can't tell the difference between several of them anyways, and 1-1 is meaningless.

Thanks Tiegan!  I can see it too:

I wonder if we could try fixing it by reducing the rounding, i.e. increase the number of significant digits?  Even though a building is either collapsed or not collapsed (i.e. whole number), I guess the user would understand it is some kind of probability and thus would accept seeing decimal numbers.
That said, I agree that 20 different shades of colours are too many, especially in this case.  Perhaps something like 5 to 10 different colours?

Hey @anthonyfok - thanks for looking into this!
My initial thought is that I don't think we want to change the rounding because we wanted to avoid showing people fractions (hard to understand and probably too precise), although I agree that using red to represent 1 collapsed building is going to be misleading and it's tricky to set it up as a binary (<1, >1). Since we are using fractions in the y-axes of our bar charts, I think it can be appropriate to add a more detailed legend to the map. So let's increase significant figures for the legend to 1 (ex: 0.1 collapsed buildings) and reduce to 5 shades, if that works.
Will this impact only this scenario or should we think about how to apply this to others?