Change api domain value to binary in rebar3_hex_user

The domain value for write permissions should be a binary vs an atom.
Since upgrading to hex_core 0.8.2 the domain value must be a binary instead of an atom. I say hex_core 0.8.2 as that's the only thing that has changed. It's possible something changed on hexpm side as well, regardless, it should not be an atom 😁
Edit:
It's not hex_core, hex_core still has the value defined as an atom, but it doesn't get converted, and hexpm wants a binary, not an atom. May be a bug in hex_core.

@wojtekmach Is there a bug in hex_core either in the type spec or in protobufs? If hex_core is supposed to handle the conversion to a binary, then it's a bug bug, if it's not then it's a type spec bug.

hex_core should standardise around strings, see https://github.com/hexpm/hex_core/issues/71, so this change is definitely in the right direction.

hex_core should standardise around ~strings~ binaries, see hexpm/hex_core#71, so this change is definitely in the right direction.

Right on, we can just tell dialyzer to ignore the this call until a new release of hex_core is done

I'm not keen on all the nowarn stuff, but I guess you could create an issue to review this later, lest real warnings are hidden too.

Yeah, I'll make an issue. I'm also following the issue on hex_core.


Is the timeline view broken?

The layout doesn't seem quite right to me. But I don't know if it used to look different from how it is now. If it's wrong, I'd be happy to look into a fix. This is another part of the frontend where a third-party library is being pulled in.

The timeline has now been reimplemented, in any case: https://ctg-redux.pages.dev/timeline


KAFKA-14198: Define separate swagger configuration in Gradle build

Follow-up from https://github.com/apache/kafka/pull/12609. Non-urgent, just tidies up the build file a bit.
Tested and verified locally by:

Running ./gradlew releaseTarGz and then examining the resulting release artifact with tar tf tar tf core/build/distributions/kafka_2.13-3.4.0-SNAPSHOT.tgz to ensure that it did not contain the swaggerJaxrs2 jar or its dependencies
Running ./gradlew siteDocsTar and then examining the resulting docs with cat docs/generated/connect_rest.yaml to ensure that all Connect REST endpoints were included.

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Thanks @C0urante. Did you verify that the documentation is still generated correctly and the release tarball still doesn't have swagger and snakyaml in the dependencies?

Thanks @ijuma. Yes, I verified both, and updated the PR description with the steps I took to do so.

Thanks Ismael. Kicked off another Jenkins build since the previous one failed with a disk space error; will merge if everything looks alright.

Failures appear unrelated, merging.

@ijuma @jsancio I'm assuming we don't need to backport this to 3.3 since the immediate issues with Swagger deps and Connect OpenAPI docs generation have already been fixed on that branch; let me know if that's not the case, though.


Adapt module

Thank you for your contribution @YassineLambarki 👍
I know that the ruff format check in the CI pipeline is a little bit pedantic, but could you please apply ruff format . to this PR?
Please add a summary and reasons of the changes.


Disconnected Event Appears as 'new' on _updateConnectionState

Browsers and versions affected
Edge shim.
Description
RTCPeerConnection.prototype._updateConnectionState states object does not define a disconnected property. When the transceiver.iceTransport.state or transceiver.dtlsTransport.state is 'disconnected' it results in a value of NaN which therefore emits the default state of 'new'.
Expected results
'disconnected' event should be emitted.
Actual results
'new' event is emitted.

Thank you, i've just seen this too. PR to fix this is in #566


Create LICENSE

This pull request is part of an initiative to make the licensing information about OBO Foundry ontologies more actionable.
While this ontology contains licensing information in its metadata, GitHub is not aware of the license unless you create a LICENSE file with standardized text. This PR creates a LICENSE file with the standard text for the CC BY 4.0 license.
More information about this initiative and further discussion is taking place here: https://github.com/OBOFoundry/OBOFoundry.github.io/issues/1840.

@addiehl - tagging you and putting you as reviewer as you are the contact person for CL. Probably can just merge this in, but didn't want to do it without your thumbs up :) thanks

Is the one failed check significant?

@addiehl seems irrelevant to this PR

Is the one failed check significant?

Nope - that just tries to post the diff. I think its cause of permissions on GitHub Token cause of the creator of the PR that disallows automated posting, but it isn't important to the PR

Thanks Charles and Shawn


Revise schedule

I pasted our tentative schedule on the README. Do we need to revise this or will we keep it as is?

We might be able to drop Jupyter from the schedule. There are other workshops covering it and we probably won't use much in the workshop if we're covering packaging and testing (both things that don't fit well with notebooks).

It's a tad bit long, no? I do like Jupyter as an example and it would be really cool to show people who to set it up in a way to directly run an example on binder. But I agree that its not necesasary for the workshop and its the only things that's simple to cut. The rest seems pretty mandatory to me.

There is a whole other workshop on Jupyter on the Sunday, so if we need to drop it, I think that is okay. If we happen to use it as one of our tools in a demo, we can inject a bit of verbage there, but I agree that it doesn't formally need to be on the schedule


How to reduces specified consecutive characters  in collector.referrer-link-text?

Sometimes I have collector.referrer-link-text=\r\n\r\n\t\t\t\r\n            Some text ....\r\n            \r\n\r\n\r\n\t\t\tSome text ....
How to reduces specified consecutive characters or strings to only one instance in collector.referrer-link-text?

My solution with ScriptTagger in JavaScript:
  <tagger class="com.norconex.importer.handler.tagger.impl.ScriptTagger">
    <script><![CDATA[
		var referrerLinkText = metadata.getString('collector.referrer-link-text');
		if (referrerLinkText != null) {
			var result = referrerLinkText.replace(/\s+/gi, ' ').trim();
			metadata.addString('referrer-link-text', result);
		}
    ]]></script>
  </tagger>

But I'm not sure it's the most efficient one.

What you have looks fine to me.  You could also use the ReplaceTagger, like this (untested):
<tagger class="com.norconex.importer.handler.tagger.impl.ReplaceTagger">
  <replace fromField="collector.referrer-link-text" regex="true" replaceAll="true">
    <fromValue>\s+</fromValue>
    <toValue xml:space="preserve"> </toValue>
  </replace>
</tagger>

Thanks for your help. The solution you're proposing also works very well.


Documentation

Can you add a documentation to get started?
Thanks for your effort.

Did you try the example in the example directory?

I got it running on iOS, there was an issue with the pods.
Happy to do a pull request in a bit.


ResponseJSON is not working with the given example

Alamofire.request(.GET, "http://localhost:3000/iosData")
.responseJSON { _, _, result in
print(result)
debugPrint(result)
print("Parsed JSON: (result.value)")
}
I have used this template given in the example but while compiling it is giving error
"(,,_) Void is not convertible to 'Response<AndObject, NSError> -> Void'"

Did you get anywhere with this issue? as I'am having the same issue on this latest commit

Some how yes :)
Just checked the release note for the latest release, it is still not updated in the ReadMe.
Use the syntax below : (Still not sure how to parse the data, if is there any inbuilt support for that or not). I am using SwiftyJSON for that.
.responseJSON { response in
print(response.request)
print(response.response)
print(response.data)
print(response.result.value);
}

Ha thats what I just got working, Ye i use SwiftyJSON for parsing

When i run now I get the following issue with the response.swift file
Generic type 'Result' specialized with too many type parameters (got 2, but expected 1)

Check this out
https://github.com/antitypical/Result/issues/77
Probably, you will get what you are looking for.

Yea, still not luck, what did you do to get it working?

I didn't got such issue. I am working with
Mac OS - (10.10.5)
Xcode - version 7
Swift - version 2
AlamoreFire - Version 3.0.0-beta.1

just use
response()
(request, response, data, error)  in
and  then

I used this (validation example).. works on latest
Alamofire.request(.GET, "http://httpbin.org/get", parameters: ["foo": "bar"])
.validate()
.responseJSON { _, , result in
switch result {
case .Success:
print("Validation Successful")
case .Failure(, let error):
print(error)
}
}

You guys really need to read through the commits if you're running off master instead of the official "Latest Release". Otherwise you run the risk of the documentation being a bit out-of-date. Considering that master currently contains the Alamofire 3.0.0-beta.1 pre-release changes, the docs are significantly out-of-date. This will be resolved over the next couple of days.
If you are running on 2.0.2, @peteclark3's example will work. If you are running on master or Alamofire 3.0.0-beta.1, you need to use the new response type:
Alamofire.request(.GET, "https://httpbin.org/get")
    .responseJSON { response in
        debugPrint(response)

        if let JSON = response.result.value {
            print(JSON)
        }
    }

FYI, I'm running the latest that Cocoapods gives me.
On Tue, Sep 22, 2015 at 11:05 AM Christian Noon<EMAIL_ADDRESS>wrote:

You guys really need to read through the commits if you're running off
master instead of the official "Latest Release". Otherwise you run the risk
of the documentation being a bit out-of-date. Considering that master
currently contains the Alamofire 3.0.0-beta.1 pre-release changes, the docs
are significantly out-of-date. This will be resolved over the next couple
of days.
If you are running on 2.0.2, @peteclark3 https://github.com/peteclark3's
example will work. If you are running on master or Alamofire 3.0.0-beta.1,
you need to use the new response type:
Alamofire.request(.GET, "https://httpbin.org/get")
.responseJSON { response in
debugPrint(response)
    if let JSON = response.result.value {
        print(JSON)
    }
}

—
Reply to this email directly or view it on GitHub
https://github.com/Alamofire/Alamofire/issues/800#issuecomment-142315997
.

@cnoon how do you handle the error or failure case?

:+1: @kapildave6 @marklochrie50265 @Lawgrin @peteclark3 any luck with this?

I'm fine with my example on 2.0.2.  If you want to look at error handling on master or 3.0.0-beta.1 I would say look at the source, e.g. https://github.com/Alamofire/Alamofire/blob/master/Source/ResponseSerialization.swift
let response = Response<T.SerializedObject, T.ErrorObject>(
                request: self.request,
                response: self.response,
                data: self.delegate.data,
                result: result
            )

Or just run his examples and set a breakpoint...

thanks @peteclark3 i have been looking at the source and the response serialization code is pretty confusing. i'm just ignoring errors for now.

The documentation is forthcoming gents. Please be patient. The Alamofire 3.0.0-beta.1 is a "pre-release", not an official release.


Supports Web and Windows Desktop

Did you have any plan to support web and windows?

At present, we have completed the development of the basic functions and are in the stage of experience optimization, function supplementation, and defect fixing.
There are currently no plans to support web or Windows compatibility in the near future, but we will consider supporting them in the future.


Extasy Coco Amber Use Case Fails on Stampede

When I run the Extasy Coco Amber Use Case Fails on Stampede. The log file is here:
https://gist.github.com/iparask/00b893c19cca5f19eab8

Whoops

Uploaded again!
https://gist.github.com/iparask/5e75c66170fe257203ac

This is pretty old (feb 18), please try again whenever possible.

This was because of permissions. Resolved.


Firefox & Thunderbird crashing

They crash when using the fedora repo packages with segmentation fault, but the flatpak versions work. In gnome both repo & flatpak versions work.

Nvidia card? The Nvidia page of Hyprland's wiki (and the Arch wiki too) mentions adding these two lines, but I had to comment them to get Firefox and Thunderbird working
export GBM_BACKEND=nvidia-drm
export __GLX_VENDOR_LIBRARY_NAME=nvidia

I also noticed better performance after commenting these lines

Yeah Nvidia, always the culprit. I'll try that out later, thanks. Though any disadvantages to removing them? Im actually using a AMD & Nvidia Optimus laptop

I'm not fully sure myself either. The Arch wiki explains what those lines do. They force GBM as a backend. But I'm not sure if it uses GBM without those lines.
I also read somewhere that wlroots doesn't support EGLStreams, which means Hyprland must be using GBM regardless.

Removing the two variables fixed. Thanks

Hi,
Let me leave my comment here in order to - hopefully - save somebody some tears.
I had a problem with Thunderbird crashing on my machine.
In my case installing a notification deamon helped. Looks like thunderbird desperately needs something like this.
I installed dunst, but I guess pretty much anything would solve the problem.


Type not widened by assignment in switch statements

var a = "";
var b = "";
declare var x: mixed;
switch (x) {
  case "foo":
    a = 0;
  default:
    b = 0;
}
(a : string); // no error, expected number ~> string
(b : string); // no error, expected number ~> string

@mroch Any idea what's going on in this example? I was trying to write a counter example for let/const, but wasn't able to trigger an expected error, leading me to this.

Oh, after slightly more digging, it's the presence of the default case that prevents widening. If I remove the default case, then I see the expected error for a.

adding a break at the end of the first case also seems to make both a and b error, so this sounds like a problem with fallthrough merging.

I think I've found the bug (at least from my testing) and the fix is relatively simple; I can make a pull request for it tonight.  I was wondering if there was a good way to add test cases for this so it doesn't break in the future -- the test cases I wrote to debug this obviously are intended to fail once the bug is fixed; I basically just adapted the code from the original issue and it fails once the proper types are inferred.

@ngavalas That's awesome! IMO, the best test cases are the ones that add expected error output, because then the test suite assets not only on the existence of the error, but also the quality of it—in particular the locations associated with the error. Obviously expected to fail is the best kind of expected to fail. :smiley:

Ah, I see now, the output gets diffed with the .exp file in the test directory.  I'll work on making sure this change doesn't break anything else then.

We can move the discussion to #792 if you'd like, but I have definitely identified the issue and why it happens, but I'm not sure what the most correct way to fix it is.  What I did certainly works and all of the test cases still pass (it produces the correct errors from number->string at the annotation, not at the a=0 assignment site), so I do believe it's correct, but we could also go down the route of havoc'ing the new changeset in all cases also -- I'm not sure of what the consequences of either choice are in the long run.


Remove superfluous flow control

hide the inlet address from the other side in kafka workers
removed superfluous flow control

Draft because i want to do some extra validation on the MultiAddr instantiation

double-checked!


Question: .NETStandard 2.0 support

Greetings,
Is there any hard rule to keep .NET dependencies >= .NETStandard,Version=2.1.
Can this support Version=2.0 too?

Greetings,
There shouldn't be any hard rule for why not supporting NETStandard 2.0, but it require some code changes since some language features are not supported in NETStandard 2.0.
Nothing too hard to do, I will try to include it in the next release.

NETStandard 2.0 would allow to use the package also in full framework. Therefore if there's no hard dependency on Core, NETStandard 2.0 would be preferable.

@BrightLight, yeah, we should be able to support NETStandard 2.0. Hoping to do that with the new release I'm working on towards the end of this month.

Hey Moaid,
I was just a bit interested in how to add .NET Standard 2.0 support and did it in the following branch:
https://github.com/Hejle/Dumpify/tree/feature/netstandard2.0_support
Just letting you know in case you want to take inspiration from it, however I am pretty sure its not a complete or good version - Looking at you DumpColor.cs
But yeah, if you already have it all solved you can just ignore this.

Hi @Hejle, thanks for this!
I will need to do some small adjustments, hoping to merge it this weekend.

Looking forward to see the adjustments!

Hi @Hejle, I'm almost done. I did some modifications, but the result was inspired by your branch.
Since you worked hard on this, do you want to be the one to marge the PR so that you can get contribution credits? :)
If it interest you, I'll share my branch, and you could create a PR from it (or copy it to your branch for the commits).

@sadedil, @BrightLight, the work on this feature is done, and it should be part of the next release, which is due this month. Thank you for suggesting it :)
@Hejle, the following is my branch. If you are interested in contribution (commit) credits, please say so and we will figure out a way. I'm planning to merge this branch into master during the weekend, but I can delay it if you need more time :)
Regardless of contribution credits, I will mention you in the Release Notes of the next version.
https://github.com/MoaidHathot/Dumpify/tree/feature/netstandard2.0

That sounds great @MoaidHathot.
I will see if I can get it into my branch and make the PR, but if not, its not a big deal.
I will look at it today or tomorrow. :)

@BrightLight, @sadedil, @Hejle, the PR was merged into Main. I'll release the new version before end of month.
Thanks @Hejle for the contribution!   #7

@MoaidHathot, @Hejle thank you both.


Fixed ground clamping example to zoom to geometries

Polygons, corridors and rectangles don't have an Entity.position so they can't be tracked. Fixed to use zoomTo.

@pjcozzi We probably want to get this in for 1.23.

Looks good, thanks!


Favourites bar for symbols

Create a favourites bar in the top navigation to show the recently used symbol for quick access.

@LazuLitee it would take 1h at most to fix it. I can do it. someone then just needs to review it.

@yeller0205 That would be nice. I think we can somehow manage the rest.


Supports spin

Goal

Supports spin

Checklist

[x] Testing in compability platforms
[x] Installed correct via Swift Package Manager and Cocoapods

Lovely, thanks!


An option to default spawaning of windown in right side of the screen

I am currently using Polonium installed directly from KDE store in Fedora 38.
The old kwin-script used to follow 'Meta+T setup' set by the user.
Polonium however does not rely on the user settings and it seems to dynamically change 'Meta+T setup' acording to the number of windows. This is cool and I appreciate that as I don't need to care about the 'Meta+T setup' anymore.
However, by default, Polonium spawns the third window in left corner. Although I prefer the natural right corner spawning which is default in swaywm. In the old kwin-script this was not a problem as I could change the 'Meta+T' settings acording to that.
Kindly enable such option or suggest any workaround.
Thanks for your awesome work!!

Works as expected. Thanks a lot!!


Update python-dotenv pin to allow 1.0 release

Python dotenv released 1.0.0, and other packages are starting to pin to >=1.0.0, which ends up forcing pip to downgrade confz to an old release with a looser pin on dotenv.
The changelog doesn't look too crazy, and in my own environment I haven't noticed any problems, so I suggest updating the pin to include at least the 1.0 versions.

Totally agree, comming soon

See release 1.8.2


Fix ReadMe documentation link

Changelog:

Update API link to https://www.ibm.com/docs/en/instana-observability/current?topic=monitoring-ios-api#instana-ios-agent-api

#Description
Update the API page link, Pervious like was showing 404 as shown in the attachment.

@tapwork @ginger99 can only one you please have a look 👀 🙏

Looks good!


Signal misspelled in API

Description of the signals shows the proper name for the signal: microtransaction_auth_response

found here: https://gramps.github.io/GodotSteam/signals-user.html

The actual signal method signature is this: ** microstransaction_auth_response**

found here: https://github.com/Gramps/GodotSteam/blob/f8b41173fba8f07ec88bd6b137906cbd77a20666/godotsteam.cpp#L305
Notice the 's'

This is critical in that to make micro-transactions work, the developer needs to hook this API call.
To Reproduce

try to hook the  signal with a callback as described

Expected behavior

The names match and are aligned with the SteamSDK which would be: microtransaction_auth_response

Desktop (please complete the following information):

Both versions

Version of Godot:

v.3.5.1

Version of GodotSteam:

3.4.1 plugin

Thanks for finding this!  I am currently out of town but will be back in action on Sunday.  The plug-in version is still getting updated to match the current master branch so I will add this to the list of changes!

OK, this is now fixed in the module and will be live with 3.18.3; it'll also be fixed in the plug-in which will come out around the same time this week.  Thank you again!


Add GitHub Topics to increase visibility

https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics
https://github.com/topics

Good improvement. Thanks a lot 👍


Glimpse Icon Not Rendered for any path except "/"

When I navigate to any page other than my home page, the script tags are rendered, but there is no icon shown.
I haven't looked into this yet, because this is my first few minutes of messing with glimpse.

I have forked, and will look into this when I get home, unless someone more familiar with Glimpse can speak to the issue.

@otac0n: What would really help is whether you are getting any script errors or if the script tags are even being rendered?

I mentioned in the issue that the script tags are indeed being rendered.  When I inspect the HTML with Firebug, it shows that the script's contents are as expected.
However, Firebug does not show the data.js in the list of Scripts.

Sorry @otac0n, your last comment left me confused.
You are getting the two Glimpse tag's properly rendered in the HTML (client and data) or just client?

Both of the script tags are being rendered properly.
However, the data.js does not seem to be executing as JavaScript.


Why not use :extra for uncaught exceptions?

Rollbar allows to report message, exception object, extra hash or any combination of them.
But default middleware for Rails wants report only message.
Is there any reason why nobody extended ExceptionReporter with simething like
....
exception_message = exception.respond_to?(:message) ? exception.message : 'No Exception Message'
...
exception_extra = exception.respond_to?(:extra) ? exception.extra : nil
exception_data = Rollbar.log(Rollbar.configuration.uncaught_exception_level, exception, exception_extra, :use_exception_level_filters => true)

@sogoodday we don't plan to support that, since Exception doesn't have a #extra method by default and all of this looks too custom.
But if you want to send custom data on a certain request you can use Rollbar.scope!(extra_data) on any point during your request. Would this work for you?

@jondeandres , ou, sorry. I see a good method Rollbar.scoped :)

Yes, you can wrap some code with Rollbar.scoped(data) do or you can mutate the scope with Rollbar.scope!(data). In the middleware we reset always the scope so it's clean for the next request


[Feature request] Add support for indic-whisper models

Please convert and quantize the 12 indic-whisper (medium) models available at https://github.com/AI4Bharat/vistaar#download-models
for use in transformers.js. I was able to convert, quantize and make inference using these models using the https://github.com/OpenNMT/CTranslate2 library and got proper results. But in case of transformers.js, the conversion script did not work out of the box. After a lot of hit-and-trial changes in the script, I was able to generate the quantized onnx model, but I guess I made some changes without understanding and as a result while inferencing, these models do not load even. So, requesting you to convert and quantize these models because for Indian languages these have much lower Word Error Rate than similar other models.

But in case of transformers.js, the conversion script did not work out of the box.

Could you share what problems you ran into?

No, the models are not on HF hub.
I am now performing inference on those models using the ctranslate library and I do not remember now the exact error message.
Since this is no longer an issue for me, I am closing the issue.

Opening the issue again because I guess I will need to use transformer.js I have uploaded one of the models at https://huggingface.co/bh4/whisper-ben but while running inference I get the error -
node index.mjs file:///root/trjs/test/node_modules/@xenova/transformers/src/models.js:3630
           throw Error(Unsupported model type: ${config.model_type})                 ^
 Error: Unsupported model type: whisper
   at AutoModelForCTC.from_pretrained (file:///root/trjs/test/node_modules/@xenova/transformers/src/models.js:3630:19)    at async file:///root/trjs/test/node_modules/@xenova/transformers/src/pipelines.js:2176:33
 Node.js v18.13.0

Hi there - can you please share some more information about your environment? (OS, build tools, transformers.js version, etc.)?

Using our conversion script, with these versions, I was able to export the model you linked without any major errors.
I have uploaded the checkpoints here.
You can run the model with the following code:
import { pipeline } from '@xenova/transformers';

let url = 'https://huggingface.co/datasets/Xenova/transformers.js-docs/resolve/main/bengali-audio.wav';
let transcriber = await pipeline('automatic-speech-recognition', 'Xenova/whisper-ben');
let output = await transcriber(url);
// { text: 'বাংলা নিউজের আয়োজন এই মূহূর্তবিশ্বের কোটি কোটি পাঠক দেখছে' }

Note that this uses the quantized version of the model by default. If you want to get the exact same output as the python version, you can use the unquantized version by specifying { quantized: false } in the pipeline function:
import { pipeline } from '@xenova/transformers';

let url = 'https://huggingface.co/datasets/Xenova/transformers.js-docs/resolve/main/bengali-audio.wav';
let transcriber = await pipeline('automatic-speech-recognition', 'Xenova/whisper-ben', { quantized: false });
let output = await transcriber(url);
// { text: 'বাংলানিউজের আয়োজন এই মুহূর্তে বিশ্বের কোটি কোটি পাঠক দেখছে' }

Closing the issue, but feel free to ask any questions you may have.


Update ro.json

Made some small corrections plus translated and completed what's new in version 4.0.46

The changes in this PR already seem to be updated on master, should we fix the conflicts in this one and merge it or just reject it?


MAINT: Bump production committish.

@jmccorriston are your changes ready for prod?

talked to Jamie on slack.


[bug]: Improve Form Validation

Describe the bug
If the form is incorrect, you can call a function to handle the error and provide feedback to the user.
To Reproduce
No response
Expected Behavior
No response
Screenshot/ Video
No response
Additional context
No response

Great start  working on this.


Log details - Offline Status

HA-ecowater-softener component version: 1.0.1
HA version: 2021.9.5-ls36
I realize this project has not yet been released, but I noticed a potential issue and would like to assist with determining if the cause is code-related or a server-side problem.  The logs available in HA are not detailed enough to point to a culprit.
I've only had this installed for the past few days. It worked very well upon the first installation attempt. However, the past two days have reported the device unavailable on two lengthy occasions. It has occurred this morning at 2:21am PT, and yesterday morning around 4:30am PT.  The device appears and remains unavailable for 20+ hours before returning back to Available status on its own.

Troubleshooting attempted during unavailable status:

EcoWater device itself reports as online
Website login via web browser succeeds, showing device as online and reporting data
EcoWater mobile app succeeds, showing device as online and reporting data
Python project barleybobs/ecowater-softener queries succeed and return valid data
Reloading this custom component homeassistant-ecowater-softener does not resolve the issue
Rebooting HA does not resolve the issue (multiple attempts)

HA Logs:     [serial number intentionally masked]
"Log Details (WARNING)"
`Logger: homeassistant.helpers.entity
Source: helpers/entity.py:644
First occurred: September 10, 2021, 8:50:58 PM (27 occurrences)
Last logged: 2:20:58 PM
Update of sensor.ecowater_ac000w003xxxxxx is taking over 10 seconds`

also appearing in the logs:
"Log Details (ERROR)"
`This error originated from a custom integration.
Logger: custom_components.ecowater_softener.sensor
Source: custom_components/ecowater_softener/sensor.py:115
Integration: Ecowater Softener (documentation, issues)
First occurred: September 10, 2021, 7:20:48 PM (35 occurrences)
Last logged: 2:21:00 PM
Error: time data '01/31/2022' does not match format '%d/%m/%Y'
Traceback (most recent call last):
File "/config/custom_components/ecowater_softener/sensor.py", line 115, in async_update
self._attrs[ATTR_OUT_OF_SALT_ON] = datetime.strptime(data_json['out_of_salt'], '%d/%m/%Y').strftime('%Y-%m-%d')
File "/usr/lib/python3.8/_strptime.py", line 568, in _strptime_datetime
tt, fraction, gmtoff_fraction = _strptime(data_string, format)
File "/usr/lib/python3.8/_strptime.py", line 349, in _strptime
raise ValueError("time data %r does not match format %r" %
ValueError: time data '01/31/2022' does not match format '%d/%m/%Y'
`

Is it possible to enable additional log details to help determine whether the trouble resides with server replies, component code, or perhaps unique to my HA instance itself?  I do hope this information is valuable and look forward to assist with testing.

@mblauser I realize this project has not yet been released, but I noticed a potential issue and would like to assist with determining if the cause is code-related or a server-side problem.

Thanks for bringing this to my attention!

HA Logs: [serial number intentionally masked]
"Log Details (WARNING)"
`Logger: homeassistant.helpers.entity
Source: helpers/entity.py:644
First occurred: September 10, 2021, 8:50:58 PM (27 occurrences)
Last logged: 2:20:58 PM

Update of sensor.ecowater_ac000w003xxxxxx is taking over 10 seconds`

This should just be a warning and can be ignored. It is because it takes over 10 seconds to get the data from the ecowater servers.

"Log Details (ERROR)"
`This error originated from a custom integration.

Logger: custom_components.ecowater_softener.sensor
Source: custom_components/ecowater_softener/sensor.py:115
Integration: Ecowater Softener (documentation, issues)
First occurred: September 10, 2021, 7:20:48 PM (35 occurrences)
Last logged: 2:21:00 PM

Error: time data '01/31/2022' does not match format '%d/%m/%Y'
Traceback (most recent call last):
File "/config/custom_components/ecowater_softener/sensor.py", line 115, in async_update
self._attrs[ATTR_OUT_OF_SALT_ON] = datetime.strptime(data_json['out_of_salt'], '%d/%m/%Y').strftime('%Y-%m-%d')
File "/usr/lib/python3.8/_strptime.py", line 568, in _strptime_datetime
tt, fraction, gmtoff_fraction = _strptime(data_string, format)
File "/usr/lib/python3.8/_strptime.py", line 349, in _strptime
raise ValueError("time data %r does not match format %r" %
ValueError: time data '01/31/2022' does not match format '%d/%m/%Y'

This seems to be where the problem is. It appears that your ecowater device is returning a MDY date but the code expects a DMY date. To fix this during setup I have added a dropdown to pick the correct date format.
This is on the dev branch. If you could delete the integration from the integration tab. Then delete the ecowater_softener from your custom_components folder and then download the dev branch to test if that fixes the problem that would be appreciated!
Thanks 👍

This is on the dev branch. If you could delete the integration from the integration tab. Then delete the ecowater_softener from your custom_components folder and then download the dev branch to test if that fixes the problem that would be appreciated!

I performed these steps while the integration was reporting as 'unavailable'.  Upon adding the integration with updated dev code, it immediately began reporting as 'online' and has been so for the past 23 hours.  Thank you!  I'll certainly report back if the status changes.

Future enhancement consideration:  It may be able to automatically select the user's date format with additional logic by comparing the result of a today() function with the value reported by the Ecowater server.  It might then be possible to distinguish 09/10/2021 from 10/09/2021 based on today() during setup, and automatically set MM/DD or DD/MM accordingly.  Very low-priority enhancement but worth considering.

@mblauser Future enhancement consideration: It may be able to automatically select the user's date format with additional logic by comparing the result of a today() function with the value reported by the Ecowater server. It might then be possible to distinguish 09/10/2021 from 10/09/2021 based on today() during setup, and automatically set MM/DD or DD/MM accordingly. Very low-priority enhancement but worth considering.

I had considered this but it has problems when it is for example 01/01/2021 or 08/08/2021.
I'll close this issue in that case. Thanks for pointing this bug out!
If it goes offline again for a similar reason do not hesitate to comment on this issue and I can reopen it. Otherwise, create a new issue.
I will move the dev branch to the main in a day or two if no further problems are reported.
Thanks 👍

@mblauser This has now been added to the main branch.
Thanks for finding this issue and reporting it 👍


REST APL and generic register handler

add new SALEOR CLOUD APL
use generic register handler
use request validation for restricted access handlers (and removed duplicated JWT verification code)
drop deprecated VercelAPL

#666 FINALLY

Hey @saleor/storefront-checkout please take a look - we should merge this, because its already a long living branch and we will have problem to maintain it

I'll review it today @lkostrowski

@mmiszy

added requested changes
resolved conflicts
the build step fails because of the misconfiguration of APL. Could you set up the keys I generated last week?

Pushed update with the newest version of the SDK. No code changes were needed.

@mmiszy

rebased with the canary branch
CheckoutVercelAPL is back and updated
found a bunch of no longer-used code and dropped it


Have Hugo generate the import statements of the search scripts

Currently the script holds the following:
import algoliasearch from 'algoliasearch/lite';
import { instantMeiliSearch } from "@meilisearch/instant-meilisearch";
import instantsearch from 'instantsearch.js';
import { history as historyRouter } from 'instantsearch.js/es/lib/routers';
import { simple as simpleMapping } from 'instantsearch.js/es/lib/stateMappings';
import * as instantWidgets from 'instantsearch.js/es/widgets';
import { tnd_config } from '@params'

Note that we import both algoliasearch/lite and @meilisearch/instant-meilisearch as well as all widgets from instantWidgets.
This was my bad for misunderstanding the limitation of tree shaking to import/export statements. In order to treeshake the script, we need to limit the import statements to what we need depending on the script configuration (meili or algolia, list of used widgets etc...)
To achieve this, we'll need Hugo to create the list of import statements and prepend the main search script with them. This way, js.Build will effectively treeshake the resulting scripts (import statements + script)

@budparr 🎉
So for tnd.dev, using Algolia we're at 221ko (used to be 225ko), using MeiliSearch we're at 247ko, I'll put those extra 20~ko of weight on MeiliSearch instant search wrapper being heavier than Algolia's


tile_animation_sync option

this adds a sync option that is on by default just above separation
if turned off all animations of that type will start at random frame instead of 0
to address my recent issue and proposal
https://github.com/godotengine/godot-proposals/issues/6856
https://github.com/godotengine/godot/issues/57677
thanks.

Thanks for opening a pull request!
 This way, people reading the Git log can easily figure out what's going on :slightly_smiling_face:

Superseded by https://github.com/godotengine/godot/pull/77257.


make kyma-system visible on dev, it is hidden by default

Move hidden namespaces to kyma-dashboard
Make kube-public hidden by default
Make kyma-system visible on dev

Remove those namespaces from the list of hidden namespaces:

compass-system
knative-eventing
knative-serving
kyma-backup
kyma-installer
kyma-integration
natss
kube-node-lease
serverless-system


minor fix for aishell recipe

just remove unnecessary 'torch.sum'
update result with more epoch

Thanks!


A few fixes

Added grrseguin's fix from issue #38
Fixed failing to unstick when media query no longer matches
Optimized _getTopOffset by providing alternative use of getBoundingClientRec

Thanks @collectivecognition ! :+1:


Correct typo in SSD documentation

Reference issue
Fixes #12807.
What does this implement/fix?

Correct typo in SSD documentation
minor language corrections

Additional information
I have been asked by @larsoner to submit this PR.

Hey, I amended the former commit, adding the requested files and lines.
Not sure whether amendments are your usual way to update PRs.

Comments addressed and failures are unrelated (#12928), so I'll merge. Thanks @SHEscher !

Comments addressed and failures are unrelated (#12928), so I'll merge. Thanks @SHEscher !

Thank you guys for your great work with the package!


Added add-task, notes, task, and video-recording icons

Description
Adds Aleksey's request icons (#160 & #161). Also fixes a couple icons from not being in alphabetical order.
The icon names are:

Add Task
Notes
Task
Video Recording

Pull Request Checklist

[X] Ask the contributors if a similar effort is already in process or has been solved.
[X] Review the contribution guidelines.
[X] Use staging as your pull request's base branch. (All PRs using production as its base branch will be declined).
[X] Ensure all gulp scripts successfully compile.
[X] Update, remove, or extend all affected documentation.
[X] Provide a description what is being changed, extended, or removed.
[X] Link to any issue(s) this request is resolving.
[X] Ensure no private Dialpad links or info are in the code or pull request description (Dialtone is a public repo!).
[X] Request a review from Drew Chandler, Joshua Hynes, or Ted Goas.

Obligatory GIF

@tedgoas-dialpad I'm adding you to this in the event you have a couple minutes to review and approve. I'm hoping to get a new version out today to unblock Brian Sinclair's team.


[Docs] Document how to generate spreadsheet credentials for Meshery

Current State
Currently, there is no documentation or clear instruction on how to generate the required spreadsheet credentials for the --spreadsheet-cred flag when using the mesheryctl registry generate command
Desired State

Contributor Guides and Handbook

📚 Instructions for contributing to documentation

Meshery documentation site and source

🛠 Meshery Build & Release Strategy
🎨 Wireframes and designs for Meshery UI in Figma (open invite)
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

Quick notes:

Make a copy of the Meshery Integration spreadsheet.
Create a GCP API token for interacting with your spreadsheet clone.
base64 encode your GCP API token as you provide it to the mesheryctl generate command.
example:

$ export CRED=`cat ~/spreadsheet.json | base64`
$ cat ~/spreadsheet.json | xargs ./mesheryctl registry generate --spreadsheet-id "1DZHnzxYWOlJ69Oguz4LkRVTFM79kC2tuvdwizOJmeMw" --spreadsheet-cred

Ideally, we build support for CSV files, too.

It seems that I'm unable to make a copy of the integration spreadsheet because the export options are disabled for the document.

Please assign this docs feature to me.


Removing stack.yaml ?

Is it ok if I rename stack.yaml into stack-template.yaml  or something like that ?
The reason for this change is the fact that the file is often out-of-dated and conflicts with my nix setting.

Another better name would be stack-8.0.yaml

Well with the hope that stackage does not require such a file ...

stack-8.0.yaml is good to me. Stackage doesn't require the file to be present.


Add a way for 3rd party to intercept method param injection

From https://github.com/jmockit/jmockit1/issues/337
It should work with and without dataprovider.
@rliesenfeld Any wishes on a future provided API?
@nitinverma is open to participate to the integration as he already made good job on param injection.

I think the brand new JUnit 5 extension model can be a good source of inspiration. The only thing missing in JUnit 5 is a way for a 3rd-party library to automatically register those extensions, without users having to manually add "@ExtendWith" annotations to their test classes.
TestNG already has a set of extension interfaces (IExecutionListener, for example, which JMockit implements), but none similar to JUnit's ParameterResolver interface. I imagine something like this could be added.

I would like to propose we should think not just about method argument injection but other augmentations/extensions that may be possible to a testing framework.
Following is a preliminary idea on generically supporting/exposing integrations:

Feature integrations can be introduced.

Feature integrations can be deprecated.

Feature integrations can be retracted.

Feature integrations may have prerequisites.

Feature integrations prerequisites may be versions.

Feature integrations prerequisites may be another integrations.

One product may expose multiple feature integrations.

Product integration is not directly dependent of other product integrations but via feature integrations.

User should have easy access to the list of active integrations.

Metaphor:
TestNG is a mothership and other products are pods. Pods dock in the mothership and offer bunch of features. Features get coupled or coupling waits of another features (via same pod or another) or rejected as is retracted. Once the couplings are in place mothership can engage or disengage to carryout proper functioning and course correction.
Above is just a rough outline I hope gets enriched via discussion.

I like the vision but it can be done by steps and method argument injection is the perfect candidate for the first step.
And currently, listeners are a good way for 3rd party extensions.


Laptop sized VLAB demo

Create a section inside of the VLAB area of docs to guide a user with laptop level resources through setting up a smaller fabric.

Working on some changes to CLI and defaults to allow for more flexibility


Counting Levels doesn't work on Mountain Stage

I think the "world" page is showing fully released and the "region" page is showing full & adventurer.

I haven't finished any subscriber levels, those should be counted.  If we're following the same pattern as previous levels @Vlevo

Yes, no subscriber levels in yours would make the 5/5 make sense (mine is 8/8) I can make sense of those numbers (if you did it, it must exist). I think there is another problem here as well.
'cause mine should be 9/9 and 9/10 but it is 8/8 and 9/10. I can understand the 10 (future level started but not submitted, I guess I'll go submit and see what happens) but why have I completed 9 but only show 8. Seems like one of the adventurer levels from last week isn't getting counted... Is there one you haven't done?

Also, (unfortunately I don't have an image) I was getting 3/3 and 4/4 as I was completing levels.  I don't think it's just not counting subscriber levels.

Try doing a localStorage.clear() and seeing if the count updates.


[TKMDPA-608][JS] Removes Google API key instead sets origin Api Key f…

…or Google service

Rename apiKey into googleApiKey


Discovery doesn't work

Environment:
MicroXRCEAgent: Raspberry Pi 4, Ubuntu 20.10
MicroXRCEClient: Discovery example on laptop, Ubuntu 20.04
Connection: Home wifi, the 2 devices could ping each other normally.
Issue: The discovery code built couldn't discover the Agent running on Raspberry Pi, the Discovery runs for some seconds without giving any outputs. The Agent side shows no connection established.
As far as I understand, the on_agent_found callback should be invoked and show the found agent and port. However, it doesn't seem to work. Please correct me if the understanding is wrong, thank you.

How are you launching the Micro XRCE-DDS Agent? Could you share the command?

I launched it with the command:
./MicroXRCEAgent
then
udp4 --port 2020
The other clients on ESP8266 could connect to that Agent using fixed IP and port.

To enable discovery you should use ./MicroXRCEAgent upd4 --port 2020 -d

Thank you for the support, the client discovered the agent.


Can not  back to the first page

I have four pages, index.html, test01.html, test02.html, test03.html.
Each page has the code like this

                navigate_before

            test01

but when I reached test03.html, and then click the back button, it can back to the test02.html,
and then click the back button in test02.html, it can not back to the test01.html
I don't know how can I implement it, please help
ps: sorry for my English, wish you can understand what I mean :-)

Does it go anywhere?

@ZanderBrown NO, nothing happened :(

try using the demo
something must be wrong

Are there any errors in js console?
If you can post a fiddle or codepen example it would be easier to help you and debug this:

http://www.jsfiddle.net
http://www.codepen.io

@AlwaysBee can you put your project in a repository ?
Are you running this on http server like apache?
You need to understand the navagation history is the base to use the back link. So if you came from another page, this page will be the back page, so in this case i suggest you organize your project and review your HTML and links to be sure, if all are in the right place.

Could you please expand you point?
Consider pointing code snippets here, on Codepen or on JSFiddle.
Make sure you have read the documentation correctly and followed any instructions it may give.

There hasn't been a response by the issues owner in 20 days.
This issue will be closed in 7 days if no further response is submitted


RecurrenceRule.setByDayPart doesn't remove BYDAY part when given an empty list

Calling RecurrenceRule#setByDayPart with an empty list seems to include that empty list in the parts map — I believe it's due to a missing else or return in the method:
https://github.com/dmfs/lib-recur/blob/d59e8668c0e4ffa9b1bc207e16f9a41984ef302d/src/main/java/org/dmfs/rfc5545/recur/RecurrenceRule.java#L1957-L1965
This makes the resulting rule have an empty BYDAY-value, e.g. "FREQ=MONTHLY;BYMONTHDAY=31;BYDAY=", eventually leading to an "too many empty recurrence sets" exception when expanding the rule.

Admittedly, the setters never were a real use case for me so far, that's probably why they are so poorly tested. Thanks for reporting and fixing this. I hope there are no other bad surprises there.


🌌 Make the Universe Strict

This PR does away with ElIn and ElOut, and makes ElStable code definitionally equal to unfold_el code, and closes #189.
I initially tried removing ElStable entirely, but found that this solution was the simplest, as there are several places where we rely on something being a code.
The main complication this introduces is that pattern matching on a type requires also matching on its code, because they're now equal. The only place we don't have to do this is when matching on the goal in a tactic, because we have still have intro_implicit_connectives and elim_implicit_connectives, which now unfold an ElStable but do not add ElIn or ElOut. Perhaps ElStable should no longer be an "implicit connective" and we should instead be pattern matching on codes in tactics as a matter of consistency?
Having multiple representations of definitionally equal types in the core theory initially felt awkward to me, but @TOTBWF pointed out to me that this is sort of like an eta law for the universe. The main difference is that we're not usually pattern matching on "a variable at function type or a lambda" but we match on types pretty regularly.
This is a non-trivial change to cooltt, so please let me know if this implementation is a Bad Idea and needs to be reworked.

Thanks for this work, and I'm very sorry that your code has not received an official review after all this time!
I am thinking about the definitional equality issue you mentioned... Let me ponder it a little bit.

My concern about making ElStable definitionally equal to its unfolding is exactly the thing you point out --- in parts of the implementation, we rely on something being a code. Unfortunately, it is not reasonable for these parts of the code to not be stable under definitional equivalence. To put it another way, an important invariant of an implementation of type theory is that if you replace equals by equals, things continue to work --- but this change will violate that.
Thus I think that something a bit more elaborate will be required in order to maintain the necessary invariants.

Let me continue reviewing this actually, I misunderstood some of it.

Closing, as we have discussed some new design.


fix javascript error in iconpicker

fix #826

@LukeTowers
I killed my dev and my fork :( , so I had to fork again and send an new pull request with your suggestions and with the compiled javascript


Add timeouts to the pushover, hipchat, slack handlers

I'm not sure about the release/review cycle here, but if any of the maintainers got some pointers I'm happy to hear about it :D

ping @symfony/monologbundle
who can we ask for help/directions to move this PR forward?
thanks !

e

Thank you @SpacePossum.


Updates Deps

excludes lodash, bootstrap-switch and the latest mock (outstanding pr address that)
holding off on post-css loader till this is resolved: postcss/postcss-loader#209
ui-router from .4.x.x to 1.x.x breaks $statechange, adding stopgap shim. eventually we'll have to use migration guide to get rid of $statechange instances
https://ui-router.github.io/guide/ng1/migrate-to-1_0

just dependancies, no review really needed.  Merging.

@AllenBW can you please post a SS to ensure that all is working.


shaka did not correctly calculate first index of chunk to fetch.

Have you read the FAQ and checked for duplicate issues:
yes.
What version of Shaka Player are you using:
check 2.3.1 | 2.2.9 | master.
Can you reproduce the issue with our latest release version:
yes.
Can you reproduce the issue with the latest code from master:
yes.
Are you using the demo app or your own custom app:
both.
If custom app, can you reproduce the issue using our demo app:
yes.
What browser and OS are you using:
chrome(63.0.3239.132) | macOS High Sierra(10.13.2)
What are the manifest and license server URIs:
(you can send the URIs to<EMAIL_ADDRESS>instead, but please use GitHub and the template for the rest)
manifest.txt
What did you do?
try to play live content
What did you expect to happen?
expect live playback starting
What actually happened?
actually shaka did not correctly calculate first index of chunk to fetch.
Correct first index for this manifest is 520617
but got 8979424

i did not dig deeper but i suppose problems in calculation position/startNumber which are passed to getUris func in SegmentReference
https://github.com/google/shaka-player/blob/master/lib/dash/segment_template.js#L347-L352

@DenisDashkevich #1232 has been fixed, can you please retest?
https://nightly-dot-shaka-player-demo.appspot.com/demo/

Hi, it works pretty well. thanks!
2018-02-01 21:26 GMT+03:00 Jacob Trimble<EMAIL_ADDRESS>
@DenisDashkevich https://github.com/denisdashkevich #1232
https://github.com/google/shaka-player/issues/1232 has been fixed, can
you please retest?
https://nightly-dot-shaka-player-demo.appspot.com/demo/
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/google/shaka-player/issues/1245#issuecomment-362357418,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARY5fdv_YSfVgr8D-QVzYOGxH64xQnzBks5tQgHKgaJpZM4RrSIF
.


MB-8224: Copy changes for Select Shipment Type screen

Description
Design requested copy and minor design changes to the SelectShipmentType component. This pull request implements those changes.
This pull request also adds several stories for this component to Storybook, roughly mapping to the states that this component can be in. (Customer Components / Pages / Select Shipment Type)
Reviewer Notes
The copy changes are pretty minimal, but definitely check for typos from transliteration. Ensure there are no other major states that this component can be in which should be covered by a story.
Setup
Check it out in storybook. If you want to view the base component in storybook (before any of the copy or design changes were made), you can jump to the first commit in this branch:
git checkout d5cc1a5
yarn storybook

To view this in the application proper,
make server_run
make client_run

Code Review Verification Steps

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] User facing changes have been reviewed by design.
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Closes MB-8224.


init commands returns weird error about fetching a file from github

I was expecting this to work, but it fails:
/tmp ➜  timoni version
api: timoni.sh/v1alpha1
client: 0.17.0
cue: 0.6.0
/tmp ➜  timoni mod init myapp .
4:12PM ERR pulling artifact manifest failed: GET https://ghcr.io/token?scope=repository%3Astefanprodan%2Ftimoni%2Fminimal%3Apull&service=ghcr.io: DENIED: denied

Your GHCR token has expired. Update it or run docker logout ghcr.io

Thanks, that was it, but I didn't get it from the original error message. Maybe there's a way to make it a bit more verbose?


contentURL added in CA query

Hello @aggelosgkiokas! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file trompace/queries/controlaction.py:

Line 19:23: W291 trailing whitespace
Line 35:33: W291 trailing whitespace
Line 37:1: W293 blank line contains whitespace


[Feature] Support nested property access for encode

What problem does this feature solve?
e.g. consider this option:
{
  dataset: [{
    id: "42",
    source: [{
      x: 42,
      y: {
        type: "range",
        resolvedMin: { value: 20, inclusive: true },
        resolvedMax: { value: 24, inclusive: true },
      }
    }]
  }],
  series: [{
    type: 'line',
    datasetId: '42',
    encode: {
      x: 'x',
      y: 'y.resolvedMin.value'
    }
  }]
}

What does the proposed API look like?
I'd like to be able to use y.resolvedMin.value as a path in a JS object such as in lodash's get: https://lodash.com/docs/4.17.15#get

We don't have a recent plan to support this but a pull request is welcomed. Extra library should not be imported.


Update scalatest to 3.2.5

Updates org.scalatest:scalatest from 3.2.4 to 3.2.5.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalatest", artifactId = "scalatest" } ]

labels: library-update, semver-patch

Codecov Report

Merging #928 (68d93e9) into develop (b1c7967) will decrease coverage by 0.03%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop     #928      +/-   ##
===========================================
- Coverage    89.66%   89.63%   -0.04%
===========================================
  Files          119      119
  Lines         9869     9869
  Branches       494      494
===========================================
- Hits          8849     8846       -3
- Misses        1020     1023       +3

Impacted Files
Coverage Δ

...in/scala/com/twitter/algebird/scalacheck/Gen.scala
90.90% <0.00%> (-9.10%)
:arrow_down:

...main/scala/com/twitter/algebird/monad/Reader.scala
52.94% <0.00%> (-5.89%)
:arrow_down:

.../main/scala/com/twitter/algebird/JavaMonoids.scala
77.96% <0.00%> (-1.70%)
:arrow_down:

...a/com/twitter/algebird/immutable/BloomFilter.scala
95.08% <0.00%> (-0.82%)
:arrow_down:

.../scala/com/twitter/algebird/immutable/BitSet.scala
96.78% <0.00%> (ø)

.../main/scala/com/twitter/algebird/BloomFilter.scala
94.69% <0.00%> (+0.44%)
:arrow_up:

...src/main/scala/com/twitter/algebird/Interval.scala
80.00% <0.00%> (+0.86%)
: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 b1c7967...68d93e9. Read the comment docs.


Dependency: Upgrade reason-harfbuzz

This prunes the link flags brought in by reason-harfbuzz, and fixes a bug where images wouldn't load on linux builds.

Fixed in #758


[HUDI-764] [HUDI-765] ORC reader and writer implementation

What is the purpose of the pull request
This pull request supports ORC storage in hudi.
Brief change log
In two separate commits:

Implemented HoodieOrcWriter

Added HoodieOrcConfigs
Added AvroOrcUtils that writes Avro record to VectorizedRowBatch
Used orc-core:no-hive module (no-hive is needed because spark-sql uses no-hive version of orc and it would become easier for spark integration)

Implemented HoodieOrcReader

Read Avro records from VectorizedRowBatch
Implemented OrcReaderIterator
Implemented ORC utility functions

Verify this pull request

Added unit tests for

reader/writer creation
AvroOrcUtils

(local) Wrote a small tool that reads from ORC/Parquet files and writes to ORC/Parquet files, verified that the records in the input/output files are identical using spark.read.orc/spark.read.parquet.
(local) Changed the HoodieTableConfig.DEFAULT_BASE_FILE_FORMAT  to force the tests to run with ORC as the base format. Some changes need to be made, but I'm leaving it out of this PR to get some initial feedback on the reader/writer implementation first.
For all tests to pass with ORC as the base file format:

Understand schema evolution in ORC (ref TestUpdateSchemaEvolution)
Add ORC support for places that have hardcoded ParquetReader or sqlContext.read().parquet()
Add ORC support for bootstrap op
Hive engine integration with ORC (implement HoodieOrcInputFormat, and more)
Spark engine integration with ORC (implement HoodieInternalRowOrcWriter, and more)
Add ORC support for HoodieSnapshotExporter
Implement HDFSOrcImporter
and possibly more.

Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

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

@prashantwason Can you review this ?

How can I trigger a rebuild?

option 1: close and reopen the PR;
option 2: push an empty commit via git command

@leesf

would not sync hudi orc format table to hive metastore yet?

ORC is well-integrated with hive, so hive already has OrcInputFormat, OrcOutputFormat etc. With my latest change to the HoodieInputFormatUtils class, I was able to sync hudi orc format table to hive metastore (tested with deltastreamer).
However, we do still need to implement HoodieOrcInputFormat & HoodieRealtimeOrcInputFormat. I have done some work on that but it's not tested yet.

Codecov Report

Merging #2793 (619d75b) into master (6786581) will decrease coverage by 1.09%.
The diff coverage is 8.72%.

@@             Coverage Diff              @@
##             master    #2793      +/-   ##
============================================
- Coverage     52.54%   51.45%   -1.10%
+ Complexity     3707     3101     -606
============================================
  Files           485      393      -92
  Lines         23171    18584    -4587
  Branches       2459     1911     -548
============================================
- Hits          12176     9562    -2614
+ Misses         9923     8222    -1701
+ Partials       1072      800     -272

Flag
Coverage Δ
Complexity Δ

hudicli
40.29% <ø> (ø)
0.00 <ø> (ø)

hudiclient
∅ <ø> (∅)
0.00 <ø> (ø)

hudicommon
48.61% <8.72%> (-2.07%)
0.00 <21.00> (ø)

hudiflink
56.54% <ø> (-0.04%)
0.00 <ø> (ø)

hudihadoopmr
?
?

hudisparkdatasource
?
?

hudisync
?
?

huditimelineservice
?
?

hudiutilities
69.74% <ø> (+0.01%)
0.00 <ø> (ø)

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

Impacted Files
Coverage Δ
Complexity Δ

...org/apache/hudi/common/util/OrcReaderIterator.java
0.00% <0.00%> (ø)
0.00 <0.00> (?)

...ain/java/org/apache/hudi/common/util/OrcUtils.java
0.00% <0.00%> (ø)
0.00 <0.00> (?)

...java/org/apache/hudi/common/util/AvroOrcUtils.java
9.11% <9.11%> (ø)
19.00 <19.00> (?)

...va/org/apache/hudi/io/storage/HoodieOrcReader.java
25.00% <25.00%> (ø)
1.00 <1.00> (?)

...org/apache/hudi/common/model/HoodieFileFormat.java
100.00% <100.00%> (ø)
3.00 <0.00> (ø)

...pache/hudi/io/storage/HoodieFileReaderFactory.java
61.53% <100.00%> (+11.53%)
5.00 <1.00> (+2.00)

.../apache/hudi/sink/partitioner/BucketAssigners.java
33.33% <0.00%> (-16.67%)
2.00% <0.00%> (ø%)

.../java/org/apache/hudi/common/util/CommitUtils.java
40.47% <0.00%> (-3.12%)
6.00% <0.00%> (ø%)

...java/org/apache/hudi/sink/StreamWriteFunction.java
77.77% <0.00%> (-2.74%)
22.00% <0.00%> (ø%)

...g/apache/hudi/common/model/WriteOperationType.java
50.00% <0.00%> (-1.43%)
2.00% <0.00%> (ø%)

... and 112 more

Codecov Report

Merging #2793 (e787d8e) into master (6786581) will decrease coverage by 43.17%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master   #2793       +/-   ##
============================================
- Coverage     52.54%   9.36%   -43.18%
+ Complexity     3707      48     -3659
============================================
  Files           485      54      -431
  Lines         23171    1996    -21175
  Branches       2459     236     -2223
============================================
- Hits          12176     187    -11989
+ Misses         9923    1796     -8127
+ Partials       1072      13     -1059

Flag
Coverage Δ
Complexity Δ

hudicli
?
?

hudiclient
?
?

hudicommon
?
?

hudiflink
?
?

hudihadoopmr
?
?

hudisparkdatasource
?
?

hudisync
?
?

huditimelineservice
?
?

hudiutilities
9.36% <ø> (-60.36%)
48.00 <ø> (-325.00)

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


Implement parquet simple record as a source for the druid spark indexer

Probably can't be merged right away.
Works fine with the parquet file I included (mapped the csv from test resources into a parquet file). The strategy is to directly map to json without going through avro as loading generic data made it more complicated than not for me.
I'm going to run production tests soon (vs a few hundreds of gigs of data).

For future maintainability, there is already a parquet input row parser in druid: https://github.com/druid-io/druid/blob/master/extensions-contrib/parquet-extensions/src/main/java/io/druid/data/input/parquet/ParquetHadoopInputRowParser.java is there any reason that cannot be used?
It would be nice if the row parser (or factory) could be passed in and eliminate the giant switch statement which is not really sustainable.
Also regarding https://github.com/metamx/druid-spark-batch/issues/10 it might make sense to have an RDD passed in the index method in the future, though I don't think such a refactoring would be in scope for a specific new format.
Getting rid of the giant switch statement should be investigated more though.

test failure looks like a guava version problem:
org.apache.spark.SparkException: Job aborted due to stage failure: Task 0 in stage 6.0 failed 1 times, most recent failure: Lost task 0.0 in stage 6.0 (TID 58, localhost, executor driver): java.lang.NoSuchMethodError: com.google.common.io.Files.asByteSource(Ljava/io/File;)Lcom/google/common/io/ByteSource;

Guava version reconciliation is always a huge issue.

Looks like checks have passed.
A few things :

This uses the simplest read api from parquet which I copied over because parquet-tools which this api belongs to imports a very old version of guava
I didn't add push down filters as an option, which can be very effective while doing parquet
I fixed the druid version to 0.10.1 but we can revert that to snapshot
I am unsure how hadoopFileAPI works with Spark/Parquet over a directory, meaning if it splits the ParquetFileReader workload properly or if it's a bottleneck.

how would we specify the nested columns ?
also would it respect partition column ?

The point is that it transforms parquet records to json, so that you can
use the json spec (including flatten).
In 0.10.1 the avro flattening, nesting access isn't available yet afaik
which is why I went with a custom parser that can easily transform to json
without too much overhead.
On Wed, Oct 4, 2017, 1:56 PM Gaurav M Shah<EMAIL_ADDRESS>wrote:

how would we specify the nested columns ?
also would it respect partition column ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/metamx/druid-spark-batch/pull/111#issuecomment-334132076,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAYyhiLZpG5OzSorXW-Yzt0-oDQVkEnIks5so3JkgaJpZM4PsLLC
.

I feel going down dataframe route might be better.
Current way there are two transforms needed, Parquet to Json to Map<string,Object>
With dataframe router we could do Parquet to Map<String,Object>
Would allow us to do other transforms also would make use of parquet pruning features from spark

Sure, why not, let me have a look

Please correct me if I am wrong but I think that the parser need not be "simple" in that the parsing can produce a POJO for our manipulation. Hence, it is up to us to decide what is the record that will be produced and how are we going to map it into druid.

@xanec You're right, I've had other things to patch on our end on Druid, I'm getting back to this as soon as I can to refactor it.

I rebased on 0.11 to use the transform and flatten APIs, but I had to copy maps in the parser because AbstractMaps in the ObjectFlatteners API aren't directly serializable by Kryo.


HashingVectorizer behaves differently from FeatureHasher

Describe the issue:
HashingVectorizer behaves differently from FeatureHasher,  HashingVectorizer can work off a Sting like
JUNK_FOOD_DOCS = (
    "the pizza pizza beer copyright",
    "the pizza burger beer copyright",
    "the the pizza beer beer copyright",
    "the burger beer beer copyright",
    "the coke burger coke copyright",
    "the coke burger burger",
)

but FeatureHasher expects an iterable of strings like:
JUNK_FOOD_DOCS = [["the", "pizza", "pizza", "beer", "copyright"],
   ["the", "coke", "burger", "burger"] ]

Which is the correct behavior:

expect the hasher to parse strings into vectors
fix the test by sending list of lists of strings to FeatureHasher instead list of strings, like the other hasher expects

Minimal Complete Verifiable Example:
See dask-ml/tests/feature_extraction/test_text.py: test_basic()
Anything else we need to know?:
This is illustrated in the failing test
Environment:

Dask version:  dask-ml-3.8 conda env  dask 2023.1.1
Python version: 3.8, 3.9, 3.10
Operating System:  ubuntu-latest
Install method (conda, pip, source): conda

Here is a possible fix to this test if this is the route we wish to go: https://github.com/dask/dask-ml/compare/main...brian-methodical:dask-ml:fix-tests#diff-824171fe718be1c9bd2d722b5ebc30f71b6dd402568282716078a1c5ec25db1f


Potential Database and Schema Updates - Filled filaments, temperature ranges, material field, alloy codes.

In the work to create entries for 3DXTECH filaments i ran across a few bits which could be addressed. I fully understand that making the database too complex is not desirable or actually beneficial to end users.

3DXTECH use temperature ranges for extruder and bed temp. The JSON schema only allows for a single integer. It would be nice to be able to input two values indicating a temperature range recommended by the manufacturer. Alternatively we could have a min and max values for extruder/bed (less preferred I think as that creates two new fields and begs the questions of what to enter when only a single value is given by the manufacturer).

This probably doesn't matter as users set their own print temps through the slicer config and filament calibrations. For 3DXTECH filaments I just averaged the two band values. But this is not exactly correct, so it bothered me a little bit 🥲

I think we need a solution to deal with filled filaments. My initial suggestion is simply an optional "fill" parameter that is "null, glass fiber, carbon fiber". The material name could then be  NAME {color_name} {fill}.  Most of the 3DXTECH entries have fill material and that is important to call out. They way I implemented it feels a bit clunky have it as text "Carbon Fiber" in the name.

Also some guidance on how to deal with the material field text with regards to fill and alloys would be helpful:

For two filaments ABS and Carbon Fiber ABS should they both have material as ABS or should they be ABS and ABS-CF. My suggestion is to use the later as they are two difference materials and conforms to ISO 1043 marking standard.

In general polymer alloys should be designated as PC+ABS and not PC/ABS to conform to ISO 1043 marking standards. So a blend with fill would be PC+ABS-CF or PC+ABS-GF. This gives us a basis of why to do it this way.

I could add new fields called e.g. "extruder_temp_range" and then you can either specify a single value or use this new field to specify a range. That should solve it for all use cases.
Yes, a fill field is a good idea. You can submit a PR to add that to the schema if you want. I dont think you need to add {fill} to the filament name though since that should be evident from the material name, where I agree we should go with as you said e.g. ABS-CF.
I also agree with your blend marking there. Good to keep it consistent.

I've drafted an idea in https://github.com/Donkie/SpoolmanDB/pull/21

I think this is fully implemented now by Stu's PR


Style issue: Language selector expand menu does not display text

Describe the bug

Language selector expand menu does not display text
To Reproduce
Steps to reproduce the behavior:

Open the SplashScreen on PC

Expected behavior

I tried to modify its css to fix this issue

Screenshots
Microsoft Edge (121.0.2277.128):

Firefox (122.0.1):

Details

Platform: Desktop
Platform version: Microsoft Windows 11 Pro 10.0.22631 build 22631
App version: 1.68.0

Additional context

ref: #2952


Server wont start

start.sh: 33: start.sh: Syntax error: "(" unexpected
Im guessing a same and simple issue?

I guess, that you are starting your server from a start.sh file right ?
If so there is a misplaced or unexpected ( in the code of the file.
It may be on line 33 I don't know I'm not some sort of wizard with this stuff
Have you tried running you unturned server via the shortcut method
And are you running the server with like a shutdown script or something along the lines of that?

computerboydude, you seriously? IT IS A LINUX BASH FILE, You can't start the linux server from the shortcut! You must use the RocketLauncher.exe(via Wine + Mono), for this you have the start.sh, that edelin3 maybe wrong edit or this is outdated version, anyway the linux server is having much bugs at this time, becouse i recommend you to setup a VM for this things


webpackMode expected 'lazy', 'eager' or 'weak', but received: lazy-once

lib version:
   "webpack": "^4.29.6",
    "webpack-cli": "^3.3.0"

code:
import (/* webpackChunkName: "asyncA",webpackMode:"lazy-once" */'../common/async1')

error:
`webpackMode` expected 'lazy', 'eager' or 'weak', but received: lazy-once

when i set "lazy-once" for "webpackMode", the error will be reproduced
but I saw in the documentation that it was available
👉https://www.webpackjs.com/api/module-methods/

@light0x00 please use issue template

@light0x00 please use issue template

all right,i'm sorry,i have been relaunched a issue😄


Can You Provide Complete sample program without having confidential data how to use this API

Please

Hello @Sivaramayya ,
You have several examples here.


doc: maintain full documentation of the features in all crates

People have been complaining that finding feature documentation is difficult.
Fixes #46. Hopefully.

People have been complaining that finding feature documentation is difficult.
Fixes #46. Hopefully.

Thank you！


Just a question

Just wanted to know how it's possible to have a window with the blurred transparency in DeskGap. As I understand it, that is not possible with Electron.
Does using the system webView help make that possible?

Hi, actually it is possible in electron.
There is nothing much to do with the webview. Both DeskGap and electron use NSVisualEffectView to achieve this effect.


Limit the maximum number of requests which can issued concurrently to the chain

This PR targets #3341

Controlled via the max_concurrency setting in the chain configuration.

I should probably use a CondVar + Mutex here instead of pulling in resevents. Will get to it later.


Off-by-one error in Back to State parsing

Recent version of TLC improved the format of lasso counter-example.  What used to be a Back to state: N marker for N being the ordinal of the state in the trace, TLC now prints Back to state: <SomeAction ...>:
java -XX:+UseParallelGC -cp /home/markus/.vscode/extensions/alygin.vscode-tlaplus-1.6.0/tools/tla2tools.jar -Dtlc2.TLC.ide=vscode tlc2.TLC MCEWD998.tla -tool -modelcheck -config MCEWD998.cfg -deadlock -noTE

TLC2 Version 2.16 of Day Month 20?? (rev: c465d0d)
Running breadth-first search Model-Checking with fp 116 and seed -8108095979473316199 with 1 worker on 4 cores with 5291MB heap and 64MB offheap memory [pid: 171802] (Linux 5.4.0-74-generic amd64, Ubuntu 11.0.11 x86_64, MSBDiskFPSet, DiskStateQueue).
Starting SANY...
Parsing file /home/markus/src/TLA/ewd998/MCEWD998.tla
Parsing file /home/markus/src/TLA/ewd998/EWD998.tla
Parsing file /tmp/Integers.tla (jar:file:/home/markus/.vscode/extensions/alygin.vscode-tlaplus-1.6.0/tools/tla2tools.jar!/tla2sany/StandardModules/Integers.tla)
Parsing file /tmp/Naturals.tla (jar:file:/home/markus/.vscode/extensions/alygin.vscode-tlaplus-1.6.0/tools/tla2tools.jar!/tla2sany/StandardModules/Naturals.tla)
Parsing file /home/markus/src/TLA/ewd998/AsyncTerminationDetection.tla
Semantic processing of module Naturals
Semantic processing of module Integers
Semantic processing of module AsyncTerminationDetection
Semantic processing of module EWD998
Semantic processing of module MCEWD998
SANY finished.
Starting... (2021-06-16 18:36:48)
Implied-temporal checking--satisfiability problem has 1 branches.
Computing initial states...
Computed 2 initial states...
Computed 4 initial states...
Computed 8 initial states...
Computed 16 initial states...
Computed 32 initial states...
Finished computing initial states: 64 distinct states generated at 2021-06-16 18:36:49.
Checking temporal properties for the current state space with 6144 total distinct states at (2021-06-16 18:36:52)
Temporal properties were violated.
The following behavior constitutes a counter-example:
1: <Initial predicate>
/\ pending = (0 :> 0 @@ 1 :> 0 @@ 2 :> 0)
/\ counter = (0 :> 0 @@ 1 :> 0 @@ 2 :> 0)
/\ token = [q |-> 0, color |-> "black", pos |-> 0]
/\ active = (0 :> TRUE @@ 1 :> FALSE @@ 2 :> FALSE)
/\ color = (0 :> "white" @@ 1 :> "white" @@ 2 :> "white")
2: <InitiateProbe line 93, col 5 to line 100, col 45 of module EWD998>
/\ pending = (0 :> 0 @@ 1 :> 0 @@ 2 :> 0)
/\ counter = (0 :> 0 @@ 1 :> 0 @@ 2 :> 0)
/\ token = [q |-> 0, color |-> "white", pos |-> 2]
/\ active = (0 :> TRUE @@ 1 :> FALSE @@ 2 :> FALSE)
/\ color = (0 :> "white" @@ 1 :> "white" @@ 2 :> "white")
3: <SendMsg line 123, col 5 to line 132, col 41 of module EWD998>
/\ pending = (0 :> 0 @@ 1 :> 1 @@ 2 :> 0)
/\ counter = (0 :> 1 @@ 1 :> 0 @@ 2 :> 0)
/\ token = [q |-> 0, color |-> "white", pos |-> 2]
/\ active = (0 :> TRUE @@ 1 :> FALSE @@ 2 :> FALSE)
/\ color = (0 :> "white" @@ 1 :> "white" @@ 2 :> "white")
4: <PassToken line 104, col 5 to line 113, col 45 of module EWD998>
/\ pending = (0 :> 0 @@ 1 :> 1 @@ 2 :> 0)
/\ counter = (0 :> 1 @@ 1 :> 0 @@ 2 :> 0)
/\ token = [q |-> 0, color |-> "white", pos |-> 1]
/\ active = (0 :> TRUE @@ 1 :> FALSE @@ 2 :> FALSE)
/\ color = (0 :> "white" @@ 1 :> "white" @@ 2 :> "white")
5: <PassToken line 104, col 5 to line 113, col 45 of module EWD998>
/\ pending = (0 :> 0 @@ 1 :> 1 @@ 2 :> 0)
/\ counter = (0 :> 1 @@ 1 :> 0 @@ 2 :> 0)
/\ token = [q |-> 0, color |-> "white", pos |-> 0]
/\ active = (0 :> TRUE @@ 1 :> FALSE @@ 2 :> FALSE)
/\ color = (0 :> "white" @@ 1 :> "white" @@ 2 :> "white")
3: Back to state: <InitiateProbe line 93, col 5 to line 100, col 45 of module EWD998>
Finished checking temporal properties in 00s at 2021-06-16 18:36:52
Progress(10) at 2021-06-16 18:36:52: 34,687 states generated (501,861 s/min), 7,763 distinct states found (112,317 ds/min), 1,619 states left on queue.
34687 states generated, 7763 distinct states found, 1619 states left on queue.
The depth of the complete state graph search is 10.
Finished in 4159ms at (2021-06-16 18:36:52)

@lemmy, I see no difference whith the current implementation. Here's an example from the test suite: error-trace-back-to-state.out. Are you sure this format is new?

The interpretation of https://github.com/alygin/vscode-tlaplus/blob/master/tests/fixtures/parsers/tlc/error-trace-back-to-state.out was wrong; the lasso is closed by state Foo=1 that we reach from state Foo=2 by action <Cycle line 42, col 10 to line 48, col 30 of module back_to_state>.


C035 - Add support for cart PS and infinite scroll; add table view to cart

c035 - add support for PS and infinite scroll to cart; added the table view whilst i was at it.

Clicking on a table row doesn't bring up the metadata modal
Unchecking an obs in the table view doesn't actually seem to do anything
Shift+clicking on a table row doesn't start add range
If you click on the Cart tab while already in the cart view, you get a blank gallery
Now that we have "View Gallery/Table" and then "Select Metadata" in the nav bar, it has a very similar feel to the browse page. Except those items are on the right side of a divider, and the whole section is on the right side of the screen. What do you think about:

A) Swapping the two sides (View Table / Select Metadata / Empty Cart) and (Metadata CSV / Data Archive / URL archive) and/or
B) Swapping the product pane and the gallery pane. If we did this, then switching between browse and cart would seem almost seamless. The nav bar wouldn't change all that much. In fact we could rename Download CSV (all results) to Download CSV (cart) and it would also look almost the same. You could even keep the slider where it is (since we do want a slider in the cart)

There's something really broken with infinite scroll on the normal browse page. As you scroll down it keeps reloading the same page over and over so you get duplicate data, and the slider moves right and then jumps left.
The cart gallery runs off the bottom of the screen, so when it's full the final row of thumbnails is partially obscured.

I had to change document.ready to say:
    opus.namespaceDict = { "search": o_browse, "cart": o_cart, "browse": o_browse };
I'm sure this isn't the right fix, but at least it let me get things going.
When you first switch to the browse page, the slider just spins forever
If you drag the slider on the browse page, it does update and the page fetches, but the size of the slider "button" is wrong - it doesn't expand to support the width of the observation number you've set
When you scroll down in either gallery or table view on the browse page, there is no big spinner while it fetches
When you switch from gallery to table and back on the browse page, the slider moves
The first time you switch to the Cart tab, it says there are no entries in the cart. Then if you switch to it again it displays thumbnails.
Clicking on a table header (browse or cart) jumps you back to the search tab
Infinite scroll on the browse tab is still completely broken - as you scroll down you keep getting copies of the same data
Infinite scroll on the cart gallery doesn't do anything at all

The following bugs from earlier are now FIXED:

Clicking on a table row doesn't bring up the metadata modal
Unchecking an obs in the table view doesn't actually seem to do anything
Shift+clicking on a table row doesn't start add range

mutationObserver.js looks fine. cartObserver will detect changes when we:

Switch from other tabs to cart tab
In gallery, click add/remove icon
In table, click checkbox, remove/add tab in hamburger
Switch between gallery and table
adjustProductInfoHeight is called in cartObserver callback function to update both perfect scrollbar.
The only optimization I can see is to update the callback with: (which I didn't do it in original file)
let lastMutationIdx = mutationsList.length - 1; mutationsList.forEach((mutation, idx) => {   if (idx === lastMutationIdx) {       adjustProductInfoHeight();   } });
But overall it will work fine.


{Packaging} Bump urllib3 and requests

Description
Since setup.py doesn't pin urllib3
https://github.com/Azure/azure-cli/blob/d1585e356d547fe5adcc4c6651096e8884dcb45e/src/azure-cli/setup.py#L146
Component Governance alert is triggered when urllib3 1.26.2 is installed.
The current urllib3 is 1.26.4, so the alert is no longer valid.
For security sake, we should force urllib3 >= 2.26.4.

Packaging


Not able to find AWS Fargate shape which is the most used one among AWS services

Preflight Checklist

[x] I agree to follow the Code of Conduct that this project adheres to.
[x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
draw.io version (In the Help->About menu of the draw.io editor):

draw.io version [e.g. 12.6.7]

Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

We follow the official AWS icon set, if that doesn't contain the icon then AWS is the place to file an issue.


Fixed minor spelling error in a comment: aliged -> aligned

Question: why does the memory pointer have to be 32-byte aligned? I ran the code reserving exactly 78+32 bytes str := add(mload(0x40), 0x6C), and the execution of the function cost 3 less gas.

It must be aligned, or else other code that assumes a 32 byte alignment will break.


Fix broken markdown when code snippet has > operators

[x] Fix broken markdown when code snippet has > operators

Coverage remained the same at 84.504% when pulling 2b6aefa661c751b234821b82421b826267e4597d on fix-markdown into 9d8a23364d31b2fdfe92e28bb6e3c3a6d8051122 on master.


New face recognised with any other face add in this

Hi friends,
I m facing an issue if any new face will recognize and then given any old user name on that face.

Hi, a lot of people asked this same question. The implementation here is not face identification but face recognition. What you are asking for would be to have a confidence score. If the confidence score is below a threshold it would name the person as "unknown".
But this is not implemented yet, but you can find more information on how to implement it https://github.com/Qualeams/Android-Face-Recognition-with-Deep-Learning-Test-Framework/issues/14 and https://github.com/Qualeams/Android-Face-Recognition-with-Deep-Learning-Library/issues/8

New face recognized matched with an already added old face. if new face not added in this.

how to find confidence score

Hi sladomic
Give me any solution for how to show message to user's face not registered if new face recognize on app

Hi sladomic
Plz give m any solution for this, new face recognized without add face.

Hi, as already mentioned, this feature is not implemented, but you can try to implement it by yourself. I will share some emails I have shared with other people already.

What you ask for is used in face identification (confidence score). A lot of people asked for this, but I’m afraid, that I don’t have any time to implement this by myself at the moment (maybe in a few months).
But I can share with you what I shared with others regarding this function.
I hope this helps for a start. Best would be if you research for confidence score and probably you can come up with an implementation of a good algorithm and even share it (commit it) to the library so anyone could benefit.
Thanks and best regards,
Michael
—————————————————————————————————————————
E-Mail
—————————————————————————————————————————
Dear XXX,
First of all thanks for the interest and feedback.
Face recognition generally doesn't include the feature you mentioned. This is more a task of face identification.
But since a few other people already had the same question, you can try to implement a confidence score and set a threshold (experiment a bit to set it at the right point), so that you only tell the name if the confidence score is about the threshold and "unknown" if below.
https://github.com/Qualeams/Android-Face-Recognition-with-Deep-Learning-Test-Framework/issues/14
Here and especially in the last comment you can find information of how this could be implemented.
Please note that the confidence score I proposed is not 100% accurate. If you want to train it correctly you would need to implement a bit more complex algorithms.
Best regards
—————————————————————————————————————————
E-Mail
—————————————————————————————————————————
Hello Sir,
Can you please help me with face identification, i tried to implement confidance score using below code.

double dotProduct = featureVector.dot(featureVectorToRecognize);
double normFeatureVector = Core.norm(featureVector, Core.NORM_L2);
double normFeatureVectorToRecognize = Core.norm(featureVectorToRecognize, Core.NORM_L2);
double cosineSimilarity = dotProduct / (normFeatureVector * normFeatureVectorToRecognize);
double absoluteCosineSimilarity = Math.abs(cosineSimilarity);

But still there is not much difference that i can distuinguiss between registered and non registered faces. I have tried my best, it will be very helpfull to me if you can help me with face identification.
Please help me, Thanks in advance.
—————————————————————————————————————————
E-Mail
—————————————————————————————————————————
Hi XXX,
Sorry, I don’t have much time at the moment.
What do you take as „featureVector“?
I just see the code here to calculate the cosineSimilarity, but not the code how you calculated the „featureVector“.
The featureVector here is the mean of all feature vectors of one person.
https://github.com/elimu-ai/authentication/blob/master/app/src/main/java/org/literacyapp/authentication/thread/TrainingThread.java on line 244 we reduce all feature vectors of one student to one feature vector (meanFeatureVector). This meanFeatureVector is then used in the cosineSimilarity calculation as „featureVector“.
So what you need to do in training is, to additionally calculate the meanFeatureVector per label/person and store this for later use (so that you don’t need to calculate it every time you do the recognition).
Then when you want to do the recognition, you load the meanFeatureVectors and after you’ve got the recognized person/label, calculate the cosineSimilarity by using the person’s meanFeatureVector and the current image (featureVectorToRecognize). Then if the value is above a threshold (e.g. 0.5), you print out the name and if it’s below, you print out „Unknown“.
Good luck and regards

Thanks a lot I will try them :)

hi,
I am trying but not calculate confidence score so plz give m the solution..............

@sladomic Please let us know in case you have implemented it .Thanks

hi @sladomic any update about calculating confidence score. thank

tensorflow_jni.cc has a function to return confidence score as shown below. Can I please know how do I make use of this function
// Returns the top N confidence values over threshold in the provided vector,
// sorted by confidence in descending order.
static void GetTopN(
const Eigen::TensorMap<Eigen::Tensor<float, 1, Eigen::RowMajor>,
Eigen::Aligned>& prediction,
const int num_results, const float threshold,
std::vector<std::pair<float, int> >* top_results) {
// Will contain top N results in ascending order.
std::priority_queue<std::pair<float, int>,
std::vector<std::pair<float, int> >,
std::greater<std::pair<float, int> > > top_result_pq;
const int count = prediction.size();
for (int i = 0; i < count; ++i) {
const float value = prediction(i);
// Only add it if it beats the threshold and has a chance at being in
// the top N.
if (value < threshold) {
  continue;
}

top_result_pq.push(std::pair<float, int>(value, i));

// If at capacity, kick the smallest value out.
if (top_result_pq.size() > num_results) {
  top_result_pq.pop();
}

}

Hi
That's because they use the softmax function as the last layer in the CNNs. The softmax function gives you a probability for each class.
So instead of using KNN or SVM you could add a new classifier (softmax) and should then have the ability to use confidence scores.

@sladomic  Thanks very much for your help .
Could you PLEASE provide some inputs on how to add the 'softmax' classifier instead of using KNN or SVM in the project . I shall try to implement it

Hmm I doubt that this will work https://www.tensorflow.org/tutorials/image_retraining

I think you need more than just 20 images per person (e.g. 1000)
Tensorflow for Android removes some of the functions/operations so the training might not even be possible
The training might not be feasible on a mobile device (but maybe it's fast enough once the bottleneck features have been computed and stored for reuse)

If you really want to try out I would suggest you first gry it out on a PC. There the transfer learning should work with python. But for Android you would need to adapt the python code, build TensorFlow with special instructions for the operations and then it might still not be feasible. But on a PC you can try it out with lesd effort (still some effort though).

@sladomic Thanks I have been looking at the link for past few days. (i am ready to implement irrespective of mobile or PC)
Everything is fine, but the only problem is 'Python'.
I was looking for similar type of stuff only in C++ (need for a particular research purpose) so that it can be easily integrated in this project (or on PC) but unable to find it. :(
If you find similar content for C++ , please let me know  :)

Could I please know if the below implementation is possible
Currently the output Image Classification is 128 numbers for each training image which is then fed to SVM for training.
Instead of providing these 128 numbers of each image as input to SVM for training,
Could we provide these 128 numbers of each image as input tensorflow to create a graph/model file at runtime as shown in a link which is implemented in python http://jackytung8085.blogspot.in/2016/06/loading-tensorflow-graph-with-c-api-by.html
If so , how do we provide these 128 numbers of each image as input to tensorflow graph ?

The setup would then be as follows:

Detection
Preprocessing (at least resize the input)
Extract bottleneck features (embeddings layer in facenet)
Train 1-layer NN with 128 inputs and N-classes output and softmax activation function

Yes, that should be possible on a PC but on Android only with modifications in the build of TF for Android (google for "tensorflow no opkernel android") if you want to execute step 4. Also best would be to save the features of step 3 so they don't need to be extracted every time but can be reused (extract once per image and then save the 128-vector per image to save time).

sir how can i get the  recognized label name from the  coding.....may i  used this code for face login

Dear @chithrabaskar sorry but I don't get the question.
If you want to use it for face login you need to tweak it. At least you would need to add probabilities so you could check against a threshold if the probability is high enough for the person (confidence score) and you would need to add eye tracking, so you could detect eye blinks (so the recognition cannot be fooled by a photo)

thank u sir...sorry for my late reply...how and where to add probabilities??..can you explain in detail??

@Zumbalamambo , Great to hear you made it working ,but I am still facing the same problem to the confidence score on the Android App . I am using KNN. Could you please help me in to achieve confidence score.

I am trying but not change camera Orientation so  Orientation please give m the solution..............

has this functionality been implemented?

What is the confidence score below threshold value for unknown people?

hi, can anyone implemented New face recognised with out adding  face add in this please mail me..
<EMAIL_ADDRESS>

I am using this library  but  probelm is that every mobile perfect work  but huwai p20 and google nexus 5 crass .
when click pic once click when going to detacting face now crass at a time ...my friend in japan he have 2 device nexux 5 and huwai p20 both are in  crass..if you have any idea any why do work as like ..so please help me ..i am  10 days working on this problem but does not solve this isue....


Add UMD library build process

It's starting the build with the root package.json umd and umd:min tasks and build into dist/.
I don't know how useful this is at the time, or in its current state. Just shoot me a message with your requirements for this. ;)
This should use the existing version of webpack and
configuration for babel to build an UMD library version
of React Look.

The React package is externalised. This means that if
the UMD file is used, React must be already present
as either a commonjs2 or amd import or in the global
root var as 'React'.

Lodash on the other hand is not externalised, as the
babel plugin takes care of including only the methods
that are actually in use.

Cool :) Thanks a lot


Added a basic .travis.yml to check that the build works.

Merged w/small changes:

using https:// for Closure Linter repo
build commands are now ./do.sh build_(app|extension) debug.

Thanks, David!


fix type annotation

Codecov Report

Merging #34 (c407361) into master (a1e4163) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master      #34   +/-   ##
=======================================
  Coverage   98.64%   98.64%
=======================================
  Files           3        3
  Lines         516      516
=======================================
  Hits          509      509
  Misses          7        7

Flag
Coverage Δ

unittests
98.64% <100.00%> (ø)

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

Impacted Files
Coverage Δ

thrift_fmt/core.py
98.73% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


code

I am interested in your research, but I have some trouble in reading. So can you release your code?

I plan to upload it this month. Will do it asap.

Apologize for the delay. The code is updated now.


Appendix M content lost

Section Number *n/a content is missing; see below
Issue The prior PDF version of PDQm contains an update to Vol 2 Appx M.  See page 28 in https://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_Suppl_PDQm_Rev2-2_TI_2020-08-28.pdf
I don't see that content here.   If we decided to omit it in the IG and CP it into the Appx M, or do something else in another way, then I forgot about it.
Note that there are some inaccuracies in the tables in Appx M (eg why is date of death listed?).  If we keep the content, then those should be fixed.
Proposed Change
Priority:

Medium: Significant issue or clarification. Requires discussion, but should not lead to long debate.

It looks like appendix M was moved to profiles.ihe.net for the resolution to #23

https://profiles.ihe.net/ITI/TF/Volume2/ch-M.html#M.4
We likely need some reference from PDQm to this publication.
I think at this point any changes to appendix M would be thru normal CP process.

#35 will be adding references to M as needed. Thus there is nothing more to do for this issue. The content was not lost.