Add Secret dialect

This PR implements a secret dialect to represent generic, high level computation on encrypted data, along with a demonstration lowering pass that drops the secret types.
It defines a single new type, secret.secret<AnyType> which wraps a non-secret type, and centers around the secret.generic op, which "lifts" a computation on the plaintext types to a computation on the corresponding secret types, with some metadata attached to the high level operation encapsulated by a secret.generic so that it can be lowered to custom ops in specific dialects.
I also defined a pass, --secret-forget-secrets, which simply drops the secrets from all types and returns an equivalent program that operates on plaintext data.
Some notes:

In my examples I have secret.generic's body containing a single op, but I think more realistically we will have front ends that convert large regions of code into a large secret.generic, and then passes in this dialect that transform it by doing things like extracting loops with static bounds outside of the body of a secret.generic and only having the inner-most loop body contain secret.generic ops (which could then be further analyzed/optimized with partial loop unrolling and fusing), or something like transforming the body of a secret.generic into a combinational circuit, then applying a circuit optimizer to it.
Forgetting secrets is only intended to be useful for testing, e.g, to ensure a program is functionally equivalent before and after any FHE passes are applied. But it also helps me understand how to write passes that operate on the mildly complex IR I've defined for secret.generic.
I'd like to eventually generalize the forget-secrets pass to operate on an interface(s), and then apply that interface to lower level dialects, so that at any point during a program's compilation lifecycle, we can exit the "encrypted" part of the pipeline and test functional equivalence.

Note to self: check out llvm-project/mlir/lib/Dialect/Linalg/Transforms/Detensorize.cpp as a guiding pass, and use the DialectConversion framework to make the secret type illegal.

There are a handful of TODOs still littered throughout the PR, for improved documentation and my confusion about the dialect conversion framework. But I think now is a good time for an initial review by @asraa and @AlexanderViand-Intel

I think there is some benefit to having this checked in even if we think doing it in full generality is too ambitious. It will be useful for some experimentation and @asraa and I are interested in trying it out as an entry point for some ML-specific dialects.

Something got messed up with the internal integration of this PR, so I'm going to cut an internal patch which will show up as a PR with some weird changes in it (including the changes for Alex's two comments)

Manually merged as https://github.com/google/heir/commit/69db9f04991fdc98c12ab39d08e3480adfc6629c


CoCo /teachers/classes: add an embed of latest podcast episode

Latest podcast episode added to bottom of "My Classes" view.
The new PodcastItemComponent was extracted from podcast/BodyComponent in order to make it available anywhere else as a single entity.

oh sure, thanks for reminding me.


Do not change matplotlib style parameters

When loading scanpy through import scanpy.api as sc the plotting style is changed. This prevents my from using it in my general workflow because I have particular plotting styles I use.
This used to be a issue with seaborn, but was changed in version 0.8, but scanpy still seems to restyle the entire plotting environment?
If styles are applied locally in particular plotting functions, that is fine, but it shouldn't affect the users other plots.

Yes, agreed.
You can currently workaround with set_rcParams_Defaults. Upon import, set_rcParams_Scanpy is automatically called.
I had the impression that seaborn still changes the rcParams also after 0.8. If it doesn't I can remove the hack of resetting the params after calling seaborn.violinplot for the first time.
I agree that in Scanpy 1.0, we should remove the automatic call of set_rcParams_Scanpy and instead require this from the user.

Great! Thanks! :)
Just doing a quick check, it doesn't seem like Seaborn affects things:

Scanpy on the other hand makes the text larger and puts in a grid.

Hm, yes, such behavior is really frustrating. I was probably using old seaborn versions when coming up with the brilliant idea of fighting back its annoying behavior by building the same annoying behavior into scanpy.
Will be resolved in 1.0. Thank you for pointing it out again.

Fixed in https://github.com/theislab/scanpy/commit/57161ec444eef7815e159037c6944ddcc75572d9
However, the version1 branch is not stable yet... another day or two...
What made me believe that seaborn is still doing strange things, is this... one call to seaborn.set_style messes up the whole configuration... That's a bug, isn't it?

Ah ok, just looked it up. It's not a bug... :wink: I don't know why I misunderstood this... Must have been a long time ago...

Mm I think I you're supposed to use a context (with ... :) to avoid changing things globally.
Anyway my current workaround of doing from scanpy.api import preprocessing as scpp is not too cumbersome, so should be okay until 1.0 hits :)

Scanpy 1.0 is out and hence I can close this, I guess.


Error when instansiating a class with an enviroment variable

Describe the bug
This issue only seems to happen when upgrading to the pre-release version of VSCode which I did to fix another error I was previously having which was recommend by this github repo.
When I am initiating the resend library I am getting the following error.
 FAIL  src/app/api/survey/recruit/tests/recruit.test.ts [ src/app/api/survey/recruit/tests/recruit.test.ts ]
Error: Missing API key. Pass it to the constructor `new Resend("re_123")`
 ❯ new Resend node_modules/resend/dist/index.mjs:325:15
    323|       }
    324|       if (!this.key) {
    325|         throw new Error(
       |               ^
    326|           'Missing API key. Pass it to the constructor `new Resend("re_123")`'
    327|         );

My implementation
import { beforeEach, expect, test } from "vitest";
import { loadEnvConfig } from "@next/env";
import { Resend } from "resend";

beforeEach(async () => {
  loadEnvConfig(process.cwd());
});

test("send survey started / payment confirmed email", async () => {
  const resend = new Resend(process.env.RESEND_API_KEY);
  const generateId = () => Math.random().toString(36).substring(7);
  const fakeSurveyId = generateId();
  const fakePaymentIntent = "pi_" + generateId();

  const { data, error } = await resend.emails.send({
    from: "Some company<EMAIL_ADDRESS>    to<EMAIL_ADDRESS>    subject: "Your survey is live!",
    react: PaidSurveyLive({
      survey: {
        audience: "uk",
        question:
          "How likely are people to support a coffee brand that is environmentally friendly (test)",
        size: 1,
        id: fakeSurveyId,
      },
      paymentDetails: {
        date: new Date().toDateString(),
        discount: 0,
        total: 7900,
        paymentIntentId: fakePaymentIntent,
        paymentMethod: {
          type: "other",
          last4: "4242",
        },
        subtotal: 7900,
        tax: 0,
      },
      enviroment: process.env.NEXT_PUBLIC_ENVIROMENT === "production" ? "production" : "staging",
      previewText: "Your survey is live! Click the button below to view your survey results.",
    }),
  });

  expect(data).toBeDefined();
  expect(error).toBeNull();
});

Reproduction
I'm not sure how I could reproduce this as it is related to local enviorment variables.
System Info
I'm using Next.js 14 with .env file

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

I'm not sure how I could reproduce this as it is related to local enviorment variables.

I need a repository that I can open in VSCode and see the error. It doesn't matter if the code is the same that you have right now - you can use code from examples and create a reproducible repo there.


firebase v10

In v10, there is error in install npm i @react-query-firebase/firestore

Same here, once you are in the corresponding directory (in my case a ReactJS proyect with typescript, npm and firebase), when you use the command (in the ubuntu console): npm i --save @react-query-firebase/analytics
The following message appears:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/firebase
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@react-query-firebase/analytics
npm ERR!   @react-query-firebase/analytics@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /root/.npm/_logs/2023-12-15T18_39_38_961Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2023-12-15T18_39_38_961Z-debug-0.log

I have already tried as well updating the packages I use for the project with: npm install --legacy-peer-deps
but still get the same error.

The installation documentation points that react-query-firebase only supported Firebase JS SDK v9. This is the reason the issue above is happening.

Note: The library only supports Firebase JS SDK v9 - learn more about it here!

I went ahead and created a feature request (#96). Hopefully this package can be updated to support the newer Firebase versions 😄


Plugin completely not working on Android Studio / macOS Big Sur

This plugin is not usable on Android Studio on macOS Big Sur 11.2.3.
Specifically, it:

Does not highlights the syntax
Prevent me from editing .rules files (I mean, when I have it installed, I cannot edit anyway my .rules files)

The only clue I have that it is installed is that the icon of .rules files changes and become the little flame icon like Firebase.
I have not been able to recover any log file which may be useful to resolve this error...

Which Android studio version are you using?

Hi,
Android Studio 4.1.3
Build #AI-201.87<IP_ADDRESS>99119, built on March 11, 2021
Runtime version: 1.8.0_242-release-1644-b3-6915495 x86_64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
macOS 10.16
GC: ParNew, ConcurrentMarkSweep
Memory: 1979M
Cores: 12
Registry: ide.new.welcome.screen.force=true, external.system.auto.import.disabled=true
Non-Bundled Plugins: mobi.hsz.idea.gitignore, org.intellij.plugins.markdown, org.jetbrains.kotlin, com.jetbrains.darkPurpleTheme, com.developerphil.adbidea, pl.pszklarska.pubversionchecker, Dart, io.flutter, com.localizely.flutter-intl, tanvd.grazi, PythonCore

That's all the data I have been able to gather.

@emiliodallatorre is the issue fixed for you? let me know if the plugin is working for your mac big sur.

@emiliodallatorre is the issue fixed for you? let me know if the plugin is working for your mac big sur.

Hi,
yes: the plugin is now correctly working.
Thank you for the kind attention to this bug, it has been really appreciated.


GAM 5.33 Virus Detected: Trojan:Win32/Wacatac.D1!m

Hi,
While downloading the lates Windows x64 MSI package (GAM 5.33), Windows 10 Defender blocks the file with the following warning:
Trojan:Win32/Wacatac.D1!m detected.
Could you please review if a trojan has infected this executable.
Thanks

I also have this issue on Windows 2016 Standard, version 1607.
Windows Defender:
Antimalware Client Version: 4.18.2001.7
Engine Version: 1.1.17800.5
Antivirus definition: 1.331.524.0
Antispyware definition: 1.331.524.0
Network Inspection System Engine Version: 1.1.17800.5
Network Inspection System Definition Version: 1.331.524.0

I have the same issue with the git.exe in the gam-5.33-windows-x86_64.zip package.

Sorry, not git.exe -- in the gam.exe.

This is a false positive on the part of AV vendors. GAM uses PyInstaller to compile the Python source code into an executable. Unfortunately many malware apps also make use of PyInstaller. AntiVirus vendors don't do the work to distinguish between the two, they just assume that any app using PyInstaller is a virus.
You should report this as a false positive to your AV vendor.

same issue here.  Microsoft Windows Security flagged it as Severe

Zip file gam-5.33-windows-x86.zip is getting flagged too

Same here.. It doesn't mather if I use chrome or edge. It says virus detected. Also downloading with wget and trying to extract only gam.exe removes the file because a virus is detected.

I ended up using WSL to get something working

Sorted

Submitted the same information and confirmed that GAM is not detected now.

Sorted

Submitted the same when I reported this.  I can confirm that GAM is no longer detected by Windows Defender now -- at least as of February 15th, 8.45 AM GMT+7


Return a unit type constant when a function has no return value

E.g.
fn f() {
asm ( .. ) {
// no return value. Just a log for example
}
}
In the above, the asm block doesn't return anything but we still return its result (of type ()) from f(). Instead, I'm now returning a separate const () directly which seems to simplify a few things downstream. The current code is causing an illegal move to be generated (a move from a register that isn't assigned) which causes some issues in the register allocator. With this patch, the problem goes away.

There's probably a few ways of doing this but this seems to be the quickest.

Yeah, if feels like you're treating the symptom and not the cause..?  This will need a follow up.

The ASM for any script/contract which used to implicitly return unit is now explicitly loading a unit (zero) from the data section, but is still returning $zero.  Not ideal, but neither is a lot of the new post-IR ASM until we get in there and aggressively clean it up, which I'm absolutely busting to do, but isn't p.critical at this stage.
Looks like I was premature with just call_basic_storage, other contracts have changed too...

@otrho thank you so much for fixing the tests! 🙌


Update Composer dependencies (2022-06-10-00-07)

Visual regression test passed!
View the visual regression test report


[cleanup] [trivial] Change more functions to return bool

Auto-merge toggled on

@braddr: An idea: How about instead of posting a comment with 'Auto-merge toggled on" the pull instead gets marked with the label "Auto-merge"?


Feature request: self referencing a note the dataview snippet is in?

Maybe this is already possible, in which case it's a documentation request.
It would be useful if a snippet could use / reference attributes of the note a dataview snippet is in.
So that e.g. thisnote.path or thisnote.mtime can be used in equations.
And so that template dataview snippets can be used.

I was actually working on exactly this (accessing self fields through this), though I seem to be unable to actually access the current file in Obsidian from the Markdown post-processor (where I generate the dataview). I've asked around and will put in a request for it in the API so I can properly add this.

Support for this has been added in recent Obsidian versions, so will be added to an upcoming release.

Released as part of 0.2.6.


project cards are not showing up due to missing comma in code [gssoc'21]

project cards are not showing up due to missing comma at correct place in code. Kindly assign this issue to me as a participant of gssoc 2021.

@ishita-sehgal Sorry to say and thanks for help but I have solved this issue!

Okay :)


anchor links, plaintext->html

likely will have to use Xmlm (couldn't make it work without it)

done, not using Xmlm


Add helpers to disable progress bars globally + tests

Solve https://github.com/huggingface/huggingface_hub/issues/978 (see API discussion in issue).
@sgugger Since both HF_HUB_DISABLE_PROGRESS_BARS env variable and disable_progress_bars()/enable_progress_bars() helpers are defined, there might be a conflict at some point if not correctly handled. For example a library, could call disable_progress_bars() even though the user has set HF_HUB_DISABLE_PROGRESS_BARS=0. Current solution is that disable_progress_bars() has higher priority but I'm not 100% sure it's clever.
The other solution would be the opposite: if HF_HUB_DISABLE_PROGRESS_BARS is set (either 0 or 1), then disable_progress_bars/enable_progress_bars are ignored in the code with a warning ("cannot programmatical disable progress bars as verbosity has been set by environment variable").
What is your opinion about it ? I feel that both are correct, it's more a usage preference.
EDIT: after discussion below, we went for solution 2 (environment variable has priority).

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

I think the env variable should get priority over programmatic functions. My reasoning being that if the user goes out of their way to set it on the env level, it's really clear they want that thing all the time. But it's just my 2 cents and going the other way around also works.

Makes sense. That's what I also started to think when writing the PR text actually but didn't want to change the code before having a second opinion :D
Will make the change.

@sgugger I made the changes to give priority to env variable in commit https://github.com/huggingface/huggingface_hub/pull/987/commits/b47378a7f6b9f10906bb5d817c78255e8ca37598.
Could you quickly review it so that I can merge ? Thanks in advance 🙏


test_models.py fails

The model test fails for the current version.
See below for verbose=0:
$ python test/test_models.py
Test sequential
Traceback (most recent call last):
File "test/test_models.py", line 43, in
model.fit(X_train, Y_train, batch_size=batch_size, nb_epoch=nb_epoch, show_accuracy=True, verbose=0, validation_data=(X_test, Y_test))
File "/home/thread/workspace/keras/keras/models.py", line 294, in fit
return callbacks.callbacks[-1]
IndexError: list index out of range

Thank you for pointing this out! It's fixed now. A screw-up on my part.


makeTiledWorld import .tsx tileset file

Hello,
First of, awesome project, I'm taking really big shortcuts for a project I'm working on with this codebase!
I'm wondering if it's possible to read a .tsx tileset file instead of having to import the whole tileset into the tiled .json export. I could use this because on the designteam I'm working with is using 1 general .tsx tileset file to create their levels.
Kind regards,
Thomas Verleye

Hi Thomas!
Glad you're enjoying Hexi!
I'm using it every day for my production work too (making educational games.)
I'm really sorry but reading .tsx files is not a feature.
Also, it's not on my road map for future, but if someone wants to create a plugin for it, that would be awesome!
The place to do it would be in this module:
https://github.com/kittykatattack/tileUtilities

While we are thinking of features, the one I miss is support for multiple tilesets. Tiled allows the use of different tiles (e.g. I might have items in one tileset and then map tiles in another tileset).
I guess Thomas meant .tmx files which is Tiled's native format. .json serves me well.
Another observation:

If I have a map without a "name" tile property for at least one tile, it will fail to load. This is strange and was hard to catch for me.


GitlabUrlReader: Allow fetch:plain Scaffolder action to use user-provided token

Hey, I just made a Pull Request!
The Scaffolder action fetch:plain allows the user to input a token, however, in the GitLab case,  the action fallsback to the integration token.
This PR allows user-provided tokens (private or bearer) to be used in the requests.
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Not stale, waiting for review.


Rename proposer into leader

Description

Checklist

[ ] Targeted PR against correct branch.
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Wrote unit tests.
[ ] Re-reviewed Files changed in the Github PR explorer.

Codecov Report

:exclamation: No coverage uploaded for pull request base (paul/rename-in-solana-way@b9f2a7a). Click here to learn what that means.
The diff coverage is n/a.

@@                     Coverage Diff                      @@
##             paul/rename-in-solana-way     #166   +/-   ##
============================================================
  Coverage                             ?   65.22%
============================================================
  Files                                ?       34
  Lines                                ?     1524
  Branches                             ?        0
============================================================
  Hits                                 ?      994
  Misses                               ?      499
  Partials                             ?       31

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 b9f2a7a...93f0b61. Read the comment docs.


How to calculate mAP?

I have a trained model using keras_yolo2.  Now i want to evaluate this trained model. i.e calculate mAP . How can I do it?

https://github.com/rodrigo2019/keras_yolo2/blob/master/evaluate.py


Deprecates unnecessarily public types to ease burden

Types like Properties and AutoConfiguration and internal utilities are
routinely marked public when they needn't be. This causes toil as we
have to preserve signatures even if they were made public by accident.
This deprecates the mass of types marked public to give some hope of
less undifferentiated toil in the future. Ideally, future change will
consider greatly if a type should be public or not as doing so haunts
maintainers.

@spencergibb then the solution is to just change them without deprecation? Some of these need to disappear in 3.x

anyway I will revert the deprecated on properties thing, 3.x breaks many classes anyway. thanks

thanks for the look @spencergibb I sometimes wonder if anyone ever looks at PRs here. Nice you have eyes out https://github.com/spring-cloud/spring-cloud-sleuth/pull/1639

Thanks!


Generic http client handler does not work well with okhttp

I'm trying to use HttpClientHandler with OkHttp and use it inside network interceptor.
When HttpClientHandler.handleStart is invoked, it supposed to inject header.
Unfortunately, OkHttp uses builder pattern to construct requests and the only way to add a header is through builder (see https://stackoverflow.com/questions/32196424/how-to-add-headers-to-okhttp-request-interceptor)
It is possible to supply HttpClientHandler with request builder, but it seems to be inefficient (re-building and extra allocations).
The only efficient way to instrument okhttp seems to be:

create request builder
start span
inject trace context
build request
fill attributes (yes, you can fill them from request, but not the builder 👎 )

But this approach also does not work with the network interceptor (and it nice to be able track redirects and retries without thinking about the position in the handler list)
So I think the right long-term plan is to fix it on the okhttp side.
@rghetia am I missing something in the handler design? what http libs it intends to work with?
What version of OpenCensus are you using?
0.19.0

@lmolkova I have used it with jetty. I am not familiar with okhttp but let me look into it.

I looked at okhttp and agree with your assessment. Another problem with creating span during request builder is that the actual request may be executed later and there by creating longer span than what it is.

@rghetia thanks for looking into this.
I've created feature request for okttp: https://github.com/square/okhttp/issues/4459

As per conversation in the square/okhttp#4459 there is no support from the okhttp team to save a couple of allocations,

The request object is immutable by design. I don't see any reason to change
that and lose all the benefits therein without proof these allocations are
actually prohibitive to performance. And that finding would be extremely
surprising given the other allocations and work that must be done
per-request.

It also makes it hard to use HttpClientHandler with okhttp as it requires special treatment  - rebuilding. Probably the easiest approach is to have a special handler implementation.


Color picker not dismissing after changing settings

Microsoft PowerToys version
0.41.4
Running as admin

[X] Yes

Area(s) with issue?
ColorPicker
Steps to reproduce

open color picker
open power toys settings
select color picker
change activation behavior to color picker only then back (while color picker is still open)

✔ Expected Behavior
i expect that the open color picker would change modes or close when settings is open.
❌ Actual Behavior
A color picker is stuck to my screen and is not dismissible or able to be used at all.
Other Software
No response

This is interesting, I can't seem to repro on my machine. @dragoncommits , can you please attach the logs generated by the bug report tool in your systray?

Also, does this behavior happen every time you perform the repro steps, or only occasionally?

Updated steps to get this bug every time
select editor setting
open color picker
while it is still open select color picker only
PowerToysReport_2021-07-28-00-00-36.zip

Ok great, thanks. The logs don't seem conclusive, but we'll investigate further in the coming releases.

I've been able to replicate this in 0.41.4.
I expect this to be fixed on the next release, though, since it's no longer possible to replicate it on master.
This should be fixed after https://github.com/microsoft/PowerToys/commit/65618ffa9cdc7cbdfd54fc97265802baf54e336b gets released.


Add actions/cache

Codecov Report
Patch and project coverage have no change.

Comparison is base (d1441ae) 78.38% compared to head (4fd9edd) 78.38%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##             main      #13   +/-   ##
=======================================
  Coverage   78.38%   78.38%
=======================================
  Files          53       53
  Lines        1841     1841
=======================================
  Hits         1443     1443
  Misses        398      398

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


AppWebSocket is not provided by runPrerenderedRhyoliteWidget

The Kiln code used AppWebSocket provided by runRhyoliteWidget, but that API has been removed and now we only have runPrerenderedRhyoliteWidget,which doesn't provide it.

I noticed this as well. Would be nice to have it passed out like it used to be.


 I have not tried tested outside of a crossProject.

For now, I think a good workaround might be to define commonSettings or an ad-hoc AutoPlugin.

This is now likely fixed in sbt 2.x https://github.com/sbt/sbt/pull/6746/commits/dbaa34bdacb796dfca54ecc83e8ed85ea27b5756


📝[DOCS]  (Grammatical Mistake)

Issue Description
this should be changed to this.
"Got a Idea? We've got the skills. Let's team up". to  "Got an Idea? We've got the skills. Let's team up !!!"

Its is "an idea" not "A idea". (Simple Grammer)
There is not much difference in this, but the impact is huge while you read the second sentence.
(Just Psychology)

Screenshots or Examples (if applicable)

Checklist

[X] I have checked the existing issues.
[X] I have read the Contributing Guidelines.
[X] I have read the Code Of Conduct.
[X] The changes doesn't break the code

Please assign me this issue.

Please assign me this and add gssoc label to this.

Please add gssoc tag to my issue, this issue is already solved and merged successfully


Create slack tags for different teams in the big channel and the lead channel

Create slack tags for different teams in the big channel.(Ex: @fe-eng, @be-eng, @ux-eng, @infra, etc). I think the tags are isolated to one channel but if they aren't then the tag will have to look more complex
Create slack tags in the lead channel to divvy up by skillset, or maybe team? Not sure

ZenHub Information
This information is updated automatically. To modify it, please use ZenHub.

Got done when we got upgraded to Plus!


Android pick callbacks revision

This clears up some confusion and ambiguity in the feature/label/marker picking interfaces in the Tangram Android SDK.

Updated documentation to clarify that pick calls will always result in a callback (when a listener is set). Success of the pick is expressed in the result object passed to the callback.
onFeaturePick etc. have been renamed to onFeaturePickComplete to both distinguish the updated method signatures and to emphasize that the pick is complete, but not necessarily successful.
Callback methods now take a single result object as their argument, which will be non-null if the pick call resulted in a feature/label/marker and will be null otherwise.

@matteblair this requires some more old context for me to understand and refresh my memory on the API usages. I am going to get to this during the holidays, sorry for the delay.

This is great! I was about to look up how this worked internally and report that the feature/marker/label pick listener is not called when the result is empty if that would have been the case. The way you implemented it - that the listener is always called - makes it feasible to extend the MapController to be used with Kotlin coroutines. Simplified example:
suspend fun MapController.awaitPickMarker(posX: Float, posY: Float) =
    suspendCoroutine<MarkerPickResult?> { cont ->
        c.setMarkerPickListener { markerPickResult ->
            cont.resume(markerPickResult)
        }
        c.pickMarker(posX, posY)
    }

This enables to write code like this, which is cleaner than juggling with the callbacks
suspend fun clickAt(clickPosition: PointF) {
    val pickResult = controller.awaitPickMarker(clickPosition.x, clickPosition.y)
    if (pickResult == null) {
        toast("Hmm, no marker here...")
    } else {
        val x = pickResult.coordinates.longitude
        val y = pickResult.coordinates.latitude
        toast("Found a marker at $x, $y!")
    }
}


Move non vital nginx over to router

References #1616
Type
🚑 Health
Moving the less detrimental parts of the proxy to the router.

Close in favour of #1711


android build failed

i tried to build the apk ,
build got failed
Execution failed for task ':emoji_picker_flutter:compileReleaseKotlin'  Inconsistent JVM-target compatibility detected for tasks 'compileReleaseJavaWithJavac' (1.8) and 'compileReleaseKotlin' (17).

flutter doctor

Did you try flutter clean?

Did you try flutter clean?

Same problem here, and yes i tried "flutter clean"

I needed to update my kotlin version to 1.9.22 to compile again...
https://plugins.gradle.org/plugin/org.jetbrains.kotlin.android/1.9.22

Did you try flutter clean?

yes i did

I had the same issue after I upgraded Flutter SDK today.
Could you please try if adding the below line to android/gradle.properties works for you?
kotlin.jvm.target.validation.mode=IGNORE

https://stackoverflow.com/questions/77520506/inconsistent-jvm-target-compatibility-detected-for-tasks-despite-already-definin

Couldn't reproduce the issue. But I assume it is due some change in Kotlin 1.8 (issuetracker)
Might be possible to solve it by adding following to your build.gradle.
android {
   ...
   compileOptions {
       sourceCompatibility JavaVersion.VERSION_17
       targetCompatibility JavaVersion.VERSION_17
   }
}

kotlinOptions {
    jvmTarget = '17'
}

Can you try?

I'm facing the same issue, i try to update the emoji_picker to 2.1.0 from 1.6.4 in flutter 3.19, and the build failed for me.
I try to use this options also but dindt work for me
android {
...
compileOptions {
sourceCompatibility JavaVersion.VERSION_17
targetCompatibility JavaVersion.VERSION_17
}
}
kotlinOptions {
jvmTarget = '17'
}
im my opinion its better to downgrade the emoji picker, when i try to upgrade the kotlin, others packages failed, is better to following the same versions as flutter using and waiting for the emoji_picker to fix this erro

I downgraded Kotlin version in this branch, can somebody check if that fixes the issue?
  emoji_picker_flutter:
    git:
      url: https://github.com/Fintasys/emoji_picker_flutter.git
      ref: downgrade-kotlin

I downgraded Kotlin version in this branch to 1.7.10, can somebody check if that fixes the issue?
  emoji_picker_flutter:
    git:
      url: https://github.com/Fintasys/emoji_picker_flutter.git
      ref: downgrade-kotlin

What went wrong:
Execution failed for task ':emoji_picker_flutter:compileDebugKotlin'.

'compileDebugJavaWithJavac' task (current target is 1.8) and 'compileDebugKotlin' task (current target is 17) jvm target compatibility should be set to the same Java version.
Consider using JVM toolchain: https://kotl.in/gradle/jvm/toolchain
2

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.

I have the same issue when upgrading flutter.
tried:
compileOptions {
        coreLibraryDesugaringEnabled = true
        sourceCompatibility = JavaVersion.VERSION_1_8
        targetCompatibility = JavaVersion.VERSION_1_8
    }

    kotlinOptions {
        jvmTarget = "1.8"
    }

as well as:

    compileOptions {
        coreLibraryDesugaringEnabled = true
        sourceCompatibility = JavaVersion.VERSION_17
        targetCompatibility = JavaVersion.VERSION_17
    }

    kotlinOptions {
        jvmTarget = "17"
    }

I downgraded Kotlin version in this branch to 1.7.10, can somebody check if that fixes the issue?
  emoji_picker_flutter:
    git:
      url: https://github.com/Fintasys/emoji_picker_flutter.git
      ref: downgrade-kotlin

Without a example project to reproduce the issue it is difficult to fix.
I updated the branch above to match its content like a newly generated package. Maybe someone can try again?
Based on the link @RasmusGrift96 provided there was one comment with a fix, maybe also worth a try.
https://github.com/flutter/flutter/issues/125181#issuecomment-1555034383

Adding to my pubspec.yaml:
emoji_picker_flutter:
    git:
      url: https://github.com/Fintasys/emoji_picker_flutter.git
      ref: downgrade-kotlin

gave the same error for me.
As I'm on a different kotlin version, I also tried changed it. (together with the git)
In my settings.gradle file changed:
id "org.jetbrains.kotlin.android" version "1.8.20" apply false
in
id "org.jetbrains.kotlin.android" version "1.7.10" apply false
this gave me errors in the form of:
 e: C:....../recaptcha.proto.mobile_webview_sdk_kt_proto_lite.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
e: C:....../jetified-recaptcha-18.4.0-api.jar!/META-INF/third_party.java_src.protobuf.current.java.com.google.protobuf.kotlin_only_for_use_in_proto_generated_code_its_generator_and_tests.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
e: C::....../jetified-recaptcha-18.4.0-api.jar!/META-INF/third_party.java_src.protobuf.current.java.com.google.protobuf.kotlin_shared_runtime.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.
e: C:....../jetified-play-services-measurement-api-21.5.1-api.jar!/META-INF/java.com.google.android.gmscore.integ.client.measurement_api_measurement_api.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.7.1.

So I think I have to be on a newer kotlin version to get my app working.
In the new flutter version you had to change some gradle files to get it compatible with the new flutter version.
Maybe you can see what is wrong if I post them here:
settings.gradle
 pluginManagement {
    def flutterSdkPath = {
        def properties = new Properties()
        file("local.properties").withInputStream { properties.load(it) }
        def flutterSdkPath = properties.getProperty("flutter.sdk")
        assert flutterSdkPath != null, "flutter.sdk not set in local.properties"
        return flutterSdkPath
    }
    settings.ext.flutterSdkPath = flutterSdkPath()

    includeBuild("${settings.ext.flutterSdkPath}/packages/flutter_tools/gradle")

    repositories {
        google()
        mavenCentral()
        gradlePluginPortal()
    }
}

plugins {
    id "dev.flutter.flutter-plugin-loader" version "1.0.0"
    id "com.android.application" version '8.2.2' apply false
    id 'com.android.library' version '8.2.2' apply false
    id "org.jetbrains.kotlin.android" version "1.7.10" apply false
    id "com.google.gms.google-services" version "4.4.0" apply false
    id "com.google.firebase.crashlytics" version "2.9.9" apply false
    id 'org.gradle.toolchains.foojay-resolver-convention' version '0.7.0'
}

include ":app"

in my build.gradle:;
plugins {
    id "com.android.application"
    id "kotlin-android"
    id "dev.flutter.flutter-gradle-plugin"
    id "com.google.gms.google-services"
    id "com.google.firebase.crashlytics"
}

dependencies {
    implementation 'com.google.android.material:material:1.11.0'
    testImplementation 'junit:junit:4.13.2'
    androidTestImplementation 'androidx.test:runner:1.5.2'
    androidTestImplementation 'androidx.test.espresso:espresso-core:3.5.1'
    implementation 'com.google.firebase:firebase-analytics:21.5.1'
    implementation 'com.google.firebase:firebase-auth:22.3.1'
    coreLibraryDesugaring('com.android.tools:desugar_jdk_libs:2.0.4')
    implementation 'com.google.android.gms:play-services-auth:21.0.0'
    implementation 'com.google.firebase:firebase-messaging:23.4.1'
    implementation 'androidx.window:window:1.2.0'
    implementation 'androidx.window:window-java:1.2.0'
    implementation('com.google.firebase:firebase-auth') {
        exclude module: "play-services-safetynet"
}
    constraints { implementation('com.stripe:financial-connections') { version { strictly '20.11.0' } } }
}

I'm not very skilled in kotlin/gradle so if I make some ugly mistakes, I'm happy to learn

I downgraded Kotlin version in this branch to 1.7.10, can somebody check if that fixes the issue?
  emoji_picker_flutter:
    git:
      url: https://github.com/Fintasys/emoji_picker_flutter.git
      ref: downgrade-kotlin

This fix works.
Last week we moved  our project to 1.9.22 to get emoji_picker_flutter to compile our production app that uses 100+ packages with 600k android installs.  Moving to 1.9.22, Gradle 7 produced warnings of mixing old java with java 17 (used by 1.9.22).  Fyi these warnings are defaulted to errors in Gradle 8.
Our user perceived crash rate had been in the normal range of 0.15%.  Updating our user base to the 1.9.22 build the crash rate began climbing, hit 6% within 2 days. 99.9% of the crashes were in android library code when resuming the app from background.
Crash rate did not change with the our 500k iOS users.  So we looked at android specific changes between releases.
We created a fork of emoji_picker_flutter setting kotlin to 1.7.10 and reverted our project back to 1.7.10.  The java old/new mix warnings go away.  We released this version of the app 2 days ago and crash rate has been restored to sub 0.15%.
Again reverting emoji_picker_flutter to 1.7.10 fixes the build and crash issues we were seeing.

https://github.com/flutter/flutter/issues/125181#issuecomment-1555034383
Doing this worked for me, even for
emoji_picker_flutter: ^2.1.0
Not sure what the issue is.,

I had the same issue after I upgraded Flutter SDK today. Could you please try if adding the below line to android/gradle.properties works for you?
kotlin.jvm.target.validation.mode=IGNORE

https://stackoverflow.com/questions/77520506/inconsistent-jvm-target-compatibility-detected-for-tasks-despite-already-definin

working for me

I had the same issue after I upgraded Flutter SDK today. Could you please try if adding the below line to android/gradle.properties works for you?
kotlin.jvm.target.validation.mode=IGNORE

https://stackoverflow.com/questions/77520506/inconsistent-jvm-target-compatibility-detected-for-tasks-despite-already-definin

working for me

Noice, This seems to work as well.

Yours is a lovely package, but I was having the same issue
I decided to look into the error and have found following direct instructions from it to be the solution for me.
Before looking into what I did, here's the outline of my project configuration:

Build pipeline upgraded according to https://docs.flutter.dev/release/breaking-changes/flutter-gradle-plugin-apply
AGP (com.android.application) 8.1.8
Kotlin (org.jetbrains.kotlin.android) 1.8.22
Gradle 8.0-all
AndroidX and Jetifier enabled for Gradle.
org.gradle.jvmargs=-Xmx2048M (increased to avoid crashes while caching)
compileSdkVersion 34
minSdkVersion 29
compileOptions and kotlinOptions version 1.8

This might not be relevant if you're on gradle 7..., however, new Gradle requires that every package defines a namespace under android. I couldn't be bothered to facilitate this in an orderly fashion so I worked around this by changing my android level build.gradle's subprojects from:
subprojects {
    project.buildDir = "${rootProject.buildDir}/${project.name}"
}

To:
subprojects {
    project.buildDir = "${rootProject.buildDir}/${project.name}"
    afterEvaluate { project ->
        if (project.hasProperty('android')) {
            project.android {
                if (namespace == null) {
                    namespace project.group
                }
            }
        }
    }
}

Personally I've been having some issues with R8 minification (Missing classes detected while running R8). I fixed that by copying generated rules from build/app/outputs/mapping/release/missing_rules.txt into android/app/proguard-rules.pro and configuring the proguard file in my app level build.gradle via proguardFiles 'proguard-rules.pro' under android.buildTypes.release.
Important changes I've made to my project are at https://github.com/GlitterWare/Passy/commit/6bd7707b1faba45b98eeef7ef541f5b230a4b3b8 and https://github.com/GlitterWare/Passy/commit/addf7a076ce85e3559a353da9efa45083c8b9420.
You can find the exact project I was building at https://github.com/GlitterWare/Passy/commit/0bd62f51ef30c6dbba626b9f865efeb08e542170`. Feel free to clone this commit and test it out on your end.
Now onto changes I've made to your package:
It seems that, for some reason, the default value for android.kotlinOptions.jvmTarget has been changed for 17. For this reason, it needs to be manually set back to 1.8. To avoid similar problems in the future, I've also changed set the version in compileOptions, just like what you did on your fix branch (this is not the cause of current problem but it might become important in the future).
Here's what your project's build.gradle file looks like on my branch:
...
android {
    compileSdkVersion 34

    compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
    }

    kotlinOptions {
        jvmTarget = '1.8'
    }
    ...
}
...

I have created a pull request over at https://github.com/Fintasys/emoji_picker_flutter/pull/192, merge it if it works for you.
Thank you once again for providing this package, it is a wonderful addition to my application.

Hello @jerryrox @RasmusGrift96 @MBilalMurtaZa , I'm aware that the issue is "fixed" on your end but it would be greatly appreciated if you could try the fork I've created at https://github.com/GlitterWare/emoji_picker_flutter . This will both assist the maintainer in asserting correct behavior across projects and might help you avoid future problems caused by ignoring this error.
I can confirm correct behavior across 2 independent Flutter projects with different Gradle versions (8.0-all and 7.6.3-all).
To do so, remove the line that you have added earlier to ignore the error and replace the emoji_picker_flutter dependency with
  emoji_picker_flutter:
    git:
      url: https://github.com/GlitterWare/emoji_picker_flutter
      ref: ba7e1116380e37bb3fac0d53277dd6937d8849d5

Thank you!

Hello @jerryrox @RasmusGrift96 @MBilalMurtaZa , I'm aware that the issue is "fixed" on your end but it would be greatly appreciated if you could try the fork I've created at https://github.com/GlitterWare/emoji_picker_flutter . This will both assist the maintainer in asserting correct behavior across projects and might help you avoid future problems caused by ignoring this error.
I can confirm correct behavior across 2 independent Flutter projects with different Gradle versions (8.0-all and 7.6.3-all).
To do so, remove the line that you have added earlier to ignore the error and replace the emoji_picker_flutter dependency with
  emoji_picker_flutter:
    git:
      url: https://github.com/GlitterWare/emoji_picker_flutter
      ref: ba7e1116380e37bb3fac0d53277dd6937d8849d5

Thank you!

Deleted the line from the gradle.properties which I added before:
kotlin.jvm.target.validation.mode=IGNORE
Added to my pubspec.yaml:
emoji_picker_flutter:
    git:
      url: https://github.com/GlitterWare/emoji_picker_flutter
      ref: ba7e1116380e37bb3fac0d53277dd6937d8849d5

Worked!!
Nice job :)

@GleammerRay I just merged your PR, when I realized we already have this line in package build.gralde
    if (project.android.hasProperty("namespace")) { namespace 'com.fintasys.emoji_picker_flutter' }

The explicit namespace declaration of your PR should not be required, so I removed it again.

we already have this line in package build.gralde

Oh whoops, my bad, I haven't noticed that. This way of declaration might be more efficient indeed. 😅

Just published 2.1.1 to pub.dev, please check and let me know if we can close this issue 🙏

@Fintasys You should close this issue. I can confirm it's fixed.

I have a new greenfield project. On 2.1.0, it would not build. I had the above error.
I upgraded to 2.1.1 and can confirm that both debug and apk are building now

Unrelated, I had another build error. My settings.gradle needed updating and the plugins block now looks like this:
plugins {
    id "dev.flutter.flutter-plugin-loader" version "1.0.0"
    id "com.android.application" version "7.3.0" apply false
    id "org.jetbrains.kotlin.android" version "1.9.23" apply false
}

Many thanks for your work on this plugin. Much appreciated. And thanks to @GleammerRay for the fix.


Provide pre-conditioners for iterative methods

It is well known that many iterative methods work much better if provided with a suitable preconditioner. We should thus aim to facilitate specifying such preconditioner. We should also provide basic examples such as a Jacobi (or diagonal) preconditioner.

Looking at COLA could be helpful:
https://github.com/wilson-labs/cola/blob/main/cola/linalg/preconditioning/preconditioners.py


Rainbird rain sensor not working (Error 503)

Home Assistant release with the issue:
0.101.2
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):
Raspberry PI / Debian
Integration:
Rainbird (Rain Sensor)
Description of problem:
It is not showing the right status and logs show an warning:
Response: 503, Service Unavailable
12:20 PM components/rainbird/sensor.py (WARNING) - message first occurred at 12:06 PM and shows up 23 times

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
rainbird:
  - host: <IP_ADDRESS>
    password: !secret rainbird_password
    trigger_time: 6
    zones:
      1:
        friendly_name: Small Garden
        trigger_time:
          minutes: 8
      2:
        friendly_name: Front Garden
        trigger_time:
          minutes: 8
      3:
        friendly_name: Back Garden
        trigger_time:
          minutes: 8

Traceback (if applicable):

Additional information:

@difelice Looks like the server is currently unavailable, therefore it throws the status code 503. See this link for more information.
Since when do you have this warning in your logs?
Have you tried to update to the newest version?

@difelice Do you use also another application to connect to rainbird? The rainbird controller is just dummy device which can not handle more connections at the moment. So try to disconnect other devices. Also change default trigger time to minutes. Querying too often could cause lock.

@springstan yes, what is strange here is the the sprinkler switches are just fine. It’s only the sensor not working anymore. I think this started to happen on a recent refactor.
@konikvranik I still have the official IOS app install but I don’t see any connections happening unless I open the app (Mitmproxy).
I’m not sure what do you mean about “too often”. Isn’t trigger_time the default time a sprinkle will be on?
Is there another option to “refresh” state less often and prevent the error.
Thank you both for replying.

@springstan yes, what is strange here is the the sprinkler switches are just fine. It’s only the sensor not working anymore. I think this started to happen on a recent refactor.

Really weird, I could not find a recent refactor of this integration that could explain this issue.

Is there another option to “refresh” state less often and prevent the error.

You could set the update_interval for this integration, however the default interval is already set to one hour.

@springstan Try to change default trigger_time: 6 to
trigger_time:
    minutes: 6

@springstan Try to change default trigger_time: 6 to
trigger_time:
    minutes: 6

I was having the exact same issue, this resolved it.

I tried that and I'm still getting the error on the UI log section. Not sure where's that coming from but it's definitely not in the home-assistant.log file.


Conflict with Vanityslots

Having Vanityslots and biome makeover causes a crash caused by biome Makeover on the client side. (Server side, it loads fine, weirdly enough.)
crash-2022-01-22_10.03.29-client.txt

Nevermind, like a dumbass, I forgot to remove an old cosmetic slots mod on my client and for some reason it blames biome makeover for that. Sorry!


scroll + javascript google.maps

When mcustomscrollbar is with google maps then map has lags, freezes - it is 100% fault of scroll because when I didnt workaround like this:
$("#map").hover(function(){
$(".wrapper").mCustomScrollbar("disable");
}, function(){
$(".wrapper").mCustomScrollbar("update");
});
It works good but reinitialize mcustomscrollbar not giving smooth working on website...
Any1 have idea how to solve this problem? maybe stop scrollbar on hover some other way, I don't know. Please help :)

It's me again, this solution works only for chrome :/


chore: update dependencies

Just bumps up a bunch of deps to the newer versions.

Codecov Report
Patch and project coverage have no change.

Comparison is base (f2a5886) 78.20% compared to head (75b10f0) 78.20%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #57   +/-   ##
=======================================
  Coverage   78.20%   78.20%
=======================================
  Files           3        3
  Lines         312      312
=======================================
  Hits          244      244
  Misses         53       53
  Partials       15       15

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

How did you change those version dependencies?
Don't we have dependabot to do these changes.
Should we really change indirect dependencies?

Do we have something like make vendor to verify that the dependencies are correct during CI?

I updated the dependencies by running go get -u, and then vendored it with go mod tidy + go mod vendor. I don't think Dependabot tracks indirect dependencies.

Do we have something like make vendor to verify that the dependencies are correct during CI?

Doesn't look like it, let me add it. Would you want it in this PR itself, or a different PR?

I updated the dependencies by running go get -u, and then vendored it with go mod tidy + go mod vendor. I don't think Dependabot tracks indirect dependencies.

Should we really change indirect dependencies? I am not yet convinced. We have those because other projects pull them in and I am not sure it is correct to update those if the vendored in projects use something else.

Do we have something like make vendor to verify that the dependencies are correct during CI?

Doesn't look like it, let me add it. Would you want it in this PR itself, or a different PR?

Separate PR sounds good.
Something like go mod tidy vendor verify and then maybe a git diff to verify nothing changed.
Please have a look at other go projects how they verify stable dependencies in CI.

We have those because other projects pull them in and I am not sure it is correct to update those if the vendored in projects use something else.

AFAIK, doing go get -u updates the indirect dependencies to the version that the direct dependencies themselves use. So they are changed only if one of our direct deps has bumped them up in the respective go.mod.

I am still skeptical about updating indirect dependencies. That sounds unnecessary.

We have those because other projects pull them in and I am not sure it is correct to update those if the vendored in projects use something else.

AFAIK, doing go get -u updates the indirect dependencies to the version that the direct dependencies themselves use. So they are changed only if one of our direct deps has bumped them up in the respective go.mod.

From the documentation it looks like go get -u  attempts to upgrade all direct and indirect (transitive) dependencies^1, and indirect dependencies can be updated beyond what is required by the direct dependencies.

@rst0git so, are in favour of upgrading indirect dependencies or not? :wink:

so, are in favour of upgrading indirect dependencies or not?

I also think it may be unnecessary to upgrade the indirect dependencies unless we have a specific reason to do so.


build(publish): nightly publish script

Description:
THIS SCRIPT DOESN'T PUBLISH ANYTHING YET
I've promised this for a while, and finally able to stab at very initial steps for this.
This PR works on our travis cron job runs daily on master, replaces version in package.json into specific nightly scheme and publish it.
Since travis doesn't have npm auth token yet, all of this script is safe at this moment and does not publish anything - before start publish, need to conclude couple of things

[x] what's semver safe version scheme for nightly?
: using --tag=nightly as suggested
[ ] is publish script in here is correct? (run npm publish under dist/package)

Related issue (if exists):
#3008

what's semver safe version scheme for nightly?

Just do something like 5.5.0-nightly.COMMIT_SHA_HERE That should be fine. And make sure it's tagged with nightly.

Although, I'm not sure I want to junk up the npm versioning with 365 builds a year... Maybe the same version every time would be better?
It's worth researching the best approach.

@benlesh

shouldn't it be 6.0-nightly? this is intended for master.
are you referring creating git tags, or other else?

I'm not sure I want to junk up the npm versioning with 365 builds a year... Maybe the same version every time would be better?

: makes sense. Maybe we can define one version only and stick for nightly.

Now PR doesn't modify but publish with --tag=nightly as suggested.

and we can actually turn this into general publish script for tagged, regular build as well 🤔  let's proceed separately, once after we verify nightly actually works.

Marking as blocked until getting conclusion for version number strategy.

With TypeScript, the maintainers use a concatenated year, month and day:
$ npm dist-tag ls typescript
beta: 2.0.0
insiders: 2.6.2-insiders.20171120
latest: 2.6.2
next: 2.7.0-dev.20171203
rc: 2.6.0-rc

If it's a nightly, using a date-derived number has the additional advantage of allowing devs to quickly see how old/recent the nightly is.

Maybe we can define one version only and stick for nightly.

http://blog.npmjs.org/post/77758351673/no-more-npm-publish-f

With TypeScript, the maintainers use a concatenated year, month and day:

Yeah, that was my initial take. @benlesh 's primary concern is stacking up new pkgs per each day afaik.

Sorry, I thought the plan was to always tag with nightly. ... my concern was over how to add versions if needed... like 5.5.0-nightly.SHA_HERE or something... and will that junk up the npm info for the project? That's what I was trying to figure out from @seldo on Twitter.

I just did npm info typescript for checking how they does, and it is indeeded stacking up whole 😅  I haven't feel this is concern (probably me didn't use npm info at all) - what's main issue if it happens?

@kwonoj what are we thinking about this PR at this point? It's high on my priority list to get nightlies published.

Just chatted with @kwonoj, and we're going to kill this one for now.


Fix example formatting and remove inline attribute

target_feature attributes work independently of inline attributes, and #[inline(always)] just forces LLVM to inline calls even in debug mode.
Also it would be great if the example would explain why all the functions are marked as unsafe.

I have confirmed the inline needs to be there.  What happens is if the generic form of the function does not get inlined into the function with the target_feature attribute, then it doesn't get the target_feature applied. So for instance the AVX2 intrinsics get downgraded by the compiler to SSE2 equivalents.
If you have doubts/questions let me know.

Interesting. How exactly did you confirm? With or without optimizations? LLVM should definitely inline the call as it's the only one for each specific instantiation of distance.

one way is just to yank it off, run a benchmark, and see it get ~5x slower with optimizations on full.
You could build up a test case in https://godbolt.org/  as well and see the assembler.
Now that I think about it the test I was doing was with a 'pub' function, maybe if it were private it would tend to inline it.

For now I'm going to merge this and put the inline back, but we can investigate further.


Issue with db-utils/cleanupDB function when actual foreign key constraints exists

I added some tables to the database and after inserting data in, the DB couldn't clean anymore given foreign key constraints.
This was weird since cleanupDb set PRAGMA foreight_keys = off in the transaction:
export async function cleanupDb(prisma: PrismaClient) {
  const tables = await prisma.$queryRaw<
    { name: string }[]
  >`SELECT name FROM sqlite_master WHERE type='table' AND name NOT LIKE 'sqlite_%' AND name NOT LIKE '_prisma_migrations';`

  await prisma.$transaction([
    // Disable FK constraints to avoid relation conflicts during deletion
    prisma.$executeRawUnsafe(`PRAGMA foreign_keys = OFF`),
    // Delete all rows from each table, preserving table structures
    ...tables.map(({ name }) =>
      prisma.$executeRawUnsafe(`DELETE from "${name}"`),
    ),
    prisma.$executeRawUnsafe(`PRAGMA foreign_keys = ON`),
  ])
}

The issue, according to chatGPT, is this:

The error occurs because the PRAGMA foreign_keys = OFF statement within the prisma.$transaction block does not persist across the individual prisma.$executeRawUnsafe statements. Each prisma.$executeRawUnsafe execution is a separate statement, and SQLite's PRAGMA commands do not affect the behavior of other statements outside of the immediate execution context.

Here’s an updated approach to ensure that the PRAGMA foreign_keys = OFF setting persists while deleting the rows:

Execute the PRAGMA foreign_keys = OFF and PRAGMA foreign_keys = ON statements outside the transaction to ensure they are applied properly.
Use a single transaction to delete the data from all tables.
Here's a revised version of your code:

const tables = await prisma.$queryRaw<
  { name: string }[]
>`SELECT name FROM sqlite_master WHERE type='table' AND name NOT LIKE 'sqlite_%' AND name NOT LIKE '_prisma_migrations';`

// Disable FK constraints to avoid relation conflicts during deletion
await prisma.$executeRawUnsafe(`PRAGMA foreign_keys = OFF`)

// Delete all rows from each table, preserving table structures
await prisma.$transaction([
  ...tables.map(({ name }) =>
    prisma.$executeRawUnsafe(`DELETE FROM "${name}"`),
  )
])

// Re-enable FK constraints
await prisma.$executeRawUnsafe(`PRAGMA foreign_keys = ON`)

I changed it locally, and the DB is cleaned correctly now, with pragma setting outside the transaction
I opened the issue because I didn't know if there was a specific reason for setting pragma inside the transaction and what implications it has on correctly cleaning, or what happens if the transaction fails. I suppose the transaction should be further wrapped in a try catch and setting foreign keys back on if transaction throws
If this is ok, I'm happy to open a PR with the change
Thank you

Interesting. I welcome a PR. Thank you!


Cannot use 0.7.2, 0.7.3 or 0.7.4-SNAPSHOT

I am unable to use latest versions of VisUI,
always getting error:
Could not resolve all dependencies for configuration ':compile'.

Could not resolve com.kotcrab.vis:vis-ui:0.7.4-SNAPSHOT.
Required by:
Could not parse POM https://oss.sonatype.org/content/repositories/snapshots/com/kotcrab/vis/vis-ui/0.7.4-SNAPSHOT/vis-ui-0.7.4-20150427.154831-2.pom
Could not find com.kotcrab.vis:vis-parent:0.0.2-SNAPSHOT.

And it seems others experienced similar issue.
is 0.0.2-SNAPSHOT in some other repo?

It's because I tried to simplify pom by moving some things to parent pom, but I'm not a Maven expert and expected that parent pom would be merged into VisUI pom but looks like it isn't...
I can't fix those versions, the workaround would be to clone this repo and execute mvn install (Maven required) in root or use those versions as jar dependencies.
I will fix this ASAP and deploy new release.
Sorry and thanks a lot for reporting this!

Thanks! I just downloaded the jar as temp workaround.

VisUI 0.7.4 and 0.7.5-SNAPSHOT should work now.


chore: add tslib to devDependencies

:tada: This PR is included in version 1.2.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Custom legend in result template

Addition of a custom legend and removal of Plotly's legend to fix the chart size and the overflow of the Plotly legend.
Plotly only allows to set the size of the plot container (plot + legend) and don't provide any method to choose the plot and the legend size seperatly. So the solution is to remove Plotly's legend and create our own. Without the Plotly's legend, we can choose the size for the plotly container which now means the size of the plot himself and also the size of the legend as is it our own.
Size issue and legend overflow issue can be visible here : Resnet

@Melvin-klein can we still click the legend to toggle the visibility of each curve?

@agramfort Yes and also double click. I kept all the behaviours

great !

Message ID: @.***>

Codecov Report

Merging #428 (730b95b) into main (ab964d0) will decrease coverage by 0.02%.
The diff coverage is n/a.

:exclamation: Current head 730b95b differs from pull request most recent head 2483bcf. Consider uploading reports for the commit 2483bcf to get more accurate results

@@            Coverage Diff             @@
##             main     #428      +/-   ##
==========================================
- Coverage   53.72%   53.70%   -0.03%
==========================================
  Files          44       44
  Lines        2710     2713       +3
  Branches      516      517       +1
==========================================
+ Hits         1456     1457       +1
- Misses       1144     1145       +1
- Partials      110      111       +1

@Melvin-klein you have a conflict. When merge I will test and merge. Thx


The type initializer for 'Mapster.TypeAdapter`2' threw an exception.

Hi
I am using Mapster 3.0.4 with DotNet Core 1.0. I am getting following intermittent error in production where the application has many user bases. I doubt Mapster is not considering thread safety while converting the object model.  Can you please help to solve this issue?
"System.TypeInitializationException: The type initializer for 'Mapster.TypeAdapter2' threw an exception. ---> System.InvalidOperationException: Collection was modified; enumeration operation may not execute.    at System.ThrowHelper.ThrowInvalidOperationException(ExceptionResource resource)    at System.Collections.Generic.Dictionary2.Enumerator.MoveNext()
at Mapster.SettingStore.Apply(SettingStore other)
at Mapster.TypeAdapterConfig.GetMergedSettings(TypeTuple tuple, MapType mapType)
at Mapster.TypeAdapterConfig.GetCompileArgument(TypeTuple tuple, MapType mapType, CompileContext context)
at Mapster.TypeAdapterConfig.CreateMapExpression(TypeTuple tuple, MapType mapType)
at Mapster.TypeAdapterConfig.b__55_0(TypeTuple tuple)
at Mapster.TypeAdapterConfig.AddToHash(Hashtable hash, TypeTuple key, Func2 func)    at Mapster.TypeAdapterConfig.GetMapFunction(Type sourceType, Type destinationType)    at Mapster.TypeAdapterConfig.GetMapFunction[TSource,TDestination]()    at Mapster.TypeAdapter2..cctor()
--- End of inner exception stack trace ---
at Mapster.TypeAdapter.Adapt[TSource,TDestination](TSource source)
Thanks

TypeAdapterConfig is not thread self. Please setup config on application start only.
If you really would like to keep config with mapping, pls use Fork to create new config (https://github.com/MapsterMapper/Mapster/wiki/Config-location#keep-together-with-mapping).


An issue about the Object.freeze()

When I performed a freeze operation on an initialized TypedArray, ChakraCore did not report an error, but other engines, such as SpiderMonkey and JavascriptCore, all reported errors.So I think there may be something wrong here.
version
chakra-1_11_22
command
ChakraCore/out/Debug/ch testcase.js

testcase
var NISLFuzzingFunc = function(){
    Object.freeze(new Int8Array(1));
}
NISLFuzzingFunc();

Output
No output.

Expected behavior
TypeError:cannot redefine non-configurable property 0.

Contributor : @Haobin-Lee

MDN has almost the same example: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/freeze
Yes, that should be a TypeError

I've had a quick dig here - the spec sets out a specific way of doing this that would throw with an typed array BUT the CC implementation is different - and doesn't have the ability to throw. To fix this could either implement the actual method per spec OR special case it to throw for non-empty typedarrays/dataviews.


Using nextra on Windows creates incorrect routes

In the loader.js, a fileRoute is calculated here:
https://github.com/shuding/nextra/blob/33987cfb5444e510efca0750a031cb13dc9c90ec/packages/nextra/src/loader.js#L34
On Windows, this route has backslashes in it, while the rest of the code expects forward slashes (e.g. active link is calculated by a match of the relative url.) This causes bugs like active state to be miscalculated.
The fix, I think, is to add a replace at the end of the computation:
      const fileRoute = path.join(route, removeExtension(f.name).replace(/^index$/, '')).replace(/\\/g, '/');

Maybe there's a better way, but this definitely resolves the issue. Want a PR?

I see this PR here fixing another related issue: https://github.com/shuding/nextra/pull/11/files
So I think this line becomes:
const fileRoute = slash(path.join(route, removeExtension(f.name).replace(/^index$/, '')));


Could I please have some guidance?

Sorry, I have successfully installed Chalet and initialized a Chalet project. What is the next step to accessing the SFML libraries? Please bear with me as I am completely new to C++ and SFML.

In theory you should be able to clone this repo, cd into the directory and run chalet build and it will pull down SFML for you. Everything that describes how it does this is the chalet.json There's a VS Code extension you can use to try it inside of VS code, and of course there is documentation available on the website.

Thank you so much for the direction, I will try this and get back to you! Is it possible you could add these instructions to the README? It was hard to infer all this from the current doc.


content overflow solved and CSS improved (Pincode Checker)

🛠 Issue (1580)

Closes #1580
Description
The input for pincode now remains inside the container and the CSS has been improved.
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] I have made this from my own
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] My changes generate no new warnings
[x] The title of my pull request is a short description of the requested changes.

ATTACH SCREEN-SHOTS / DEPLOYMENT LINK

@TusharKesarwani @zugzwang03 @harshit-paneri I have done the required changes, please merge this pr.


[Wait for #1583] [Test] Add bn layer training

[Pending commit: #1583]

[Test] Add bn layer training

Changes proposed in this PR:

Add batchnormalization layer test (for channel, width axis)

Self evaluation:

Build test: [X]Passed [ ]Failed [ ]Skipped
Run test: [X]Passed [ ]Failed [ ]Skipped

Signed-off-by: Jihoon Lee<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #1584. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnstreamer.mooo.com/.


DAT 7.1.9 & MS Surface Known Model Detection not working?

Seems this version doesn't find any known models for MS Surface devices for me. We have a Surface Laptop Studio (and previously a Laptop & Laptop GO which should probably still be detected).
Not sure if related, but the 'Identifiers' column also shows as blank for all the surface devices
(Selecting OS Win10 20H2 if it matters)

Were you able to get this going? Our surface for laptops are no longer imaging properly because the drivers aren't loading.

@ps959 i haven’t had a chance to do much troubleshooting with it. Only got the 1 SLS in use at the moment.

We have the same issue, not detecting any of our Microsoft models.
In the DriverAutomationTool log we have this entry, and I guess it could have something to do with it.
"- Required WMI class (MS_SYSTEMINFORMATION) is not being inventoried in Configuration Manager. Please refer to the documentation and extend the hardware classes being collected."

I am using DAT 7.2.2 and having this same issue.  image attached of the log output when I do a check for the drivers.  Windows 11 22H2.  Shows no results found.  Same with Windows 10.  With Windows 10 & 11 21H2 it finds 9 models for Windows 10 and 17 for Windows 11.  What am I doing wrong?  I looked at the json file that the DAT is pointing to, and even opened the link in a browser on my server, and it shows the model listed on 8 different entries.  Lost and need help please!

Ahh, it seems that the 22H2 build number is wrong in the json file.  It should be 22621.  Not sure why I didn't catch that before I posted.  Can someone go and edit this file please so this starts working?  Thank you!!!!


Reading encoded emojis in HTML attributes

I'm using jsoup to parse images that link to emoji images. These images have the actual emoji characters encoded in the alt attributes:

When I parse the attribute using jsoup, the resulting string is garbage:
    @Test
    void parseImageEmojiAttribute() {
        String html = "

";
        Document document = Jsoup.parse(html);
        Element img = document.select("img").get(0);
        assertEquals("\uD83D\uDCAF", img.attr("alt"));
    }

Is there a configuration setting that I'm missing which could help? Failing that, is there a way that I can get the raw value of the attribute so I can parse it myself? For instance, Apache commons text has a utility which can decode the value:
    @Test
    void parseHtmlEncodedEmoji() {
        String emoji = StringEscapeUtils.unescapeHtml4("��");
        assertEquals("\uD83D\uDCAF", emoji);
    }

Thanks for the clear report, fixed!
This was failing to decode and returning the replacement character due to an explicit range check it was hitting: (>= 0xD800 && <= 0xDFFF). That check has been there since https://github.com/jhy/jsoup/commit/8749726a79c22451b1f01b14fb2137f734e926b4 (12 years ago!) when I reimplemented to follow the HTML5 spec. But I can't see why that range was explicitly excluded - perhaps it was previously reserved in Unicode and then opened later.
The single-point version (💯) worked OK originally.
Have fixed by removing that range as it is now valid and not excluded in the current spec.
I note that Chrome seemingly treats this as we previously did; �� in Chrome renders as two replacement characters. The single point renders correctly.

(Commit was: 954c46a92a1a0c5052ed241d4398db8b0331e1f3)


Core: Erroneous exception message if the random switch weights sum is greater then 100%

The exception message is as follows:
Caused by: java.lang.IllegalArgumentException: requirement failed: Random switch weights sum is 1, mustn't be bigger than 100%
at scala.Predef$.require(Predef.scala:219)
The actual weights sum is 102% and not 1 (=100%), so I suspect that the number gets converted to 1,02 and then cut off its decimal places.

Thanks for reporting!


add introspection and command to generate report

This PR include new command and doc which is generated this command.

generate-reflection-report: generate reflection report as markdown format to doc/TOM-report.md.
doc/TOM-report.md is generated report. Same one is here on my repo.

This is not enhancement to Vim feature, this refrection command sometime useful for vim-mode developer to get overview of each TextObject, Operator, Motion.
This reflection parse Function.toString() to find instance variable assignment and super call.
Not 100% accurate(parsing JavaScript function written in CoffeScript), but useful.

Cool! The generic reflection part feels like it could even be a separate
NPM package.
Please add a date to the generated report, and vim-mode package version,
and if possible also current git commit ID, so it's easy to see if the
report is up to date.
Would it be possible/useful to output as the first part a subclass tree
rather than an unordered list of subclass relationships?

Please add a date to the generated report, and vim-mode package version,
and if possible also current git commit ID, so it's easy to see if the
report is up to date.

Will do, I'm not sure for git commit ID, will try.
Currently the generated file will written to under ~/github/vim-mode/docs, which will convenient to update docs without moving file.
But if we add time, version, and commit ID, we'd better to write generated file to temporary file.

Would it be possible/useful to output as the first part a subclass tree
rather than an unordered list of subclass relationships?

I couldn't understand above, how does it like? I want some example.

Now removed TOM-report.md itself from docs/ dir. since its now written under tmpdir.
If maintainer need to include report, he need to manually move under docs.
By the way, if this reflection utility be merged, I can add realtime opStack observation feature.
Its also helpful to new developer understand how vim-mode works whey they try to add new TOM.

Regarding hierarchy: currently, your output is

Input
OperatorError
Operator
OperatorWithInput < Operator
Select < Operator
Delete < Operator

and I think it would be useful to have it sorted alphabetically and nested by subclassing like this

Input
Operator

Delete
Increase

Decrease

Join
LowerCase
OperatorWithInput

Mark

Repeat

The more and more I'm looking at this, the more it looks like it could be an Atom package independent of vim-mode, which would take the current project's coffee files and run this type of introspection on their exports.
Also, instead of generating a file, how about opening a new text editor and putting the content there? Then the user can choose where to save it, if at all.

Its good idea to save non-named buiffer and let user choose where to save.
For orders hiararchy its possible but I don't have such motivation currently.
The independend Package idea is good, maybe me or other person introduce in future.
My motivation is to introduce opStack ovservation   feature on top of this introspection helper utility function  to help developer.
Its already very useful to understand where to be fixed while refactoring in my refactor ecoeriment. I can directly spot what class operator is operate on when some operator throw error.

Updated first comment to fit to current implementation.
Here is the update summary

Change command name generate-reflection-report to  generate-introspection-report.
Now table of content reflect inheritance hierarchy.
Most of code moved from vim-state.cofee to introspection.coffee.

This is a really cool technique, but I don't think this code belongs inside of vim-mode. Maybe it should be a separate npm module, like @jacekkopecky said. It could be an executable, for example, that you run with any given node.js code, like this:
$ generate-introspection-report ~/.atom/packages/vim-mode/lib/*.coffee

Your example seem that command is executed separate process to statically analyze coffee source.
But my code is for dynamically introspect within vim-mode.
The main purpose of this addition is to add osStack observation(=debugging) feature to vim-mode on top of this introspection function.
Here is the example output of opStack observation and explanation of how operation stack works.
How Operation Stack works(for current official vim-mode)
Its very useful to developer to adding or refactoring vim-mode.
Also this introspection report can be used to explain overall change between large commit by comparing to past report.
Here is example when I removed MotionWithInput intermediate class in my vim-mode folk.


SendEvent generates events twice

From SimControl, when we try to generate an event it sends successfully but twice not once.

Fixed in 0e52957


chore(optimize-ui): Improved UI for file explorer and copilot components

Enchance UI for file explorer and copilot components

Hey @priyakanabar-crest, This looks really good but have a few additions for this:

We need to be able to add items in subfolders still, we can probably accomplish this just by adding an "add item" option to the menu for folders
For opening/collapsing folders it would be good if we could just click on the title of the folder, similar to vs code
For opening the menu on an item or folder it would be good to allow for right click on that item to also open the menu
Dragging and dropping for moving items around to different folders would also be good


[python] Add zclwrite command for writing attributes

Problem

Missing zclwrite for writing attributes
Fixes #7563

Change overview
Add zclwrite command to python device controller
Testing

Run chip-all-cluster-app
Run ./src/controller/python/test/test_scripts/mobile-device-test.py -a <IP_ADDRESS> -t 45
The test script is included in cirque.

/rebase

@erjiaqing Conflict :(

@erjiaqing does it support writing optional attributes ?

/rebase

does it support writing optional attributes ?

I'd expect it to support writing all attributes that are enabled in the controller .zap file...


analytics: Improve do_increment_logging_stat performance.

Picking up where #29027 left off.
Fixes: #28947

I fixed the one typo that codespell flagged and marked this to merge once CI passes, thanks @alexmv and @Mahhheshh!


Webapp should decode contents of TRCs and certificates

The webapp currently shows TRCs and certificates in (unreadable) base64-encoded form. It would be nice if it could decode it to a human-readable form.

The "Trust" tab is now completely broken as the TRCs/certs are no longer in json format and the files have been moved. The webapp fails to load the certs and the page simply does not display anything.
The TRC and certificates are now in a binary format (ASN.1 for TRCs, x.509 (PEM) for the certificates) and can be decoded by invoking  scion-pki trcs human <path/to/*.trc>  and e.g. openssl x509 -in <path/to/*.pem> -text.
It's not clear to me what the purpose this "Trust" tab serves here. Even in "human readable form", the certificates are not really easy to digest. To me it would seem ok to simply remove this functionality.

It's not clear to me what the purpose this "Trust" tab serves here. Even in "human readable form", the certificates are not really easy to digest.

I think its purpose was to explicitly show how these certificates look to users exploring SCION to get a feeling how the control-plane PKI works.


⚠ Bofrost.at has degraded performance

In f00d97a, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1890 ms

Resolved: Bofrost.at performance has improved in 12153ac after 10 minutes.


latex issue in Mulliken question

I think those have been added by you @AdrianM0  - can you perhaps check if the json files are correct in this repo?

another one in another question

one more

those also might be caused by the app - but we should try to fix them

real exponentials might be a bit more beautiful

same here - not super important. If we can use math notation in the questions, it would be great. But it is also workable without

bigger problem here

I found one extra one in the dataset https://github.com/lamalab-org/chem-bench/blob/latex_issues/data/analytical_chemistry/25.json
Not in the human subset I thinl

probably one could also write some validation for that as it is parenthesis matching (which is an intro coding exercise) and then some regex for the different patterns we would expect

but, most importantly, thanks for giving it a look. In particular, for doing this so quickly!

In this question, is it meant creatinine instead of creanine?

I fixed them all including the creanine -> creatinine

In this one, the molecules on the left are displayed twice

In this one, the molecules on the left are displayed twice

yep (on it #510)


Wallet not showing recent transactions

Keybase GUI Version: 5.5.0-20200526131901+139bb348af
https://stellarchain.io/address/GCDI3NAN55MCYKW7USWFBHTRWT5JE62ZKLHX4GTR6CTTQTJ5XV22B5RQ shows
3 payments (1a2816428acba1ab6fb7c9a8bac0b9996b5ee47acb1be7d293d0dc854b3216e1, 5f725b443dcb7d38b765f4406f6132797de9b297ed446ee81a7daf0372c1b3da, and 7a1a626e149595c24acced6b66080f68c49b20692a7be61ecf91894335a7681b) that are not showing up in my Keybase wallet. I have tried closing and re-opening the program several times. I have also tried both the desktop and mobile client.

I too am seeing this issue. I can see payments on Stellarchain.io but not in my Keybase Client wallet page or on my mobile device.

Same here

Same, both mobile and desktop clients not showing certain transactions in the history, even though balance is correct.

Same, both mobile and desktop clients not showing certain transactions in the history, even though balance is correct.


Bug: merge does not merge ObjectLikeSequence

According to the docs:

ObjectLikeSequence.merge = function(others, mergeFn)
others	...Object|ObjectLikeSequence
The other object(s) or sequence(s) whose values will be merged into this one.

However,
var a = Lazy({kaas: {lekker: true}});
var b = Lazy({kaas: {gouds: true}});
a.merge(b).value();

Expected:
{
    kaas: {
        lekker: true,
        gouds: true
    }
}

Actual:
{
    kaas: {
        lekker: true
    },
    source: {
        kaas: {
            gouds: true
        }
    }
}
// This object also has all of Lazy.js ObjectLikeSequence functions attached.

Version: 0.4.2

I think this needs fixing in jazy.js:3958 but this code is way to magical for me to understand how to enumerate the lazily contained properties in stead of the javascript wrapper properties.
    for (prop in a) {
      merged[prop] = mergeObjects(a[prop], b[prop]);
    }
    for (prop in b) {
      if (!merged[prop]) {
        merged[prop] = b[prop];
      }
    }

@dtao I think this needs fixing in jazy.js:3958 but this code is way to magical for me to understand how to enumerate the lazily contained properties in stead of the javascript wrapper properties.
    for (prop in a) {
      merged[prop] = mergeObjects(a[prop], b[prop]);
    }
    for (prop in b) {
      if (!merged[prop]) {
        merged[prop] = b[prop];
      }
    }

I'm guessing something with a switch and b.get(prop) and b.each().

I agree that this is a bug in that it doesn't work as advertised. Unfortunately, looking at the merge code right now... yeah, seems like it might be pretty annoying to fix. I'll try to get to it, but probably not tonight.


fix: remove ironic allocation test from run

Ironic, internally, has a lightweight allocation engine, originally added for metalsmith usage ages ago. Turns out its unit tests can fail when running automated cleaning combined with default deployment interface which is not the fake driver. This was not detected upstream because only the fake drivers are executed together.
Needed for: https://github.com/openstack-k8s-operators/ironic-operator/pull/401
As a pull request owner and reviewers, I checked that:

[x]  Appropriate testing is done and actually running

@juliakreger thank you for adding the pull request. I am going to update the PR description for making check-main-comment job passing.

/approve


Fix Browsersync review app watch extension

Forgot to update Browsersync to watch *.mjs in https://github.com/alphagov/govuk-frontend/pull/3833

Cheers @romaricpascal. Maybe 🤷♂


Use shorter variable names

We might want to start using shorter variables, things like storage and server for ReplicatedStorage and ServerScriptService. We require a lot of modules and shorter names would be preferred.
Name Changes

replicatedStorage > storage
serverScripts > server
player > client (when inside of a LocalScript)

The player > client change has been implemented and will be pushed out soon, but the others were decided against.
server is a little too ambiguous since we also have ServerStorage and using server just for Scripts could get a little confusing. For the time being replicatedStorage is being left alone, but a shorter name is still desired. It'd be great if we could use shared but that references the _G table


Needs boilerplate

[x] collaborating.md

contributor agreement

[x] readme.md
[x] license (CC-BY 4.0 or something similar)

Resolved in f72667b


Español should start with capital E in language selector

Español should start with a capital C

it should because these are title-cased endonyms, and I made this argument when osu! changed their capitalization, but the names here aren't my opinion and I'm just copying them from osu.


⚠ Bofrost.be has degraded performance

In a9909d1, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 2759 ms

Resolved: Bofrost.be performance has improved in 87a6729.


Design: Improved Low visibility and contrast in sidebar

Hey, I just made a Pull Request!
Fixes: #2367

:heavy_check_mark: Checklist

[X] All tests are passing yarn test
[x] Screenshots attached (for UI changes)
[ ] Relevant documentation updated
[X] Prettier run on changed files
[ ] Tests added for new functionality
[ ] Regression tests added for bug fixes

Hey @iamrajiv ! Thanks. Screenshots in the PR would be very helpful. 💯

@OrkoHunter I have added the screenshots but I am not able to change the colour of subsection since I did not find the attribute for subsection in siteConfig.js. Can you help me with this?

I think you will have to use custom CSS to change the color for the subsection.
See at https://backstage.io/docs/ to find the correct class names for them. And then you can set the color from here https://github.com/spotify/backstage/blob/master/microsite/static/css/custom.css
Hope this helps. :)

@OrkoHunter Please take a look.

Thank you for guidance @OrkoHunter


Create parameter to set warning columns

I am building out a test suite with the following code
drift_suite = TestSuite(
            tests=[
                generate_column_tests(TestMeanInNSigmas, columns="num"),
                generate_column_tests(TestColumnShareOfMissingValues, columns="all"),
                generate_column_tests(TestShareOfOutListValues, columns="cat"),
               ]
)
drift_suite.run(
            reference_data=self.df_live_reference[live_features],
            current_data=self.df_live[live_features],
            column_mapping=cmap,
)

however certain column failures are more concerning than others. Is it possible to pass in a column parameter, where if a test fails for that particular column it appears as a warning instead of a fail? this would be useful to know if/when I need to take immediate action.

Hi @elutins,
This is a great feature request, and it is on the roadmap. (The design of the Test Suite output already has a spot for the "warnings"  in addition to "failed" tests).
Unfortunately, I cannot confirm the exact timeline of when it will be released yet.
In the meantime, the best way to address this is to create two or several different Test Suites grouping the "critical" or "less critical" checks in different suites and manage the alert/warning workflow externally.

Hi @elutins,
We did release this update in v0.4.2.
By default, all Tests will return a Fail if the Test condition is not fulfilled. If you want to get a Warning instead, use the is_critical parameter and set it to False. Example:
data_integrity_column_tests = TestSuite(tests=[
    TestColumnAllConstantValues(column_name='education', is_critical=False),
    TestColumnAllUniqueValues(column_name='education', is_critical=False),
])

Let me know how it works for you!


Create LICENSE

I added the LICENSE file, it will add the license details on the top of the github page making it easier for other developers to check how they can use the library.

Hello,
considering that the library is not maintained and I actively use it, I have decided to fork it for the time being under the same name. Changes to naming and other practices will come in the future.
In the mean time, I have merged your PR and appreciate your contribution.
I hope we can revive this project together.
https://github.com/mario/chatkit
Cheers,
Mario

Thank you, already added


review LinearProbingHash's delete method

Looks like there's a better approach to deletion: https://github.com/kevin-wayne/algs4/blob/master/src/main/java/edu/princeton/cs/algs4/LinearProbingHashST.java#L190

Indeed, there was a bug in my implementation for keys being deleted within the same cluster.
I've added a unit test for that and fixed the issue.


Any plans for localisation?

I'm sure the JP speaking (and KR / CN) would find this project very useful too.
As a suggestion, a crowd sourced localisation integration like crowdin may be fit for the project.

We talked about this a bit on Discord, but to clarify how much do you think needs to be localized initially? Would translations of the FAQ and things like the text on the matchup page might be a good first step, without needing to figure out how to dynamically swap the text for menus?


fix: still sort when search value is absent

fix #100

What: Sort when search value is absent.

Why: Consistency.

How: Don't early escape if search value is absent.

Checklist:

[ ] Documentation "N/A"
[x] Tests
[x] Ready to be merged

[x] Added myself to contributors table

:tada: This PR is included in version 4.2.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[hotfix][docs] Fix wrong API example in dev/stream/sources doc

What is the purpose of the change
Hotfix for dev/stream/sources doc.
Brief change log
Hotfix for dev/stream/sources doc.
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

CC @StephanEwen

Sorry about the noise, I was looking at a slightly older version of 1.11, this has been changed in FLINK-18428


introduce core-types

Does this look like the right idea?

It sure looks like the right idea to me 👍


Unable To Fetch Contacts

Goals
Unable to Fetch Contacts when we click on Contact Option in Chat Window.
Expected Results
Need to see the contact which i have already added as part of previous view controller
Actual Results
Not able to see the contact
Steps to Reproduce

Code Sample
//
//  StartChatViewController.swift
//  Skillz
//
//  Created by Badrinath on 6/3/17.
//  Copyright © 2017 Badrinath. All rights reserved.
//
import Foundation
import UIKit
import Applozic
class StartChatViewController: UIViewController{
@IBOutlet var logoutButton: UIButton!

@IBAction func logoutAction(_ sender: Any) {
   /* let registerUserClientService: ALRegisterUserClientService = ALRegisterUserClientService()
    registerUserClientService.logout { (response, error) in

    }
    self.dismiss(animated: false, completion: nil)*/
}

@IBAction func launchChatAction(_ sender: Any) {
    let chatManager : ALChatManager = ALChatManager(applicationKey: Utils.MESSAGING_API_KEY as NSString)

    chatManager.registerUserAndLaunchChat(getUserDetail(), fromController: self, forUser:nil)
}

override func viewDidLoad() {
}

func addContact(){

    let contact: ALContact = ALContact()
    contact.userId = "sp1"
    contact.fullName = "service Provider 1"
    contact.displayName = "sp1"

    let contactService: ALContactService = ALContactService();
    contactService.add(contact)

    print(contactService.getOverallUnreadCountForContact())

}

func getUserDetail() -> ALUser {

    let user: ALUser = ALUser()

    user.userId = userData
    user.password = "1"
    user.displayName = userData
    user.applicationId = ALChatManager.applicationId
    user.email = userName!

    print("User Details \(user.userId) \(user.password) \(user.displayName) \(user.applicationId) \(user.email)")

    addContact()

    return user;
}

}
//addContact method tries to add a contact to contact service and should list in contacts table view.
Below are the error logs screenshot

Any help would be greatly appreciated , as we are looking to scale this application.
Applozic SDK version: ? 3.8
Xcode version: ? 8.2.1
iOS version: ? 9.0

I'm having the same issue. Any resolutions? @mukeshthawani

@MEnnabah  If you are getting the same error then you need to check if registration was successful or not. Share full logs at<EMAIL_ADDRESS>we will look into it.


Appending to RichTextLabel.text restores any cleared text

Godot version
v4.0.3.stable.official [5222a99f5]
System information
Windows 10 - Godot 4.0.3
Issue description
Calling RichTextLabel.clear() and then appending to its text field restores all of the cleared text.
This seems related to #54951, but this issue has nothing to do with bbcode_text field -- it occurs simply by writing text and calling the clear function.
This bug can be trivially worked around by calling RichTextLabel.text = "" in addition to RichTextLabel.clear(). However this is nonsensical and contradicts the documentation, which explicitly states that the clear() function "Clears the tag stack and sets text to an empty string"
Steps to reproduce

Click the "Add Text" button. A line of text is added to the RichTextLabel.
Click the "Clear" button. The RichTextLabel is cleared.
Click the "Add Text" button. The cleared lines are restored, and additional text is added beneath them.

Minimal reproduction project
RichTextLabel-clear.zip

Clears the tag stack and sets text to an empty string

Documentation is wrong, clear is cleaning tag stack, but do not affect text. It's intended to be used in conjunction with push_*/pop methods, not with text.

This bug can be trivially worked around by calling RichTextLabel.text = "" in addition to RichTextLabel.clear().

Setting text will call clear automatically, there's no need to call both.