ZAPD should use sizeof

Currently ZAPD will extract asset files like this:
Gfx sOtyukaPlatformBottomDL[] = {
    gsSPVertex(&sOtyukaPlatformBottomVtx[0], 4, 0),
    gsSP2Triangles(0, 2, 1, 0, 0, 3, 2, 0),
    gsSPEndDisplayList(),
};

Assets that are currently in the repo have things like this:
 Gfx sPlatformBottomDList[] = {
    gsSPVertex(sPlatformBottomVerts, ARRAY_COUNT(sPlatformBottomVerts), 0),
    gsSP2Triangles(0, 2, 1, 0, 0, 3, 2, 0),
    gsSPEndDisplayList(),
};

Another example of this
CollisionHeader sOtyukaCollision = {
    { -60, -60, -60 },
    { 60, 0, 60 },
    8,
    sOtyukaCollision_vtx_00002540,
    10,
    sOtyukaCollision_polygons_000024A0,
    sOtyukaCollision_surfaceType_00002490,
    sOtyukaCollision_camDataList_00002488,
    0,
    NULL
};

Is being extract instead of:
static CollisionHeader sColHeader = {
    { -60, -60, -60 }, { 60, 0, 60 },    ARRAY_COUNT(sVtxList), sVtxList, ARRAY_COUNT(sPolyList),
    sPolyList,         sSurfaceTypeList, sCameraDataList,       0,        NULL,
};

I think for the vertex buffers it makes more sense to not use sizeof / array length since it's quite common to load sub-arrays of the full vertex array into the rsp's vertex buffer

agreed, i think it straight up just wont work in many scenarios

I think that's how libgfxd outputs dlists. I don't know if that library allows to change that behaviour.

Alright so maybe not for anything GFX related but it should be ok to use for collision right? Or maybe animations of there are any hard codes sizes in there

#278


Custom Noteskins Addition :)

What feature do you want to get added on the base engine?
Like The Bob And Bosip Mod, Can Each Character Have A Different Noteskin?
You Could Give Them All The Same Noteskin, Or You Could Make Them All Seperate Ones :)
To test your sight, and reliability, please select the option of what should NOT be requested.
Stage Editor, 6K+ support, and winning icons.

This is already possible with lua. (Change texture property.)

This is already possible with lua. (Change texture property.)

Can You Send The Link To It?


getWalletTransaction gagal

Responnya begini mas
error.OVOUnexpectedError: OVOHttpResponse(code=None, status=404, message='Data Not Found!', content=None, data=None, httpStatus=404)
Barangkali sudah ganti url api nya ya?
Mohon bantuannya kalau ada update lagi.
Terimakasih banyak.

Is your issue already fixed?

Yes, it's already fixed. The error occured when there is no transaction history. Somehow, OVO deleted them if older than 30 days, which is weird. Thank you for this amazing repo.


Chat Format Issue

Description
I can't make the group prefix appear before the name or after in the game chat I tried everything if you need a picture tell me what and I will send , Pastebin link in GitHub bellow
plugins: PlaceholderAPI v2.11.6, CMI v<IP_ADDRESS> , Enabling CMILib v<IP_ADDRESS>, Vault-1.7.4.jar
Reproduction Steps
download the server version , install plugins and string to set them up
Expected Behaviour
Add a prefix in-game on the chat with the colours and the prefix I set
Server Details
Server Type : Mohist 1.19.2 (mods and plugins), Java(<IP_ADDRESS>) 61.0
LuckPerms Version
LuckPerms-Bukkit-5.4.139.jar
Logs and Configs
https://gist.github.com/Gafel98/d167613064846cf147c7852d572ce20b
Extra Details
No response

No idea what plugin's config you have shared, but I can tell its not the LuckPerms config. LuckPerms is not responsible for formatting your chat. You should seek support for how to configure your chat plugin from them.


Public Release

Coverage decreased (-0.03%) to 95.128% when pulling 8f15c5fd13c908c372a1733b079a5720fa5a2665 on develop into d9d28bd07bcca0d28e6481fcef8a6cf1b53f9fec on master.


scripts: redirect stdout to ctx.log.warn

Redirect messages written to stdout in scripts to ctx.log.warn.
(closes #1530)

This looks great, thanks. Could you please add a test?

Thanks! Will do.
There is a small issue, it seems like print is calling sys.stdout.write more than once to print a newline, resulting in empty lines in the log. Should I change it to not print empty lines?

Yes, that sounds about right. Thanks!


Updates needed to get OpenBLAS to work as a SciPy subproject

Submitted upstream in https://github.com/mesonbuild/wrapdb/pull/1815.


Camera jumps the first time it's moved after opening a project

I did some debugging on this. I might be wrong but it seems like camera matrix and controller target are not properly set in the project till first camera update via mouse. I managed to fix this. But now, we don't get same results in BSDF test scenes i.e. camera is pointing to the empty space. But I think this is consistent with the camera parameters in the project file.

Hey, thanks for looking into this!!

It seems like camera matrix and controller target are not properly set in the project till first camera update via mouse.

That's well possible, yes.

But now, we don't get same results in BSDF test scenes i.e. camera is pointing to the empty space

That sounds like a bug. If the render shows something, that means that the camera is set properly, and the camera controller should be set accordingly.
Did you try other scenes from the test suite?

This is getting interesting:)
Just rotated the camera a little bit and than saved the scene. Newly saved scene works fine. I checked the project files and the only difference is the camera matrices.

Did you try other scenes from the test suite?

Yes, same thing happens in the autofocus scene too.

the only difference is the camera matrices

How different are the matrices? Can you copy/paste them here?
Isn't there also a difference in that the initial scene has no controller pivot point, while the newly saved scene has one?

Original matrix for the autofocus scene:
0.000000000000000 0.000000000000000 -1.000000000000000 0.000000000000000
0.000000000000000 1.000000000000000 0.000000000000000 0.000000000000000
1.000000000000000 0.000000000000000 0.000000000000000 0.000000000000000
0.000000000000000 0.000000000000000 0.000000000000000 1.000000000000000
Matrix after moving the camera a little bit:
0.020990486104180 0.136938778876766 -0.990357092332281 0.001843854808597
-0.000000000000000 0.990575340373520 0.136968956497031 0.011070143145411
0.999779675475107 -0.002875044978055 0.020792657917254 0.033553467009628
0.000000000000000 0.000000000000000 0.000000000000000 1.000000000000000

Isn't there also a difference in that the initial scene has no controller pivot point, while the newly saved scene has one?

No. I diffed the files. They both have the same controller_target values. Only difference is the matrices.
I will investigate this further. If you have any suggestions, I appreciate it=)

Fixed.


How are you testing your components in Lumira Designer?

Now that we can't connect to local data sources how do you add test data to your components?

Just upload a LUMX file containing some offline data and some apps or composites that contain your components.


vvp error "compiled_fifo: unable to open input file"

Hello! After generating the compiled_fifo manually using iverilog, I begin to use vvp to generate '.vcd' file. But it throws an error called 'compiled_fifo: unable to open input file'，however it could work when I 'vvp compiled_xor2' , I have tried to use command chmod to change the permission of the file. It does not work. How do I solve this problem.

me too. Do you solve that problem?


Doubts about incremental pretraining

Hello! Thank you for your great work!

I want to train model over Japanese office documents, should I merge my domain data with other Japanese general data for incremental pretraining step?
For the SFT stage how I don't have any domain level instructions, can I only use general data sources ?

Thank you in advance!

yes
if only use general data, you get a general chat model, not domain model.


Make some assertions more conservative

Make the REPL raise errors properly instead of just printing locally so loading files
with mistakes causes an unsuccessful termination
Fix errors on some of our demos due to the fix above
Fix the chain meta command so it persists commitments with the right secret
Assert that the output of the padded frame is the same as the one from the original last frame

The env variable wasn't necessary because loading already throws errors. I just needed to actually throw the errors instead of printing them locally.
Also, added a test case asserting an expected failure.


Update css import and demo file names

Alaska Airlines Pull Request
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Resolves: #54
Summary:
Please summarize the scope of the changes you have submitted, what the intent of the work is and anything that describes the before/after state of the project.

Update how css is exported from the component
Update demo file names to index.md and api.md

Type of change:
Please delete options that are not relevant.

[ ] New capability
[x] Revision of an existing capability
[ ] Infrastructure change (automation, etc.)
[ ] Other (please elaborate)

Checklist:

[x] My update follows the CONTRIBUTING guidelines of this project
[x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Investigate this scratch that broke the site

Load it into a local instance and see if the same happens. If not, we'll have to test again on the live site during off hours
obj_loop_stopwatchman.zip

Hi!
I was able to succesfully reproduce this on a local setup; creating the scratch and then attempting to do anything with it hangs the site.
It looks like IDO 5.3 is hanging when given this scratch as an input, even outside of the site.
Some weedwhacking later, a minimized snippet that exhibits the same behaviour:
repro.c:
typedef unsigned short int u16;
typedef unsigned int u32;
typedef signed char s8;
typedef signed short int s16;
typedef signed int s32;
typedef float f32;

struct TempStruct8 {
 f32 unk0;
 f32 unk4;
 f32 unk8;
 f32 unkC;
 s8 unk10;
};

typedef struct Object {
 f32 y_position;
} Object;

void obj_loop_stopwatchman(Object *obj, s32 updateRate) {
    s32 index;
    struct TempStruct8 **sp48[1];
    void *racer;
    void *header;

     if(index != 0) {
        struct TempStruct8 ** temp = sp48[-3];
        index--;
        while(index >= 0) {
            if ((temp[index]->unk10 != 11) && (temp[index]->unk10 != 14) && (temp[index]->unk8 > 0.0)) {
                obj->y_position = temp[index]->unk0;
            }
            index--;
        }
    }
}

to compile (slash hang indefinitely):
backend/compilers/ido5.3/cc -c -Xcpluscomm -G0 -non_shared -Wab,-r4300_mul -woff 649,838,712 -32 -O2 -mips1 -o repro.o repro.c
[for what it's worth: when Ctrl-C'ing the hanging IDO prompt, it dies with the message:
Fatal error in: /usr/lib/uopt  child died due to signal 2.]

Thanks @ConorBobbleHat! Super interesting. I guess it'd be useful to know if this happens with the latest ido recomp and if it happens in the original ido compiler with qemu-irix. And yeah Alex we do have timeouts on sandbox stuff, but it's probably too high

Some other folks did some testing, and this happens on the original ido under qemu irix as well. It also seems to be extremely specific. Only index -3 into sp48 causes the issue. I think we should put a more explicit limit on compiler invocations, rather than just the one in the nsjail. Alternatively, we reduce the nsjail timeout from 30s to something more like 3s.

Would also be nice if users were limited to only a single compilation at a time, with newer ones killing older ones. ("Newer" being defined according to timestamps sent by the client, so unlucky network conditions don't result in a newer request getting dropped.) Don't know if our sandboxing library allows cancellations in a simple way.

Closing since the root cause has been investigated: ido bad
wrote two spinoff issues that could help with similar situations in the future


build(webpack): update webpack packages

Description:
webpack-serve and webpack-command have been depreciated. Migrate to webpack-cli and webpack-dev-server.
Motivation and Context:
Keep devops setup inline with community supported standards.
How Has This Been Tested?
Manually test build jobs. Manually test app in dev and prod mode.
Types of changes:
Devtools updates.
Checklist:

[ ] My code follows the code style of this project.
[ ] I have reviewed and updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes where needed.
[ ] All new and existing tests passed.
[ ] My commits have been squashed into a concise set of changes.

Coverage decreased (-0.2%) to 16.16% when pulling a82e585e7f6fb5acf6530f45487fcc733439a5d3 on mrfelton:chore/webpack-dev-server into 19c1c85a6ba848dfb69cf2e930194dbf257a9318 on LN-Zap:master.

Coverage decreased (-0.2%) to 16.16% when pulling a82e585e7f6fb5acf6530f45487fcc733439a5d3 on mrfelton:chore/webpack-dev-server into 19c1c85a6ba848dfb69cf2e930194dbf257a9318 on LN-Zap:master.


Fix sorting issues/Progress on CRUD ops/Bug fixes

This pull request includes the following changes:

Fix sorting issues on backend

Add ability to add students to rosters manually

Add ability to delete students from rosters and the student db

Several bug fixes

Bump build version

Reluctantly merging


updated the os codenames upto android Q

Updated the os code names upto Android Q.

Looks good to me. Thank you for your contribution :)


wlr_allocator_autocreate

Implements https://github.com/swaywm/wlroots/issues/2861

Can we import the doc-comments from the original issue https://github.com/swaywm/wlroots/issues/2861?

Also needs a rebase :)


runtime: map deletion doesn't work correctly

package main

func main() {
	m := make(map[string]int)
	m["fourty-two"] = 42
	m["six"] = 6
	println(m["fourty-two"])
	println(m["six"])
	delete(m, "fourty-two")
	v, ok := m["fourty-two"]
	println(v, ok)
	println(m["six"])
}

: xgene:tmp; map.arm
42
6
0 false
6
: xgene:tmp; map.arm64
42
6
0 false
0
: xgene:tmp;

I believe this has been silently fixed in latest big.runtime branch.


Add psptoolchain-extra dispatch

Right now this is missing. I'm not sure if this would require us to still set some variables in the github runner settings or if they are already set.

I don’t have grants in this repo to setup the keys

That's a bother, me neither 😬

I'll convert this to a draft for now until we have someone who can set this up.


unable install on Mac M1

I am reopening this because the solution given by others did not resolve my situtation
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for manimpango
Failed to build manimpango
ERROR: Could not build wheels for manimpango, which is required to install pyproject.toml-based projects

I had a setup failure with the same error message. In the text, it also said fatal error: 'cairo.h' file not found.
What helped me was installing cairo.h in the following way:
arch -arm64 brew install pkg-config cairo

same issue here

nice,this command worked

I had a setup failure with the same error message. In the text, it also said fatal error: 'cairo.h' file not found.
What helped me was installing cairo.h in the following way:
arch -arm64 brew install pkg-config cairo


Add watchfiles as dependency

The watchfiles dependency used in server.py is missing from requirements.
Since the changes 5 days ago, with a clean install, you get the following error:
$ sphinx-autobuild
Traceback (most recent call last):
  File "/.../sphinx-autobuild", line 5, in <module>
    from sphinx_autobuild.__main__ import main
  File "/.../sphinx_autobuild/__main__.py", line 22, in <module>
    from sphinx_autobuild.server import RebuildServer
  File "/.../sphinx_autobuild/server.py", line 8, in <module>
    import watchfiles
ModuleNotFoundError: No module named 'watchfiles'

After installing watchfiles the project runs successfully. This PR adds the package as a dependency in pyproject.toml.

@AA-Turner @pradyunsg Please could we have a bugfix release?
Otherwise we'll need to either pin to the old version or add watchfiles as a temporary dependency to CPython docs (plus backports) and the devguide and PEPs.
Thank you!

@AA-Turner clicked the relevant buttons and made it happen. :)

Confirmed working now, thanks all!


[HOLD for payment 2024-10-14] Tracking: Remove VisionCamera CameraSession on Fabricpatch once the library was fully migrated to New Arch

Description
There is a bug in react-native-vision-camera where the cameraSession isn't properly deinitialized/recycled on Fabric under RN New Architecture.
Since we currently already have a patch file to make RNVC compatible with React Native v0.75, we cannot directly apply this change upstream. We should also wait to fix this until the library has fully been migrated to the New Architecture.
cc @mountiny

I believe we can close this one as the payment will be handled as part of the native stack pr

@mountiny didn't we create this issue to track whether this got fixed upstream? This is not yet fixed in VIsionCamera

Whoops you are right, thank you for the ping, I skimmed over this and havent realized.

@chrispader how is this looking?

I will try to add this to react-native-vision-camera this week! Shouldn't be a big change

@hannojg just to confirm, have you tried working on something similar and it showed to be a lot of work?

@mountiny yes, will discuss with Chris internally first and then get back to you! Thanks for bringing this up

@mountiny so i just had a quick call with @hannojg about this change and our path forward with VisionCamera.
Hanno already explained in this thread why we won't migrate react-native-vision-camera to RN New Arch. Essentially we will be migrating the library to Nitro modules soon and the changes needed for new arch support are just too complex and unnecessary.
Therefore, we also won't be able to add the changes from the patch discussed in this PR to the library. This is because of two reasons:

This patch (cameraSession fix under New Arch) is based on another patch that we have in E/App, which adds/migrates some of the VisionCamera legacy view components to Fabric components
In the upstream library we don't have any Fabric related code in VisionCamera atm, so we also cannot add the changes from this patch (prepareForRecycle)

Since we are in the process of migrating the library to Nitro modules, it would be beneficial to update to a Nitro-enabled version soon.
@hannojg created an issue for tracking the update of react-native-vision-camera to a newer version in https://github.com/Expensify/App/issues/50650
We can also keep track of the CameraSession fix over there and make sure this works with Nitro. We should therefore keep the current patch as-is and remove it once we migrated to Nitro.
@mountiny does that sound good to you?

Sounds great, thanks!


(Logic) Boomerang can be used to defeat Gorons

As I learned from https://youtu.be/34LxoI1WuPE&t=4874.
Given that it's not in the logic already (for glitched or glitchless) I'd assume it's kinda niche?

Yeah I'd consider that to be difficult/niche combat.


removing extensions not needed anymore

This PR addresses issue #636 by removing

firstIndex(where: )
firstIndex(of:)
lastIndex(where: )
lastIndex(of:)

and their related tests.
They should be removed since they are now (since swift 4.2) part of the Swift Standard Library.
See: SE-0204
Checklist

[ x ] I checked the Contributing Guidelines before creating this request.
[ x ] I have added a changelog entry describing my changes.

          4 Messages

:book:
Thank you for submitting a pull request to SwifterSwift. The team will review your submission as soon as possible.

:book:
iOS: Executed 536 tests, with 0 failures (0 unexpected) in 17.990 (20.474) seconds

:book:
tvOS: Executed 502 tests, with 0 failures (0 unexpected) in 9.967 (12.146) seconds

:book:
macOS: Executed 366 tests, with 0 failures (0 unexpected) in 1.562 (2.084) seconds

  Generated by :no_entry_sign: Danger

The build fails but I wasn't able to understand why🤔

@marcocapano it looks like Travis stalled, I restarted the build.

@marcocapano it looks like Travis stalled, I restarted the build.

@guykogus I had already restarted it and still failed, I’m not sure this will help☹
Sent with GitHawk


Concatenate obsm

Adds obsm concatenation in adata.concatenate.

@Koncopd @falexwolf
There is an issue with the obsm concatenation. When we run sc.tl.diffmap with different anndata objects, concatenate them and run sc.pp.neighbors, we get the following exception. The reason is that  obsms are concatenated but .uns['diffmap_evals'] are not available.
---------------------------------------------------------------------------
KeyError                                  Traceback (most recent call last)
<timed exec> in <module>

/opt/conda/lib/python3.7/site-packages/scanpy/neighbors/__init__.py in neighbors(adata, n_neighbors, n_pcs, use_rep, knn, random_state, method, metric, metric_kwds, copy)
    104     if adata.isview:  # we shouldn't need this here...
    105         adata._init_as_actual(adata.copy())
--> 106     neighbors = Neighbors(adata)
    107     neighbors.compute_neighbors(
    108         n_neighbors=n_neighbors, knn=knn, n_pcs=n_pcs, use_rep=use_rep,

/opt/conda/lib/python3.7/site-packages/scanpy/neighbors/__init__.py in __init__(self, adata, n_dcs)
    527                 self._number_connected_components = self._connected_components[0]
    528         if 'X_diffmap' in adata.obsm_keys():
--> 529             self._eigen_values = _backwards_compat_get_full_eval(adata)
    530             self._eigen_basis = _backwards_compat_get_full_X_diffmap(adata)
    531             if n_dcs is not None:

/opt/conda/lib/python3.7/site-packages/scanpy/neighbors/__init__.py in _backwards_compat_get_full_eval(adata)
    395         return np.r_[1, adata.uns['diffmap_evals']]
    396     else:
--> 397         return adata.uns['diffmap_evals']
    398
    399

KeyError: 'diffmap_evals'

Doesn't it make more sense to make obsm concatenation False by default, by the way? Should concatenating obsm be the default behaviour?


Can't deal with supabase?

Describe the bug
At first, the app has stored data locally in the browser. Then I noticed that and asked to use a database, the AI suggested Supabase, which I validated. Then the AI seems to be unable to change that and to fix the issues around that. I have this kind of errors for most of my entities.
Now, I am stuck, have used most of my credits, and I'm not sure the solution can be a good fit for my project if we can have dead ends like that.
I think that from start, it should ask what kind of data storage we want because I thought I finished my app and then noticed that with another browser it didn't work and now I'm stuck. So much time lost.
Let me know if you think there is a solution to get rid of that error without spending millions of tokens again?
For the rest, you app is very very promising, congrats.
Thanks
"❌ Error:"{message: "invalid input syntax for type uuid: "1"", code: "22P02", details: Object, hint: Object}
at debugSupabase (/src/lib/supabase.ts?t=1732048904159:15:15)
at async fetchUserActivities (/src/store/activitiesStore.ts?t=1732048924122:14:22)
2
"Erreur lors de la récupération des activités:"{code: "22P02", details: Object, hint: Object, message: "invalid input syntax for type uuid: "1""}
at fetchUserActivities (/src/store/activitiesStore.ts?t=173204892
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-tekwn9
Steps to reproduce
just run the app
Expected behavior
Identify the error
Screen Recording / Screenshot

Platform
Browser name = Chrome
Full version = <IP_ADDRESS>
Major version = 131
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 104287552,
  "usedJSHeapSize": 100376116,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Username = romainboyer
Chat ID = 0f8998782709

Additional context

Sorry to hear this but glad you are liking Bolt overall! You could initially try pasting the error message into the Bolt chat to see if it is able to resolve the issue. However, if Bolt is repeatedly unable to resolve this error, manual intervention is required to prevent excessive token usage.
Unfortunately we don't have the resources to deal with individual programming problems. Next steps for developing your project are further described here: #2310. In this case, you may need to consult the official Supabase documentation. The Bolt Help Center  contains a number of resources on using Bolt most effectively, including tutorials on setting up Supabase. Hope this helps!


Running on single file

I've managed to get the example running through run.sh.
Could you provide an example or description of how I would run diarization on a wav file of my own? I'm struggling to figure out how to do this.
Thank you

there are examples, try to look at them


Have modal not take up entire viewable screen: QUESTION

Looking to use this but constrained within a limited part of the screen rather than the entire viewable screen, perhaps this is an oxymoron of using a modal?
I've given the modal specific sizing but it ignores it and still takes up the entire UI.

I am having the same problem as well!

Hi!
Yes, you can use it as a full screen component, you just need to override the modal's margin by applying a style with margin: 0 to the style prop of the modal.
Example:
const style =  StyleSheet.create({
  modal: {
    backgroundColor: 'white',
    margin: 0, // This is the important style you need to set
    alignItems: undefined,
    justifyContent: undefined,
  }

...

<Modal isVisible={true} style={styles.modal}>
  <View style={{ flex: 1 }}>
    <Text>Hello!</Text>
 </View>
</Modal>

let me know if it works for you :)

@mmazzarolo it's working fullscreen, but we want the contrary, we want the modal to be like a windowed screen, like a second window above the first one, just like in the example images the wiki have.
margin: 0 does not change that, the margin only affects the content inside the modal.

@Leminur can't you do:
  modal: {
    backgroundColor: 'white',
    margin: 15, /
    alignItems: undefined,
    justifyContent: undefined,
  }

Sorry! It something else that got me there:
backdropColor = {'white'}
backdropOpacity = {1}
I should have paid attention to that, thanks anyway!

Honestly the issue you were having is still unclear to me 🤔
Glad you fixed it though, feel free to post here again if you're still in trouble on the matter.

Is there a way to limit the scope of backdrop? As of now, it is occupying 100% of the screen, is it possible to make it like 90%?

No idea why this is so difficult to just say the modal should take up x% of the height of the screen.  It should be built into React Native.  A common use case would be for a toast notification that appears above modals.

Is there a way to limit the scope of backdrop? As of now, it is occupying 100% of the screen, is it possible to make it like 90%?

Not possible right now. If you're interested it might be done by editing the backdrop style here. What's the use case though?
A modal should always be drawn on top of all the content, otherwise it won't be a modal.

No idea why this is so difficult to just say the modal should take up x% of the height of the screen. It should be built into React Native. A common use case would be for a toast notification that appears above modals.

See message above.
Currently react-native doesn't allow using multiple modals/dialog at the same time 😞
Even if it is a known bug and not a feature it is (in my opinion) a good side effects since having multiple modals and dialog is a bad UX (again, in my opinion), especially on mobile.

@mmazzarolo I agree and thanks for the response, backdrop restyling is a good workaround. A use case might be rare, as I wanted to access bottom tabs to control Modal content without hiding it. Anyway thanks for the response!

@cauldyclark15 I am working on an app where I want 2 buttons to still be clickable over the backdrop, just like you wanted access to your bottom tabs. Did you find a workaround for this? I've tried to manually set the height of the backdrop, but it doesn't seem to be working for me.

@krestaino yes, I created a submenu using TouchableWithoutFeedback with an empty Text as a child and computed height. Whenever this is tapped, it will be closed like a backdrop.
{showSubmenu && (
    <TouchableWithoutFeedback
        onPressIn={this._onCloseSubmenu}
        onPress={this._onCloseSubmenu}
     >
       <View
          style={{
            height: deviceHeight - 60 - (deviceHeight * submenuHeight) / 100,
            width: deviceWidth,
            backgroundColor: 'transparent',
            position: 'absolute',
            left: 0,
            top: 0,
            }}
            >
              <Text> </Text>
       </View>
     </TouchableWithoutFeedback>
 )}

Hi!
Yes, you can use it as a full screen component, you just need to override the modal's margin by applying a style with margin: 0 to the style prop of the modal.
Example:
const styles =  StyleSheet.create({
  modal: {
    backgroundColor: 'white',
    margin: 0, // This is the important style you need to set
    alignItems: undefined,
    justifyContent: undefined,
  }

...

<Modal isVisible={true} style={styles.modal}>
  <View style={{ flex: 1 }}>
    <Text>Hello!</Text>
 </View>
</Modal>

let me know if it works for you :)

Dude! He is not asking to make modal appear as a full screen, that's actually the thing troubling him.

@Leminur can't you do:
 <Modal isVisible={this.state.visibleModal === 1} style={styles.modal}>
  {this._renderModalContent()}
 </Modal>

  modal: {
    backgroundColor: 'white',
    margin: 15,
    alignItems: undefined,
    justifyContent: undefined,
  }

How did you do it bro?

@BenjErgizerBunny your example also works fine with thereact-native original Modal component, thanks 👍

The only way I was abble to use the modal on screen and set a dim background for the components bellow was as follow:
`<Modal
animationType="fade"
transparent={true}
visible={templateModalVisible}
onRequestClose={() => {
this.setTemplateModalVisible(!templateModalVisible);
}}>

Hello World!
          <TouchableHighlight
            onPress={() => {
              this.setTemplateModalVisible(!templateModalVisible);
            }}>
            <Text>Hide Modal</Text>
          </TouchableHighlight>
        </View>
      </View>
    </Modal>

TemplateModalContainer:{
flex: 1,
backgroundColor: 'rgba(0, 0, 0, 0.5)',
justifyContent: 'center',
alignItems: 'center',
},
TemplateModalContent:{
width: '80%',
height: '70%',
backgroundColor: 'white',
justifyContent: 'center',
alignItems: 'center',
borderRadius: 4,
},
`

The only way I made it work was by using a View inside a View inside the modal:
`        <Modal
animationType="fade"
transparent={true}
visible={templateModalVisible}
onRequestClose={() => {
this.setTemplateModalVisible(!templateModalVisible);
}}>

Hello World!
          <TouchableHighlight
            onPress={() => {
              this.setTemplateModalVisible(!templateModalVisible);
            }}>
            <Text>Hide Modal</Text>
          </TouchableHighlight>
        </View>
      </View>
    </Modal>`

  TemplateModalContainer:{     flex: 1,     backgroundColor: 'rgba(0, 0, 0, 0.5)',     justifyContent: 'center',     alignItems: 'center',   },   TemplateModalContent:{     width: '80%',     height: '70%',     backgroundColor: colors.grayScale0,     justifyContent: 'center',     alignItems: 'center',     borderRadius: 4,   },

Hi!
Yes, you can use it as a full screen component, you just need to override the modal's margin by applying a style with margin: 0 to the style prop of the modal.
Example:
const styles =  StyleSheet.create({
  modal: {
    backgroundColor: 'white',
    margin: 0, // This is the important style you need to set
    alignItems: undefined,
    justifyContent: undefined,
  }

...

<Modal isVisible={true} style={styles.modal}>
  <View style={{ flex: 1 }}>
    <Text>Hello!</Text>
 </View>
</Modal>

let me know if it works for you :)

Work Perfectly for me

Sorry! It something else that got me there:
backdropColor = {'white'}
backdropOpacity = {1}
I should have paid attention to that, thanks anyway!

Thanks for this.

just add margin: 0 to your modal style

Latest version has 'coverScreen' prop, which you can set to false.

Latest version has 'coverScreen' prop, which you can set to false.

0.61.5? Or 0.62 release candidate?

Latest version has 'coverScreen' prop, which you can set to false.
coverScreen prop worked for me

Yes, just add margin: 0 to modal style
          <Modal
          style={{margin: 0}} //<----------
          >

               <View style={{ height:"80%", borderTopStartRadius: 10, borderTopEndRadius: 10, backgroundColor:"white",
                  width:"100%",marginTop:300,flex: 1 }}>
               ...
              </View>
          </Modal>

I fixed that issue by adding below code
<Modal             backdropColor={'transparent'}             style={{ margin: 0, backgroundColor: 'rgba(0,0,0,.6)' }}         >

I fixed that issue by adding below code
<Modal             backdropColor={'transparent'}             style={{ margin: 0, backgroundColor: 'rgba(0,0,0,.6)' }}         >

Guys, if its for android ... you can use the code:  statusBarTranslucent={true} in Modal.
Example:

I left here an example that works well. You must wrap the code inside the Modal component with a View and then set margin. If you wanna a set an opacity background you must use another View component and set his background color using RGBA's transparency in order to avoid use opacity that will make opaque all inside it (even your Modal's pop-up).

import React, { useState } from 'react';
import { Text, View, StyleSheet, Button, Modal } from 'react-native';

export default function App() {

    const [modalVisible, setModalVisible] = useState(false);

    return (
        <View style={styles.container}>

            <Modal
                transparent={true}
                visible={modalVisible}
                onRequestClose={() => setModalVisible(true)}
            >
              <View  style={{ backgroundColor: 'rgba(0,0,0,0.4)', flex:1}}>
                    <View style={{ backgroundColor: 'orange', padding: 40, margin: 80}}>
                        <Text>This is a modal</Text>
                        <Button title='close'
                            onPress={() => setModalVisible(false)} />
                    </View>

                </View>
            </Modal>

            <Button
                title="Press me"
                onPress={() =>setModalVisible(true)}
            />

        </View>
    );
}

const styles = StyleSheet.create({
    container: {
        backgroundColor: 'rgb(25, 90, 90)',
        flex: 1,
    }
});

Hi!
Yes, you can use it as a full screen component, you just need to override the modal's margin by applying a style with margin: 0 to the style prop of the modal.
Example:
const styles =  StyleSheet.create({
  modal: {
    backgroundColor: 'white',
    margin: 0, // This is the important style you need to set
    alignItems: undefined,
    justifyContent: undefined,
  }

...

<Modal isVisible={true} style={styles.modal}>
  <View style={{ flex: 1 }}>
    <Text>Hello!</Text>
 </View>
</Modal>

let me know if it works for you :)

Dude! He is not asking to make modal appear as a full screen, that's actually the thing troubling him. Please don't write anything just to increase your role in the discussions here

Hi!
Yes, you can use it as a full screen component, you just need to override the modal's margin by applying a style with margin: 0 to the style prop of the modal.
Example:
const styles =  StyleSheet.create({
  modal: {
    backgroundColor: 'white',
    margin: 0, // This is the important style you need to set
    alignItems: undefined,
    justifyContent: undefined,
  }

...

<Modal isVisible={true} style={styles.modal}>
  <View style={{ flex: 1 }}>
    <Text>Hello!</Text>
 </View>
</Modal>

let me know if it works for you :)

Dude! He is not asking to make modal appear as a full screen, that's actually the thing troubling him. Please don't write anything just to increase your role in the discussions here

Its working thank you

The modal is not covering the entire screen
The modal style applied by default has a small margin.
If you want the modal to cover the entire screen you can easily override it this way:
<Modal style={{ margin: 0 }}>...</Modal>

For those looking at this thread in current time (2024), this worked for me:
import Modal from "react-native-modal";
....
modalContent: {
    height: 100,
    backgroundColor: "white",
    padding: 22,
    justifyContent: "center",
    alignItems: "center",
    borderRadius: 4,
    borderColor: "rgba(0, 0, 0, 0.1)"
}
....
const [isVisible, setIsVisible] = useState(false);
....
<Modal style={{ backgroundColor: 'transparent'}} isVisible={isVisible}>
    <View style={styles.modalContent}>
        <Text>Modal text.</Text>
        <Pressable onPress={() => { setIsVisible(false) }}>
            <Text>Ok</Text>
        </Pressable>
    </View>
</Modal>

Modal that Fills a Percentage of the Parent's Height
The use case for this is to create a modal that doesn't cover the entire screen, a design pattern commonly seen in apps like Uber Eats and Airbnb.
Requirements

The React Native Modal component must have the transparent prop set to true (reference: https://reactnative.dev/docs/modal#transparent)
A child view within the Modal must have its top value set to a number representing the desired distance from the top of the screen.

Example
In this example, the height is set to 100% so that the modal behaves like a bottom sheet with no gap between itself and the bottom of the screen. To illustrate this behavior, you can change the height to a smaller value like 40%, and you'll see the modal disconnected from the bottom of the screen.
import { Modal, Text, View } from 'react-native'

export const MyModal = (props) => {

    return (
        <Modal visible={true} animationType="slide" transparent={true}>
            <View
                style={[
                    {
                        height: '100%',
                        top: 100
                    },
                ]}
            >
                <Text>content</Text>
            </View>
        </Modal>
    )
}


Addresses critical issue in repeater documentation

sources:
http://www.nytix.com/GuidedTours/TVLocationTours/Seinfeld/
https://mapsaboutnothing.com/2013/05/14/costanza-house/
Could not find documented Manhattan address for George, so including the Costanza family home in Queens.

@jeremysklarsky 👍  haha I'm sure @shuwen will appreciate this (it was his handiwork to begin with)

incredible 👍

@shuwen
...is that...a Jerry emoji?!?!


"Treat empty strings as nil in expr" potentially harmful

https://github.com/istio/mixer/pull/825 is potentially harmful. It leads to surprising results for expressions that end in | "". Instead of "", such an expression evals to nil.
Example:
originUID: origin.uid | "" -> nil (when origin.uid attribute is not present)

Follow-up: Removing | " from these expressions in the config leads to unexpected behavior when the attributes aren't present:
Config:
...
  - kind: attributes
    params:
      input_expressions:
        sourceUID: source.uid
        targetUID: target.uid
        originUID: origin.uid
...

Result:
E0727 12:42:12.457917   88696 attrgenmgr.go:91] Could not evaluate input expressions for attribute generation.3 errors occurred:

* failed to construct value for label 'originUID': unresolved attribute origin.uid
* failed to construct value for label 'sourceUID': unresolved attribute source.uid
* failed to construct value for label 'targetUID': unresolved attribute target.uid

So, for now, we need to leave the | "" but know that that really means the value will be nil (and not "") when evaluated in the absence of the *.uid attribute.

Is originUID: origin.uid | " "  a workaround?
Note the single space instead of empty string.

I don't think that we want to pass in " " instead of the empty string. That could lead to a bunch of code that has to Trim and the check len > 0, etc.

The "|" operator now returns "" when LHS is an attribute and the attribute is not present.

Closing per Oz.


WebJobs deployed to a staging slot should not run by default.

Due to the lack of ability to specify Websites settings that do not get copied into "swapped" slots, when WebJobs are deployed to a deployment slot, they should be disabled by default, so they don't accidentally process jobs meant for the Production slot.

Sticky settings have the unfortunate side effect of causing the web app to restart after a slot swap process, thereby defeating the main purpose of deployment slots in my opinion. It would be nice if there was a setting that could be set on the slot configuration which enabled/disabled webjobs without affecting the slot swap process.


fix(biblio): do not load org mode eagerly.

Due to unconditional loading configuration for citar-org package, org is also being loaded eagerly.
Especially, causes a warning message from doom, like
‘org’ was already loaded by the time lang/org loaded, this may cause issues

Should also resolve #5811

Don't you still have to check the completion module in the when?

Don't you still have to check the completion module in the when?

In theory, no need to add conditional clause for the completion engine. However, aesthetically agrees with your opinion it would be better to check based on the completion module explicitly.

@bdarcus Think it does not have to do with current PR, but I wonder what is the variable citar-org-note-include for. Maybe we should replace that with citar-file-note-org-include?

Summing up, will the following be the right thing to do?
(use-package! citar-org
  :defer t
  :when (and (featurep! :completion vertico)
             (featurep! :lang org +roam2))
  :config
  ;; Include property drawer metadata for 'org-roam' v2.
  (setq citar-file-note-org-include '(org-id org-roam-ref)))

Summing up, will the following be the right thing to do?

I believe so.
Except, I'm now realizing citar-file-note-org-include doesn't really make sense given it's in citar-org. But I'll take a closer look at that separately.

I've merged this now to fix the immediate problem. Don't worry about the extra :completion vertico check (I'm already working on a refactor that will add it). In any case, thanks for your help!


Cleanup of code

Naming of get_udi_event to trigger schedule
Spelling
Small formatting issues
Remove unused (logging) code

Changes already incorporated in other PRs.


AI tools Interactors no polygon output

Are the AI tool interactors disabled on the demo site? Having trouble using DEXTR specifically, after marking points no polygon is generated in any case. This issue is on the demo site and my install for me.

@jonathancaevans
Thanks for the report. Looks like something is wrong also with FBRS interactor.
We will investigate.

@bsekachev
in cvat/apps/lambda_manager/views.py
class LambdaFunction:
    ...
    def invoke(self, db_task, data):
        ...
        response = self.gateway.invoke(self, payload)
        response_filtered = []
        ...
        if self.kind == LambdaType.DETECTOR:
            ...
            response_filtered.append(item)

        return response_filtered

In this case, if it is not a detector, [ ] is returned.

@hyunchan123 , thanks for the investigation. It looks like it is a regression after recent changes in the area. Will you be able to help us and send a PR?

@nmanovic
If I understand correctly, it is expected that DEXTR does not work in the latest version of CVAT? Because I think I have the same problem: Dextr seems to return a 200 response, but this is always an empty list.
Do you have any indication of how it will take for the fix to be released? Can I expect this to be today/tomorrow, or will this take more time. In that case I might have to downgrade.

FYI, to make the fix work until it is released, I think one has to run (as stated in https://openvinotoolkit.github.io/cvat/docs/administration/basics/installation/)
docker-compose -f docker-compose.yml -f docker-compose.dev.yml build

FYI, to make the fix work until it is released, I think one has to run (as stated in https://openvinotoolkit.github.io/cvat/docs/administration/basics/installation/)
docker-compose -f docker-compose.yml -f docker-compose.dev.yml build

Thanks! It took me some time to figure this out, but just a few hours ago I indeed found that I needed to rebuild from local source code using -f docker-compose.dev.yml 😅
I can confirm that DEXTR works again after applying this fix.

I found that I also needed to set up auto annotation as shown here. After registering with nuclio I got DEXTR and YOLO to work, and I presume it would be similar for other auto-annotation models.

Hi all, I'm still seeing this issue with f-BRS - even after following above steps.
I can confirm that I even see an output from the call to the f-BRS function in browser, but no polygon is created.


Add option to reduce star size

On small screen the stars size takes two row
please add option to control the star size thanks

We also need option to center the text title
and 'message' parameters should be optional


annotation support

Add Annotation .
Add annotation interface to Layer .
Add few tests.

Sorry I made wrong PR on this repo. Please ignore this.

@xcokazaki Do you plan to reopen this / make another PR with annotation support? In principle that's a useful feature, I think. I haven't looked at annotations in plotly yet, but it's something that I'll need soon anyway.

@Vindaar Yes, I can reopen this. I just wanted to achieve annotated_heatmap feature. As I'm not so familiar with nim(actually I'm a newbie), what should I do for this PR? Should I add any examples for this feature?

I agree, this looks useful. An example would be nice, but the tests are great!

OK, then I'll reopen this PR. I think I need tiny modifications on this. When it's ready, please review the codes.

Now it's ready to review.


Remove multidex dependency

The multidex artifact was added as a dependency of every androidx.media3 library module in this commit (889f435), which I understand was to simplify the configuration for the demo apps. This adds an unnecessary transitive dependency on the multidex artifact for apps that do not require it however.

Thanks for reporting! This dependency was actually meant to be androidTestImplementation and not implementation, so that it gets automatically included in all instrumentation test builds.

You can also manually exclude this dependency for now by using
implementation('androidx.media3:media3-exoplayer:1.1.0') {
  exclude group: 'androidx.multidex', module: 'multidex'
}


Added "Difference in WordPress types"

Difference between WordPress.org and WordPress.com

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[ ] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

This is taken directly from the wordpress website. Please try again and use your own words to describe it instead of plagiarizing.


K8s: Create reference docs for all configurable custom resources

We need comprehensive reference docs and an example yaml for all of the configurable custom resources for the Operator.
All configurable custom resources can be found in the custom resource definition (https://github.com/cockroachdb/cockroach-operator/blob/master/config/crd/bases/crdb.cockroachlabs.com_crdbclusters.yaml). It's hard to navigate. Also, it contains descriptions for each of the fields.
--
Some of the custom resources that need some docs support are:

cache (it's important that we point users to our production guidelines on cache)
image (pull policy, pull secret)
dataStore (we're removing support for emptyDir)
maxSQLMemory (similar to cache, we have existing guidance)
resources (related to production guidelines as well)
tlsEnable (to be removed, all clusters will be secure by default - Make Secure Mode the Default #153)
status (probably not relevant, confirm with engineering)
all of the ports (grpcPort, HTTPport, the 3rd port for SQL traffic)

@udnay Is this yaml used to set the properties of the custom resource fields on the back end, or is it strictly a piece of internal documentation?


Discuss a @most/test package

@nikoskalogridis has been working on a @most/test package.  Thank you!
I'd like to use this as a place to discuss the design.  Although the core team has discussed it a lot, we've not yet found the time to implement anything.  So, I'd like to use this as a place to discuss your design.  I think getting on the same page will help us review code more effectively later.

I'm primarily interested in the API and ergonomics.  @nikoskalogridis could you show some examples of your current direction?  Thanks!

My initial goal was to expose the helper functions inside the @most/core in order to be usable for testing outside of the @most/core package.
I think its a great idea to discuss the API and ergonomics. It would help if you have a reference of those discussions previously held in order to be up to date as well with the rest of the core members

you can have a look at #231 typescript typing file to get an idea of what the api is going to be up to now. Since its the first time that I write typescript please let me know if there are errors. Also helping out with flow (mainly of the way it should be structured) is really appreciated.
Anyway if you think this direction is totally wrong let me know. I was hopping to finish a first beta version during the weekend as I will not have that much time during the next week. But you are right lets discuss this first then put the effort.

Great, thanks @nikoskalogridis.  No problem and TS and Flow, we can def help.
One overarching thing I'm thinking currently is that since testEnv and all the associated stuff has evolved over quite a long period of time (it started over in cujojs/most), taking a fresh look at what we'd want a simplest-possible test API to look like would be good.
For example, if we have a solid virtual timer, then it's quite simple to construct test streams with at() + merge(), or at() + continueWith().  I could imagine an incredibly simple API foundation being just collectEventsFor!  Starting small initially might be a good way to get people using it so we can learn about testing use cases outside of mostjs/core.
Thoughts?

I agree that @most/test should be minimal and intuitive.
As I see it, it needs to provide:

Mocked stream creation functions (ie. atTimes, makeEventsFromArray, makeEvents, etc)
an API for running the source stream up specific points in virtual time and collect the result events timestamped (ie. collectEventsFor)
Assertion utility functions for testing the events returned after running the stream (and by those I mean timed event collection assertion functions)

for the first we can expose the atTimes, makeEventsFromArray and makeEvents and for the second part we have collectEventsFor.
so one could write a test as follows:
describe('Adder', () => {
  it('should add 1 on each value of the source stream', () => {
    const source = map(x => x + 1, makeEventsFromArray(1, [1, 2, 3, 4]))
    const expected = [
      {time: 0, value: 2},
      {time: 1, value: 3},
      {time: 2, value: 4},
      {time: 3, value: 5}
    ]
    return collectEventsFor(4, source).then(eq(expected))
  })
})

which is great!
One issue that I run to and puzzled me at first is that if I write:
collectEventsFor(2, source)

the promise is never going to be resolved. As the stream has not ended and in the code we have this:
const collectEvents = curry2(function (stream, scheduler) {
  const into = []
  const s = tap((x) => into.push({time: currentTime(scheduler), value: x}), stream)
  return runEffects(s, scheduler).then(() => into)
})

I think we should make it resolve with the events collected up to dt = 2.
also regarding the mocked stream utilities I think we should also provide an interface for creating mocked stream from an Iterator returning {time: x, value: y} values (do we have a type for this?)

one idea for collectEventsFor is to rename it to collectEvents and provide a chained method of building execution. ie
collectEvents
  .from(source)
  .fromTime(4)
  .upToTime(6)
  .then(...)

or something like
collectEvents(
  fromTime(4),
  toTime(6),
  from(source)
).then(...)

regarding the collectEventsFor not resolving this is a sideffect of the VirtualTimer progressing correctly to specific time requested. So this can be handled as follows:
const collectEventsFor = curry2((nticks, stream) =>
  new Promise(function (resolve, reject) {
    const collectedEvents = []
    const scheduler = ticks(nticks + 1)
    const addEvent = function (value) {
      const time = currentTime(scheduler)
      if (time <= nticks) {
        collectedEvents.push({time, value})
      } else {
        resolve(collectedEvents)
      }
    }
    const s = tap(addEvent, stream)
    runEffects(s, scheduler)
      .then(() => resolve(collectedEvents))
      .catch(reject)
  })
)

actually progressing the timer to nticks + 1

I would appreciate your help regarding types in flow and more specifically for creating a type for the collectEventsFor.
I have created the following:
export type TimeStampedEvent<A> = {
  time: Time,
  value: A
}

export type TimeStampedEvents<A> = Array<TimeStampedEvent<A>>

export const collectEventsFor =
  curry2(<A>(nticks: Time, stream: Stream<A>): Promise<TimeStampedEvents<A>> =>
    new Promise(function (resolve, reject) {
      const collectedEvents: TimeStampedEvents<A> = []
      run(
        {
          event: function (time, value) {
            if (time > nticks) {
              resolve(collectedEvents)
              return
            }
            collectedEvents.push({time, value})
          },
          end: () => resolve(collectedEvents),
          error: reject
        },
        newScheduler(newVirtualTimer().tick(nticks + 1), newTimeline()),
        stream
      )
    })
  )

the above works but how could I assign the following signatures (which are not accepted by Flow) to this function
interface collectEventsForFn<Time, Stream<A>> {
  (): collectEventsForFn<Time, Stream<A>>,
  (Time): (Stream<A>) => Promise<TimeStampedEvents<A>>,
  (Time, Stream<A>): Promise<TimeStampedEvents<A>>
}

I have made some progress with this. Pushed a version using flow for the whole @most/test codebase. If you don't like it I can strip types from the source files.
You can get an overview of the API on the d.ts file. One thing I could not accomplish (with flow or Typescript) is to produce curried versions of the exposed functions yet retaining the signature information of the functions. If anyone could suggest a way please let me know.

@nikoskalogridis
Arity2 example in TypeScript:
interface CurriedAddFn {
    (x: number, y: number): number
    (x: number): (y: number) => number
}

Perhaps @briancavalier can show how to do it in Flow.

@nikoskalogridis Sorry I haven't been able to give any more feedback here yet.  I'm splitting my time between several things and trying to keep up.  I will make time over the weekend to catch up on the discussion and review #231 so that I can comment.

curried versions of the exposed functions
Perhaps @briancavalier can show how to do it in Flow.

Here are the generic curried function types from prelude:
https://github.com/mostjs/core/blob/master/packages/prelude/src/index.js.flow#L37
And here's how we tend to write separate flow defs for curried functions:
https://github.com/mostjs/core/blob/master/packages/core/src/index.js.flow#L9-L10
Do those help, or are you looking for something different?

@briancavalier thanks, I understand the way of exposing those functions with the correct signatures at the package level. I was trying to find a way to export those functions curried at the module level and be able to retain their signatures instead of the CurriedFunction2<any, any> between the internal modules.
Anyway I don't think flow and Typescript supports this.
I have updated the code to expose the correct signatures for both Typescript and Flow and expose the functions curried and with the correct signatures on the package level.

+1 for a @most/test package. I'm currently trying to test bindings to @most/core I wrote for fp-ts, and I'm finding myself just copying & tweaking code from the test helpers in the src, because they aren't exposed anywhere.

Just wondering is this proposal abandoned?

There seems to be a compelling case for such a package. Which requirements do you have, @joshburgess ?

I am also interested in this package! has the proposal been dropped?


Use workspace dependencies.

Makes dependency version handling easier. Relates in some way to https://github.com/tokio-rs/prost/pull/957
Depends on #1033 (merged into master and rebased here)

What problem does this solve? Dependabot will change all uses of a dependency when there is an update, right?

I am not interested in workspace dependencies. I feel like Dependabot already makes dependency management easy. I am open to having my mind changed.


doc: switching primary to secondary domains for organization change

update
https://github.com/GoogleCloudPlatform/pbmm-on-gcp-onboarding/blob/main/docs/google-cloud-onboarding.md
reference:  a customer that registered mydomain.com but wants to switch to dev.mydomain.com

20240406: Closing issue during retrofit/rebase of this TEF V1 based/modified repo to TEF V4 standards
This issue may participate in the LZ refactor after rebase
Query on all issues related to the older V1 version via the tag
https://github.com/GoogleCloudPlatform/pbmm-on-gcp-onboarding/labels/2024-pre-tef-v4


Add margins

[x] Above and below separators
[x] Above the Submit answers button

[x] Separators should have margins above and below them
[ ] Increase distance betwen the form and There are ... questions ... block on the start page


Enable remoteParticipantTransactionSuccessTest

Purpose
Fix intermittent test failure with remoteParticipantTransactionSuccessTest
Check List

[x] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Temporary fix with https://github.com/ballerina-platform/ballerina-lang/pull/18545


Added colcon-mixin to the source colcon repos

I went through the build from source instructions trying to setup the mixin verb, but that repo was missing from the given list.

Thanks for the patch.
Reviewing the list another repo seems to be missing. Can you please add an entry for colcon-zsh at the end? Thanks.

PTAL, should be good.

Thanks for the patch.


Watch should take into account any theme, not just casper.

At the moment grunt dev only watches the casper theme. If we add other themes to our dev environment they aren't watched, which isn't ideal. I think we should include a wildcard so that all themes are watched.

I'm pretty on the fence with this, it seems to me like it's mixing together two quite different things.
grunt dev is for watching all of Ghost when you're working on the code base. Casper is included because it's an essential part of Ghost core.
Theme developers don't have any need to use the Ghost source code or to run any grunt commands for Ghost. In fact the grunt commands for Ghost only work if you install from git and manually build the source files, which I wouldn't recommend for theme developers. Making grunt dev work for any theme implies that's how we think you should be working, which isn't the case.
Instead I'd imagine that theme devs would have their own build commands for their themes, which can also do the watching?
Rather than hijacking grunt dev for this usecase, I think it would be more sensible to add theme-development specific tools to Ghost which don't require you to use the source code.
I'd be interested to hear what other theme developers think. Maybe it's worth putting that as a suggestion on the wishlist?

@ErisDS I do see your point. But, Casper is it's own project and I assume the devs are "highjacking" grunt dev, otherwise the watch on the theme wouldn't exist.
If you want the separation of concerns then perhaps Casper should have the development specific tools in it's own repo, and the theme watch could be removed from Ghost.
From my perspective, it is very handy to add my theme as a new submodule alongside Casper, and run grunt dev. But, that workflow requires this commit.
Also, if Ghost decided to also include Roon by default, I would want grunt dev to work as well.
If using grunt dev for this case doesn't seem appropriate for my own theme, I would argue that it is also not appropriate for the Casper theme. And that would be a perfectly acceptable approach too. But, I would not agree that it should work for Casper, while not working for other themes.

I assume the devs are "highjacking" grunt dev, otherwise the watch on the theme wouldn't exist

No, you've completely missed my point.
Casper is watched as part of grunt dev because it is required in order to develop Ghost. If a developer is working on a shiny new theme feature, they need to edit a theme as well as write the core code in order to test the functionality. Casper is already there in the project because it's the default, so that's the theme we assume core devs will use.
I maintain that grunt dev is a core development tool, not a theme development tool and that this PR crosses those purposes. You shouldn't be rebuilding the ghost admin every time you make a change to your theme. I have no opposition to the creation of new tools, but that needs more consideration.

grunt dev is a core development tool, not a theme development tool and that this PR crosses those purposes.

Agreed, not right for core


Accessory type and battery status

Hey,
with the original plugin.. I could display the Roomba as a ventilator rather than a simple switch.
I liked it, so I can distinguish it from other devices.
This has also the benefit, that the Home-App will show the battery status and if it's charging.

Hey there @m-ruhl,
Not sure what you mean by displaying it as a "ventilator". Do you mean a fan? If so you can change it in the home app.
You can also currently view the battery, and charging status in the home app, if you 3D Touch on the switch two times. (It's inconvenient I know, I am working on a fix).

Thanks for the quick reply..
Oh, yes I meant fan ;-)
This is the screenshot with the homebridge-roomba-stv plugin

As you can see.. I can change the device with "Display as" and see the battery status..
With your plugin I don't have that.. I think its exposed as another device type..

If you click on Accessories, then the switch, 3D Touch on it, and you can view in there. It's a limitation due to the sensors, but as I said, I am working to separate them.

Ah sorry now I get it..
This is the parent with 2 child accessories ^^


unitest still with base58

The unit tests still uses the base58 encoding, they should be ported to base32.

Fixed as part of #62


go/types (go vet): go vet fails with illegal cycle for github.com/yuin/gopher-lua

To reproduce:
go get github.com/yuin/gopher-lua
cd $GOPATH/src/github.com/yuin/gopher-lua/
go vet

reports
$ go vet
# github.com/yuin/gopher-lua
./alloc.go:14:7: illegal cycle in declaration of preloadLimit
./alloc.go:14:7: 	preloadLimit refers to
./config.go:14:6: 	LNumber refers to
./value.go:139:19: 	assertFunction refers to
./value.go:177:6: 	LFunction refers to
./value.go:184:6: 	LGFunction refers to
./value.go:203:6: 	LState refers to
./state.go:209:6: 	registry refers to
./alloc.go:20:6: 	allocator refers to
./alloc.go:14:7: 	preloadLimit
vet: typecheck failures

Definitively a type-checker failure. The new cycle detection code is overly aggressive.

Independent reproducer:
$ cat x.go
package p

const preloadLimit LNumber = 128

type LNumber float64

func (LNumber) assertFunction() *LFunction

type LFunction struct {
	GFunction LGFunction
}

type LGFunction func(*LState)

type LState struct {
	reg *registry
}

type registry struct {
	alloc *allocator
}

type allocator struct {
	_ [int(preloadLimit)]int
}

Running gotype in it yields:
$ gotype x.go
x.go:3:7: illegal cycle in declaration of preloadLimit
x.go:3:7: 	preloadLimit refers to
x.go:5:6: 	LNumber refers to
x.go:7:16: 	assertFunction refers to
x.go:9:6: 	LFunction refers to
x.go:13:6: 	LGFunction refers to
x.go:15:6: 	LState refers to
x.go:19:6: 	registry refers to
x.go:23:6: 	allocator refers to
x.go:3:7: 	preloadLimit

This is awfully wrong. Will fix in the next few days.

A trivial fix is to set
const useCycleMarking = false

in go/types/decl.go:57. This will disable the new code and the bug disappears (but it will also undo some other fixes, and the test suite will need to disable some tests).

Shorter (go/types says C -> T -> M -> C):
package p
const C T = 1
type T int
func (T) M() [C]T

It seems to me that the "C -> T" link is spurious. For cycle detection it seems like a constant shouldn't care about its own type or initializer, so this should be cycle-free too:
package p
const C = T(1)
type T int
func (T) M() [C]T

But maybe I am missing some subtlety around constants. It's been a while.

@rsc I'm using elsewhere a slightly different algorithm that breaks this cycle after C->T. The difference is in that methods are typechecked separately, after non-methods.
Snippet of actual code
        cs := &cstack{p: p}
	for _, sf := range p.SourceFiles {
		for _, d := range sf.TopLevelDecls {
			if x, ok := d.(*MethodDecl); ok {
				cs.reset().check(x, nil)
			}
		}
	}
	for _, sf := range p.SourceFiles {
		for _, d := range sf.TopLevelDecls {
			if _, ok := d.(*MethodDecl); !ok {
				cs.reset().check(d, nil)
			}
		}
	}
	p.checkEnqueued(cs)
	for _, sf := range p.SourceFiles {
		for _, d := range sf.InitFunctions {
			d.(*FuncDecl).checkBody(cs)
		}
	}
	p.checkEnqueued(cs)
	for _, sf := range p.SourceFiles {
		for _, d := range sf.TopLevelDecls {
			switch x := d.(type) {
			case *FuncDecl:
				x.checkBody(cs)
			case *MethodDecl:
				x.checkBody(cs)
			}
		}
	}
	p.checkEnqueued(cs)

For cycle detection it seems like a constant shouldn't care about its own type or initializer,

I think that would not be correct.

@cznic Thanks for this. We can't completely change the algorithm at this point but I agree that methods should be handled separately. There's an independent/related issue open for that (#23203).

The CL https://go-review.googlesource.com/c/go/+/121757 fixes this issue. Running go/vet on the repo now produces:
$ go vet
# github.com/yuin/gopher-lua
./channellib.go:49: reflect.SelectCase composite literal uses unkeyed fields
./compile.go:1051: unreachable code
./compile.go:1052: unreachable code
./compile.go:1111: unreachable code
./state.go:1142: unreachable code
./utils.go:260: reflect.SliceHeader composite literal uses unkeyed fields
./vm.go:777: self-assignment of cf.ReturnBase to cf.ReturnBase
./vm.go:779: self-assignment of cf.NRet to cf.NRet
./vm.go:1229: unreachable code
./script_test.go:57: result of (*lua.FunctionProto).String call not used
./state_test.go:244: unreachable code
./state_test.go:262: unreachable code

all of which look correct to me.


Add validation to controller for Pipeline CRD

Expected Behavior
When someone creates a Pipeline in a k8s cluster (e.g. with kubectl apply, the controller should make sure every field is valid.
This should include verifying as many fields as possible, e.g. verifying connectivity with any endpoints, if there are any references, verifying that those actually exist in the system, etc.
Pipeline is defined here: https://github.com/knative/build-pipeline/blob/master/pkg/apis/pipeline/v1beta1/pipeline_types.go
Any additional fields included should cause a failure (e.g. if a typo is made when defining a known field).
Actual Behavior
Some basic validation is applied, e.g. that required fields are present and that fields are in the correct format (e.g. string vs. int), but that's it.
Steps to Reproduce the Problem

Deploy the Pipeline CRDs to your k8s cluster
Create an instance that has invalid fields, e.g. a malformed URL or a typo in one of the fields.
Apply the instance with kubectl apply -f and notice that the controller does not complain

Additional Info
Blocked by #19

/assign dlorenc


New line with single CRLF

Hi,
I 've been using Atom to create and edit markdown files up to now. It also has a preview plugin, which has an option 'Break on single new line'.
But as I prefer using Notepad++ as an editor, I did some tests to edit and preview markdown files in it. Your plugin is exactly what is needed to preview, only it would be nice, if you could add the same option.
Regards,
Anne-Mie Wauters

Hey @Wautean
I like the idea. I will have a look how easy I can add that option over easter.
Cheers

Yeah
It will be great also for me
I have many file (more than 500) in markdown and I need a line break when I press  otherwise I can read them properly
It work fine on stackedit (my markdown editor of choice for now) but not here

I see others markdown editor and it works, it can be very usefull for the neatness of the viewer
Thanks


add .catch() to every .then(), and try{}catch{} around every async operation.

 Must fix.

I can make some headway on this.

This PR https://github.com/cloudflare/wrangler2/pull/121 actually made the situation a lot better. I'm closing this.


TN-1201 Respect browser locale preferences

Add browser fallback for locale configuration

If no explicit locale preferred (set in /profile)
If not logged in

Hello @ivan-c! Thanks for submitting the PR.

In the file portal/models/i18n.py, following are the PEP8 issues :

Line 382:80: E501 line too long (80 > 79 characters)

@pbugni Thanks! I found it in a discussion here.
Under the covers it's just using a dict to map languages to which is there is only one reasonable locale. ie sv (language) to sv_SE (locale)


posh-gvm is unable to install griffon 2.5.0

Hi
posh-gvm is unable to install griffon 2.5.0
i ran gvm install griffon 2.5.0
It said version not found

If you execute the the command gvm list griffon you will get a list of all the available griffon version. Currently this is something like the following output showing there is no 2.5.0 available via GVM / SDKMAN.
After checking the Griffon website http://griffon-framework.org/ I think they does not distribute a SDK version anymore after release of 1.5.0. The quickstart guide recommand to use lazybones and gradle.
================================================================================
Available Griffon Versions
================================================================================
     1.5.0                0.3.1
     1.4.0                0.3
     1.3.0                0.2.1
     1.2.0                0.2
     1.1.0                0.1.2
     1.0.2                0.1.1
     1.0.1                0.1
     1.0.0                0.0.1
     0.9.5                0.0
     0.9.4
     0.9.3
     0.9.2
     0.9.1a
     0.9.1
     0.9

================================================================================
+ - local version
* - installed
> - currently in use
================================================================================


feat: add message retention seconds

Description

Motivation and Context

Breaking Changes

How Has This Been Tested?

[ ] I have updated at least one of the examples/* to demonstrate and validate my change(s)
[ ] I have tested and validated these changes using one or more of the provided examples/* projects

[ ] I have executed pre-commit run -a on my pull request

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


update cell_methods

closes #9

@gnikulin Could you check these changes? There is no 'wsgsmax', 'capemax', 'limax', 'cinmax' in CMIP6 so i took their monthly cell_methods from tasmax...


[UI/UX] Re-design the CasperDash Web App

Is your feature request related to a problem? Please describe.
We would like to re-design the CasperDash Web App which sync the styles with Chrome Extension and Mobile App
Describe the solution you'd like
N/A
Describe alternatives you've considered
N/A
Additional context
N/A

Estimation: in the end of this week (26/06/2022)

https://www.figma.com/file/tmhzFfvfRuvCFjGhSsdcjt/Casperdash?node-id=1528%3A4687
Doing responsive version.

Have finished dark mode + mobile responsive.


Allow MT only when user can publish

Short description

This PR makes our MT feature available only for users who are allowed to publish the target contents.
Proposed changes

Change is_permitted to check whether the current user can "publish" the content(s) (required: can_change for Event and POI as before, can_publish for Page either per role >= Editor or per page based permission or as organization member)
Deaktivate MT bulk action completely for observers and authors for pages

Side effects

is_permitted, DeeplApiClient and GoogleTranslateApiClient are extended with a variable. I hope this won't affect other parts, for it is "optional" with default value

Resolved issues

Fixes: #2961

Pull Request Review Guidelines

Hey @MizukiTemma, can you provide a step-by-step guide on how to test this pull request? That'd be great. 🤗

@deen13
Thank you for your interest in this confusing PR 😸
I think it's the best to log in as different roles and see whether MT is available.
-----The wished state-----
Events and locations: if you have permission "change_event"/"change_poi" you can use MT both by bulk action and check box in the form
Pages: if you have permission "publish_page", you can use MT both by bulk action and in the form.
-----The tasty point-----
Observers have neither "change_page" nor "publish_page" and authors have "change_page" but no "publish_page". As they are not allowed to finalize/publish any page, MT should not be available for them.
However, they can be entatiled for "publishing" certain pages if they are lised as editors in the area "Additional permissions for this page" in the form or their organization is assigned as "Responsible organization".
In such special cases, even for those restricted roles, MT should be available in the form. Bulk action MT should be though not available.
Tipp: the "Update" Button on the upper right corner of the form must be accompanied by checkbox for MT.
Only "Submit for approval" is available or no button for upate appears, then MT should not be available.

@charludo Thank you for review, I agree with your idea 👍 That will be a way cleaner solution 😸
This PR will be closed as its changes must be now reverted.

@MizukiTemma do you want to open a second PR for this, or would you like someone else to work on the issue?


[fix-204] - Fixes #204 - TT

Linked Issue:

Checklist:

[x] Did you sign the Contributor License Agreement?
[x] Is the linter reporting 0 errors?
[x] Did you comply with our styleguide?
[x] Is there adequate test coverage for your new code?
[x] Does the CI pipeline pass?
[ ] Did you update the documentation?
[ ] Did you update the sample app?
[ ] Do we need to increment the minor/major version?
[ ] Did you change the public API?
[x] Have you done everything you can to make sure that errors that can occur are compile-time errors, and if they have to be runtime do you have adequate tests and documentation around those runtime errors? For more details.

If Applicable:

[x] Did you test when the first item is skipped?
[x] Did you test when the last item is skipped?
[x] Did you test when middle items are skipped?
[x] Did you test when incorrect data is passed forward?
[x] Did you test proceeding backwards?

If Public API Has Changed:

[ ] Did you deprecate (rather than remove) any old methods/variables/etc? Our philosophy for deprecation.
[ ] Have you done the best that you can to make sure that the compiler guides people to changing to the new API? (Example: the renamed attribute)
[ ] If necessary, have you tested the upgrade path for at least N-1 versions? For example, if data persists between v1 and v2 then that upgrade should be tested and as easy as we can make it.

Assuming the pipeline passes and given the severity of the bug I'm going to self-approve.


Complete JavaScript example needed for writing to out blob binding

The JavaScript example simply copies the the input into the output. There doesn't appear to be any documentation on how to take a blob (from say a file upload or another operation) and put it into the output stream.

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

ID: 910d4732-bb08-d16a-a932-19c6bd1628c2
Version Independent ID: af4358c7-cb5c-bdc7-6433-289f47dc186b
Content: Azure Blob storage output binding for Azure Functions
Content Source: articles/azure-functions/functions-bindings-storage-blob-output.md
Service: azure-functions
GitHub Login: @craigshoemaker
Microsoft Alias: cshoe

@GeekTrainer Thank you for your feedback! We will review and update as appropriate.

@GeekTrainer Thank you for reaching out. So are we trying to upload a file from the stream and upload to a blob using an output  binding or you want to use any http trigger to upload any data to a blob using an output binding?
If you wish, we can also connect offline to discuss in detail : please send an email with subject line “Attn:Jaya” to AzCommunity[at]Microsoft[dot]com referencing this thread along with the detailed requirement

@craigshoemaker I would request you to review the document for JavaScript sample. I believe we should consider updating the "Usage" section as well.
Note : I have started working on a sample to resize the image and put that in the output stream. I will share the details with you  once it is completed.

@JayaChatterjee-MSFT @craigshoemaker I'd love to follow up on this to see if there's any update. Thanks!!

@GeekTrainer Thank you for following up. We have already discussed the required changes internally and the author is aware of this.
@craigshoemaker  Can we add the supported types and output examples in the Usage section.


Automatically close prepared statements after execute

Right now we rely entirely on NIF destructor calling behavior which is apparently unreliable for cleaning up our queries/statements. One thing I see the myxql driver do is automatically close any unnamed queries after execute.
As part of this we can change our implementation of handle_close to actually close the query given.

I think that is fine. It should not affect the streaming implementation since handle_close isn't called until it's done.

rely entirely on NIF destructor calling behavior which is apparently unreliable

Is there a thread or bug report to link to for this? I'm interested in it because if I make another NIF in the future, I'd like to know.

I think unreliable was the wrong word - I think "not immediate" is the better phrasing.
This link is a good one:
http://erlang.org/pipermail/erlang-questions/2020-November/100150.html

As a general rule: never use finalizers for the primary resource
reclamation path

(emphasis mine)

Interesting. Good to know.


No real NFT is shown in this project

You can consider using moralis

You can consider using moralis

Hey 👋 this project only showcase UI and animation concept with model data .
Feel free to contribute or use in personal project .


[feature request] support enable/disable

Right now I have to remove the item if I just want it temporally disabled.
Please provide option to enable/disable, something like the picture below.
Thanks for the great app!

Activate


The functionality of sources and sinks got lost

With the implementation of the balanced model interaction generator.
Check and reimplement the option of having sources/sinks in the model

It did not

i did not, afterall


UPD: pull changes from main

Not sure how relevant this is now as some time has passed. Will investigate further and create new PR if needed.


Resources are not re-resolved after installing extensions

Shallow resources that say "Install extension to enable additional features..." are not re-resolved and refreshed upon installing an extension. The workaround is to reload VS Code 😞

It seems like we really need to dump the cache on refresh.

Yep, that's the issue. I experimented with checking to see if the resolver returned by getResolver() has changed since the last resolve, and clearing the cache if it has. And it seems to work well.

I mean, the whole cache. We keep encountering issues because we're trying too hard to cache things. I don't see why we should keep anything between refreshes (except the ID of focused nodes).


Certify Ubuntu 20.04 on arm64

Scope of this issue is to validate and certify Ubuntu 20.04 on Arm64 (including Jetson nano)
Ubuntu 20.04 on amd64 is validated here
https://github.com/rancher/k3s/issues/1712 on K3s v1.18.3+k3s1

Just got a Pi4 4GB with Ubuntu 20.04 arm64 added to my cluster as an agent last night! Working great so far. Had to add amd64 nodeSelectors to a few pods (looking at you OpenEBS) that don't have multi-platform images yet.
I have an 8GB coming soon as well, I might reserve that for use as a single-node cluster to see how sqlite and etcd work on sd cards.

I replicated the failure on a Pi4 4GB found in https://github.com/rancher/k3s/issues/1712
Again, plain install with no env vars or args.
root@s2:~# k3s kubectl get node
Error from server (ServiceUnavailable): the server is currently unable to handle the request

Do you have any logs or hw info to go along with that error @sesteel ? I've been rotating my 4gb and 8gb through various configurations as server and agent and haven't found any issues yet other than just image availability.

@brandond I corrected my issue.  When I built it, I entered the cgroup settings in the wrong location.  On Ubuntu 20.04, they are to be appened in /boot/firmware/cmdline.txt.

@brandond, also have a cluster of 8GB Pi4 B but having the same message everyone else has reported. Not sure why I'm having a different experience that you are. Any thoughts on where to look?
root@rpi-k3s-mgr-01:/boot/firmware# kubectl get node
Error from server (ServiceUnavailable): the server is currently unable to handle the request

For what it's worth:
root@rpi-k3s-mgr-01:/boot/firmware# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS"

root@rpi-k3s-mgr-01:/boot/firmware# uname -a
Linux rpi-k3s-mgr-01 5.4.0-1012-raspi #12-Ubuntu SMP Wed May 27 04:08:35 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux

@brandond, @sesteel: All resolved now. I managed to also append the following cgroup info in the wrong place:
cgroup_memory=1 cgroup_enable=memory

Would be great if the log message referenced the correct location for cmdline.txt. It currently says:
"failed to find memory cgroup, you may need to add \"cgroup_memory=1 cgroup_enable=memory\" to your linux cmdline (/boot/cmdline.txt on a Raspberry Pi)"

Either way, all good now. If there are any other recommended but undocumented tweaks, could you post them here?

FWIW, I've been running ubuntu 20.04 pi4 based nodes in a mixed-architecture k3s cluster for a while now without issue whatsoever.  Using the following tweaks to the ubuntu arm64 image makes it pretty easy to install and operate.
The big one is the cgroup changes to cmdline.txt like you say.

Installation of k3s version v1.18.8+k3s1 is successful.
Validated on:
Jetson nano, Ubuntu20.04 arm64
Raspberry pi, Ubuntu 20.04 arm64 with the update made to cmdline.txt
cat /boot/firmware/cmdline.txt
cgroup_memory=1 cgroup_enable=memory


Uncaught Error: channel closed

[Enter steps to reproduce below:]

...
...

Atom Version: 1.8.0
System: Unknown Windows Version
Thrown From: atom-jshint package, v2.0.0
Stack Trace
Uncaught Error: channel closed
At events.js:141

Error: channel closed
    at ChildProcess.target.send (internal/child_process.js:509:16)
    at AtomJsHint.module.exports.AtomJsHint.run (C:\Users\iagudovi\.atom\packages\atom-jshint\lib\atom-jshint.js:105:21)
    at AtomJsHint.<anonymous> (C:\Users\iagudovi\.atom\packages\atom-jshint\lib\atom-jshint.js:66:16)
    at Function.module.exports.Emitter.simpleDispatch (C:\Users\iagudovi\AppData\Local\atom\app-1.8.0\resources\app.asar\node_modules\event-kit\lib\emitter.js:25:14)
    at Emitter.module.exports.Emitter.emit (C:\Users\iagudovi\AppData\Local\atom\app-1.8.0\resources\app.asar\node_modules\event-kit\lib\emitter.js:125:28)
    at C:\Users\iagudovi\AppData\Local\atom\app-1.8.0\resources\app.asar\node_modules\text-buffer\lib\text-buffer.js:1378:25

Commands
     -1:13 editor:consolidate-selections (atom-text-editor.editor.is-focused)
     -1:13 core:cancel (atom-text-editor.editor.is-focused)
     -1:06.4.0 docblockr:parse-enter (atom-text-editor.editor.is-focused)
     -1:06.4.0 editor:newline (atom-text-editor.editor.is-focused)
     -1:04.4.0 core:move-left (atom-text-editor.editor.is-focused)
     -0:56.7.0 core:move-right (atom-text-editor.editor.is-focused)
     -0:55.2.0 docblockr:parse-enter (atom-text-editor.editor.is-focused)
     -0:55.2.0 editor:newline (atom-text-editor.editor.is-focused)
     -0:54.8.0 core:move-down (atom-text-editor.editor.is-focused)
  9x -0:54.4.0 editor:move-line-down (atom-text-editor.editor.is-focused)
     -0:52.6.0 editor:move-line-up (atom-text-editor.editor.is-focused)
     -0:49.9.0 atom-beautify:beautify-editor (atom-text-editor.editor.is-focused)
     -0:47.6.0 core:backspace (atom-text-editor.editor.is-focused)
  2x -0:46.9.0 core:save (atom-text-editor.editor.is-focused)
     -0:05.2.0 editor:delete-line (atom-text-editor.editor.is-focused)
     -0:04.7.0 core:save (atom-text-editor.editor.is-focused)

Config
{
  "core": {
    "disabledPackages": [
      "git-time-machine",
      "tree-view-git-branch",
      "tree-view-git-projects",
      "tree-view-git-status",
      "minimap-git-diff",
      "todo-list",
      "todo",
      "todo-manager",
      "npm",
      "linter-jscs",
      "linter-package-json-validator",
      "linter-json-lint",
      "tree-view-git-modified",
      "optional-jshint"
    ],
    "projectHome": "C:\\Users\\iagudovi\\Desktop\\CODIGO"
  },
  "atom-jshint": {}
}

Installed Packages
# User
angularjs, v0.3.4
atom-beautify, v0.29.9
atom-jshint, v2.0.0
atom-json-color, v0.4.2
atomic-chrome, v0.3.0
autocomplete-angular-material, v0.4.0
autoupdate-packages, v1.3.1
chary-tree-view, v0.2.3
docblockr, v0.7.3
emmet, v2.4.3
file-icons, v1.7.16
jshint, v1.8.5
linter, v1.11.14
linter-bootlint, v1.0.2
linter-htmlhint, v1.2.1
linter-sass-lint, v1.6.1
minimap, v4.24.7
minimap-pigments, v0.2.1
pretty-json, v1.4.1

# Dev
No dev packages

Facing the same issue.

@Joezo

A restart seems to fix the issue. Can anyone else verify?


Setting $authProvider.loginUrl appends the URL

$authProvider.loginUrl = 'http://myapi.com/auth/local';
$authProvider.signupUrl = 'http://myapi.com/api/users';

Subsequent POSTs are routed to http://localhost:9000/http://myapi.com/api/users and http://localhost:9000/http://myapi.com/auth/local.

Okay... I just found $authProvider.baseUrl in the source. Maybe it could be added to the README.

Thanks, will add it right now.

adbc9f9e6082986b93e27aa3716f42cbd5deb3c5 allows you to set baseUrl to null so you could still use loginUrl and signupUrl as before, thus avoiding "double urls" like http://localhost:9000/http://myapi.com/auth/local


Approximate European option price under SABR model

SABR model has accurate density approximations  (see, e.g., here). It is of interest to use the approximations to estimate European option prices.
The module implementing this method should live under tf_quant_finance/volatility/sabr_approximation.py. It should support both European puts and calls approximations. Tests should be in sabr_approximation_test.py in the same folder.

@joybh98
Hi Joy, Are you still working on this issue? If you aren't could you please let us know?
-Ashish

@saxena-ashish-g I'm not working on this issue. Whoever wants to take this please go ahead.

@cyrilchim I didnt come across any folder named volatility under tf_quant_finance. Can you please point me to the file?

@Rish001 It has been refactored. This has to go to models/sabr/approximations/european_option.py (similarly to heston structure)

Do you want this approximation of SABR model to be implemented?

Yes, Rishav, that is the approximation. One could use it for calibration purposes as described in the paper

What are the possible test cases that my implementation needs to be tested against?

Hi Rishav,
You can find different estimated European option prices under the SABR
model here http://ta.twi.tudelft.nl/mf/users/oosterle/oosterlee/SABRMC.pdf.
Your approximation should lead to similar results.
Please let me know if you have any further questions. I am happy to help
you debug the code if you get stuck.
Best,
Cyril
On Thu, Jul 30, 2020 at 2:19 PM RISHAV DUTTA<EMAIL_ADDRESS>wrote:

What are the possible test cases that my implementation needs to be tested
against?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/google/tf-quant-finance/issues/8#issuecomment-666359382,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADMX3DXUGCQ4CPDDD2GENZTR6FXMZANCNFSM4IVSNTLA
.

How are these integrations working? are these integrations nested in one inside the other?

It would help me if you can please give me a clue how this integral would look like for tenor T2 and beyond

@Rish001 The approximation p(t, ... ) is the forward transition density of the SABR process. Computing option prices could be done by creating a uniform grid of points in (F, A) space and computing the average in the formula (2.6) from the original paper. B is a zero-coupon bond price which is a standard notion. In case of a constant interest rate r it is a discount factor exp(-r * (T - t)). (see, e.g., here)
I think the best way to get started is to implement the approximation first. It seems that the original paper is self-contained in terms of notations.
By the time this is implemented, we will have the SABR model in the module and you will be able to use Monte Carlo method to get option prices and get your implementation tested. Does this sound good?

As the mentioned integral is unbounded, I think Monte Carlo integration is to be applied. Do you think any other way to compute the integral?

@cyrilchim I have built a minimal viable code for determining option price for option tenor T1. But i am encountering overflow error which I am unable to remove. I would really appreciate it if you can provide me some helpful direction.

Please find the link to code in google colab

Just to leave you an update. I have mostly finished debugging and will be submitting shortly

@cyrilchim could you give me a set of test cases to test my implementation against? I need a number of combinations of alpha, beta,rho, nu,forwards,strikes and time to maturity and corresponding implied volatility values so that I can test my SABR implied vol calculation

Hi Rishav,
We do not have explicit tests but you should be able to use current SABR model to sample trajectories and estimate European option price (put or call). Your approximation should give similar results


ARROW-14656: [Python] sort helper for Array, ChunkedArray and StructArray

11659

 Quality gate: Passed
3 Issues

 3 Code issues

Details

 Quality gate: Passed
16 Issues

 16 Code issues

Details

 Quality gate: Failed
 Everything looks good
Details


Fix power calculation when battery units are in μA instead of μW

current_now needs to be multiplied by voltage_now to get the current power usage in μW.

Thanks!


feat: Support retrieving config from config[Symbol.for('nycrc')]

Fixes #1087

Coverage increased (+0.01%) to 96.88% when pulling 74d9bd45dc78a65ea9e0137d766e11daebd76720 on coreyfarrell:nycrc-symbol into c5d90fa26f96b1c59875b2c8401442c5c4c9ad9c on istanbuljs:master.

Coverage increased (+0.01%) to 96.88% when pulling 74d9bd45dc78a65ea9e0137d766e11daebd76720 on coreyfarrell:nycrc-symbol into c5d90fa26f96b1c59875b2c8401442c5c4c9ad9c on istanbuljs:master.


Fixing requirements.txt

Expected Behavior

Normally install the packages from requirements.txt

Current Behavior

Getting a version mismatch error for pytz package (Picture attached below)

Possible Solution
Updating requirements.txt file to the latest one for error-free package installations

You should manually pip install all the stuff in requirements.txt because it's probably broken somewhere

yea, or you can just change the version to 306 for pywin32. btw, what version of python are you using? I am on 3.12.3, but it dont' seem to work even I install all the requirements.

Lol good for you. I will try it again. If I fail, I will simply give up

I found a cool project which can be a better replacement for this.
Glaze Window Manager (i3 and polybar-based):
https://github.com/glzr-io/glazewm


How to integrate new database support?

Hi,
nice project! Can you provide a documentation on how we can integrate a new database support.
Want to test it with ORACLE and MSSQL. 👍
Many Thanks!

You need to understand these two things to integrate a new database support for ORACLE and MSSQL
Database configuration in Django
You can go through this section in
Django's documentation to understand how database setup is done in Django.
Configuring database backend for ORACLE and MSSQL
ORACLE database can easily be configured since django provides support for that. You can follow these steps to configure your ORACLE database.
For MSSQL, you will have to use a third party library which provides a database engine for MSSQL. Here are a couple of popular libraries which can be used to configure MSSQL database - django-pyodbc-azure and django-mssql
Hope this is helpful


@ConditionalOnProperty fails with @EncryptablePropertySource

It looks like there is an issue with using @ConditionalOnProperty in conjunction with @EncryptablePropertySource. I have a bean which is annotated with
@ConditionalOnProperty(name = "bean.enabled", matchIfMissing = false)
and I am importing the properties with
@EncryptablePropertySource(value = { "classpath:beans.properties" })
and beans.properties contains the property "bean.enabled=true"
The bean is not instantiated. Commenting out the @ConditionalOnProperty annotation allows the bean to be created, and all other properties are loaded correctly.

Interesting issue, let me dig on that...

Alright so you can do this:
@PropertySource(name = "EncryptedProperties", value = "classpath:encrypted.properties")
@EnableEncryptableProperties

And that will effectively encrypt the property source imported with the @PropertySource annotation. The downside is that if you @ConditionalOnProperty's havingValue property you can't use a decrypted value. In other words, you can use this as far as you don't use an encrypted property with havingValue. So you can use any other property, or you can check for just the existence of an encrypted property.
The reason this doesn't work is because the property sources are picked up really early in the game before bean definitions, and that is not the case of property sources created with @EncryptablePropertySource since they're created with a BeanDefinitionRegistryPostProcessor and that's the earliest in the game I have found to integrate the annotation.
If you need to use havingValue from @ConditionalOnProperty depending on the value of an encrypted property, then your only option is to use:
new SpringApplicationBuilder()
                .environment(new EncryptableEnvironment(new StandardEnvironment()))

on your spring application builder, but again, for bean conditionals on properties you're limited to either the EncryptableEnvironment or EnableEncryptableProperties


Does the SDK support the mini program？

It went something wrong when I try to use the nkn-sdk-js in wechat mini program,
something like npm package dependency. If I install the dependencies manually and
try to create the client, some runtime error occured.
So does the sdk support for mini program?
Thanks!

I just did some test and found a few caveats. You need to select right lib version, enhanced compilation and use npm module.

After that there are a few incompatible dependencies:

@nodeguy/channel: this is an easy fix, just replace ` with ' in the require fix the problem.
tweetnacl: might need to switch from crypto to crypto-js for random bytes.
google-protobuf: might need to switch to protobufjs.

There might be more incompatibility but I stopped there. All of the issues I found so far are caused by the restrictions of require in mini program environment. It might be able to get it working but not easily I think.

Thanks! I got it. By the way, will the nkn offical give support for that in the future

We will try. Currently I'm still not sure if we can get it working because there might be other dependency issues.

That's it. Thanks for your effort!

Thanks! I got it. By the way, will the nkn offical give support for that in the future

Thanks! I got it. By the way, will the nkn offical give support for that in the future

所以，小程序里是如何适配才能跑起来呢，兄弟？

Closing due to inactivity. Feel free to continue the discussion or reopen it.


Auto-URLs are confused by wide characters - close #427

wxpython is explicit that you can't mix GetValue() and positions you get from other APIs.

Closing in favor of the other CR.