Remove void_t GCC bug workaround

:notebook_with_decorative_cover: Description
Problem:

void_t from type_traits.hpp is not needed as std::void_t is
widely available.
Hand-rolled void_t in vast/detail/function.hpp is not needed
either as CWG issue 1558 has been fixed as of GCC 5.0

Solution:

Remove void_t from type_traits.hpp in favor of using std::void_t
directly.
Remove hand-rolled void_t that worked around CWG issue 1558 in favor
of std::void_t.

:memo: Checklist

[X] All user-facing changes have changelog entries.
[X] The changes are reflected on docs.tenzir.com/vast, if necessary.
[X] The PR description contains instructions for the reviewer, if necessary.

:dart: Review Instructions
File-by-file.

CC: @dwms-qlab


Error in windows

Traceback (most recent call last):
File "cors_scan.py", line 6, in
from common.logger import Log
File "C:\..\..\CORScanner-master\common\logger.py", line 1, in
import fcntl
ImportError: No module named fcntl

Thanks, @razapoonja. It seems that fcntl module isn't supported on Windows.
I moved the "import fcntl" backwards. It's a temporary workaround if you don't need to use the "-o" option.

Thanks @chenjj for the quick temporary fix


tower-cli monitor command giving garbage value when running job verbosity is 3 or higher

Hi, I am trying to run a job with verbosity 3 but when I monitor the job from putty console, it is throwing garbage values as showing in below screenshot. We are not seeing the same behavior with verbosity 2. We tried with different VMs and different RAM. Could you please help me with this?

Not sure that I understand your question. Are you talking about the tw command?

Seems not related to the Tower CLI

Sorry for the late reply. We actually use the "tower-cli" command not the "tw" command.


[FEATURE] Homepage feature to have section on map

Description
On the homepage we list the feature of LinkFree, but we need to add the map page

[ ] title
[ ] description
[ ] screenshot

Screenshots
No response
Additional information
No response

Hii @eddiejaoude I want to work on this issue

hey @eddiejaoude, can you please elaborate on what we exactly need to do for this issue, I will love to help!

Is this how you want it to be @eddiejaoude

assigned

I made this on Figma, I have not started to code or anything
so I think we should let @devXprite work on this, as they asked first

@devXprite if you still want to work on it you can, use the image I provided above as a reference, and also make sure to keep note of the changes Eddie asked for above

I made this on Figma, I have not started to code or anything

oh love this @Aadarsh805 👍

@devXprite if you still want to work on it you can, use the image I provided above as a reference, and also make sure to keep note of the changes Eddie asked for above

Thanks @Aadarsh805

Great collaboration everyone !!


fix(collaborate): blocked user shouldn't be able to edit transcript

ref: https://g0v.hackmd.io/vKCvrqSQTlm7GEx9MAXGaw?view#op-Transcript-spam-處理

coverage: 76.218%. remained the same
when pulling b9cc03d6f012ac753b8afed7177537118e419275 on fix/collab
into 20083e3803056d00537944090c61f5d70690270b on master.


CubicSplines: Add AbstractMatrix support

Checklist

[x] Appropriate tests were added
[x] Any code changes were done in a way that does not break public API
[x] All documentation related to code changes were updated
[x] The new code follows the
contributor guidelines, in particular the SciML Style Guide and
COLPRAC.
[x] Any new documentation only uses public API

Additional context
Add any other context about the problem here.

Why is this needed instead of the vector of vector form?

I think we should have both forms. Its also part of fixing https://github.com/SciML/DataInterpolations.jl/issues/206

Why is this needed instead of the vector of vector form?

We can extend this to higher dimensional matrix. That is of course dependent on, whether we need that in DataInterpolations.jl

I see, yes we should support fully then.

Generalized this to AbstractArray and added tests for 3d arrays as well.

Can you rebase on master?


The service <IP_ADDRESS> can run. After the service is started, the public IP and internal IP of the server cannot access it. What is the reason?**

The service <IP_ADDRESS> can run. After the service is started, the public IP and internal IP of the server cannot access it. What is the reason?

Try localhost:3000


[Question] [Proposal] Closure vs callable

Hey good folks,
I have a question, related to a design problem I stumbled upon today while developing some nice code with Laravel:
Why don't we use callable type-hint instead of \Closure wherever applicable? The former covers the latter, whereas the other way around isn't valid. Example code:
Router::group($someOptionsHere, [$this, 'myCallbackMethod']);

won't work with Laravel's current signatures. However if one changed these sigs, let's say for the group() method above FROM
public function group(array $attributes, \Closure $callback)
TO
public function group(array $attributes, callable $callback)
everything would be honkie dorie. We could use both Closures and regular callables. Additionally, let me note that callable type-hinting has been introduced in PHP 5.4, so we are covered. As you can see there are no BC implications involved as well.
Thoughts?
CC: @taylorotwell , @GrahamCampbell

If "the Gods of Copybook Headings" are interested, I can start working on this one by the way :)

:+1: for this, bumped into this so many times

There is definitely a BC break, since the signature of an overriding method has to match exactly.

Of course, but its a framework method, both the interface and its implementation lie inside framework. Do you mean someone would be bold enough to override, let's say, Router class and rewrite it from scratch? :) If not, we can limit these changes to such implementations and their respective interfaces.

:+1: We definitely talked about this back when we created Closure typehints all over the place.
Backwards compatibility definitely is an issue, though.

Related issue is the fake callables in Laravel, ie. Foo@bar instead of PHP's standard callable notation which is Foo::bar

Can you elaborate @Anahkiasen : how can one pass anything fake that isn't a \Closure instance?

I'm pretty sure there are people that have overridden parts of the framework, created packages that implement framework contracts/interfaces etc.
In the end it doesn't really matter if someone actually did do so, but just the fact that there's a possibility of breaking someones code. I don't see this as huge issue though. The changes would just have to be targeted at 5.2.

@franzliedke : I am finding files like https://github.com/laravel/framework/blob/5.1/src/Illuminate/Support/Arr.php with callable in their signatures and PRs related to them. Can you point me in right direction when \Closure hints were added please?

@lukasgeiter : Yea, I had the same initial idea, to make these changes for the next release.

@shehi Long ago, in the beginning times of Laravel 4.

@shehi What I meant is in a lot of places Laravel expects this notation Foo@bar (routes, view composers, etc.) which means you can't pass an actual callable like ù Foo::baror[$foo, 'bar']` etc

@Anahkiasen : I know, but you don't have to. callable hint allows passing a \Closure instance. I said above, its compatible one way, not the other way around.

If at least we could do this for handful of methods, like Router implementation here - code looks so ugly when I wrap existing class method with a lambda function just to satisfy hint requirement. :(

I think 5.2 is a good place to do this if we do given 5.1 is LTS and that 5.2 will be using symfony 3.0.

We've already broken a few things in 5.2 already.

I say broken - "removed". :)

Glad to hear this @GrahamCampbell . If @taylorotwell gives a go as well, I could start small PR and we could move bit by bit, carefully :)

Yeh, it really is totally up to @taylorotwell. It ultimately doesn't matter what I say, lol.

Pinging @taylorotwell

Ping @taylorotwell.

I'm fine with moving non-breaking things to callable where possible.

Would be good to get this sorted in 5.3.

Sorry, we don't process requests/proposals here. Please see https://github.com/laravel/internals/issues.

Moved to laravel/internals#25, let's continue there.


Replace Travis CI with GitHub Actions

Things added/changed:

Replace Travis CI with GitHub Actions.
Improve README.md and add build status badge.

P.S.: Looking forward to keep contributing to this amazing repository! 🙂

Thank you!


Two events fired on first select

Hi!
I have the problem with selecting the color from picker, because the first time I open it and select some value onChange event gets fired twice. I checked the call stack and the event is fired by both onColorClick and onMouseUp events. After that it seems like it's working fine. Not sure if this is something I broke with my fork, but it does not seems so. I am using hsv format and I tried to set the value initially to both null and hsv string or object. Maybe you have some rough idea what can be potentially wrong here ?
EDIT: the first ng-model value is always (0, 0%, 100%)

Fixed in commit b9404ddb157b05113a9d3e6b1b90ee0f94114070 and released in v2.1.6


Better Explanation of the Draft Conceptual Model

There is an expressed need for clarification of various aspects of the CityGML 3.0 Conceptual Model. The rationale - use case addressed, problem solved, complexity reduced -  for modelling decisions that went into the current draft need to be explained. How much discussion about various aspects of the Conceptual Model do members want? Which areas are these? Small core plus mostly independent modules? Can we bake a profiling scheme into the structure of the modules in the Conceptual Model? A combination of flexible profiling and flexible extension (ADE) seems like a great story. But is it achievable?

This issue is subsumed by the forthcoming specification document.


Initial Commit of Clock Widget, Example for SSD1963

Initial Commit of Clock Widget and Working Example for SSD1963 8bit Parallel TFT on ESP32

Hi Bodmer,
Awesome library you have created here, I found it some years ago and have been itching to play more, but time was an issue, I'm sure you also feel that pain.
I am not sure if you accept collaborative pull requests ?
If you do, and of course when you have some time could you please review the attached Clock Widget. I've only tested it on an 7" SSD1963 8bit Parallel Interface attached to an ESP32 for now, but have access to an ILI9341 SPI ESP8266 combination and a beautiful round SPI screen which I've not connected yet but hope this works :).
I've added the Widget main code and a Widget --> Clock_Demo.ino for an example.
The widget should be scalable based on radius.
Do you see any issues ?  Any improvements or changes required to allow a pull ?
It been awhile since I sent a Pull Request outside my own environment, I hope all is OK, please let me know.

Best Regards
Kev

It appears to work well, tested on multiple screens
SSD1963 - Parallel 480x800, setup 50 with 800BD_Driver
ILI9341 - SPI 240x320, Setup 42 with no changes
ST7789H2 - SPI 198 x 240, Copy of setup 71 with just width and height updated
All with ESP32


Warnings at zef install GeoIP2

When installing via zef: $ zef install GeoIP2 got this message:
WARNINGS for /home/kostas/.zef/store/GeoIP2.git/40c1b984344b2925bfa768cab247c230d5d4f0c2/lib/GeoIP2.pm (GeoIP2):
Useless use of LOOP_BLOCK_1 symbol in sink context (line 133)
===> Testing [OK] for GeoIP2:ver<1.0.0>
===> Installing: GeoIP2:ver<1.0.0>
WARNINGS for /home/kostas/apache_root/perl6.pheix.org/git/pheix-pool/home#sources/B14446447BBA55BFD32F41138C6E7B843FF09D07 (GeoIP2):
Useless use of LOOP_BLOCK_1 symbol in sink context (line 133)

It's harmless and happens only during installation phase - https://github.com/rakudo/rakudo/issues/1900
I'll add do loop { } to sink phaser output as temporary fix until it is resolved in Rakudo.


Please publish 2.0.0-alpha

I am using  Vue.js ^1.0 and vue-validator can't work as expected

+1

+1

Have you try Vue migration? I'm using it with Vue-strap until new version release.

sorry... everyone.
I'm busy with the work.
I'm developing the v2.0 in incremental steps though. (Please see  https://github.com/vuejs/vue-validator/commits/dev/latest)
When I finished basic validation feature implemetation, I'll publish as 2.0-alpha.1
Please wait.


AssetLib out of date

The version labeled "1.0.1" on AssetLib for Godot 4 is written in GDScript 3, not 4.

Hey @halotroop2288 thank you for telling me.
It seems I forgot to update the "Download Url"
I've just resubmitted it. Should be corrected soon.


Implement optimizer rule to remove redundant repartitioning

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
When running benchmark q2 I see this in the plan:
RepartitionExec: partitioning=Hash([Column { name: "r_regionkey", index: 0 }], 48), metrics=[fetch_time=69.072358ms, send_time=48ns, repart_time=48ns]
  RepartitionExec: partitioning=RoundRobinBatch(48), metrics=[fetch_time=273.515µs, send_time=1ns, repart_time=1ns]

We introduce the RoundRobinBatch partitioning to increase parallelism but then we insert the hash partitioning later for the join. It is redundant to repartition twice here, and it would be better to just preparation on the join key right away.
Note that this repartitioning is especially expensive for distributed query engines that build on top of DataFusion (Dask SQL, Ballista) because it introduces extra shuffles.
Describe the solution you'd like
Implement new rule to push hash partitioning down and replace the round robin partitioning.
Describe alternatives you've considered
None
Additional context
None

Ballista already removes these round-robin repartitions so closing this


Can't find pkg-config during configure

Hi, I'm trying to compile vim 8.1.0150 from source with ./configure --enable-gui=gtk2 && make && make install but I can't find the gvim binary. It turns out the problem is pkg-config is not found during configure:
...
checking for IceConnectionNumber in -lICE... yes
checking if X11 header files can be found... yes
checking for _XdmcpAuthDoIt in -lXdmcp... yes
checking for IceOpenConnection in -lICE... yes
checking for XpmCreatePixmapFromData in -lXpm... yes
checking if X11 header files implicitly declare return values... no
checking size of wchar_t is 2 bytes... no
checking --enable-gui argument... GTK+ 3.x GUI support
checking --disable-gtktest argument... gtk test enabled
checking for pkg-config... /home/linuxbrew/.linuxbrew/bin/pkg-config
no
checking X11/SM/SMlib.h usability... yes
...

src/auto/config.log says:
...
configure:9008: checking --enable-gui argument
configure:9086: result: GTK+ 3.x GUI support
configure:9617: checking --disable-gtktest argument
configure:9627: result: gtk test enabled
configure:9681: checking for pkg-config
configure:9699: found /home/linuxbrew/.linuxbrew/bin/pkg-config
configure:9711: result: /home/linuxbrew/.linuxbrew/bin/pkg-config
configure:9850: result: no
configure:10495: checking X11/SM/SMlib.h usability
...

Which is very weird. I'm on CentOS 6.9 and pkg-config version is 0.29.2 and which pkg-config returns /home/linuxbrew/.linuxbrew/bin/pkg-config. I can confirm that pkg-config is working by pkg-config --modversion gtk+-2.0 which returns 2.24.32. Any clue about what's going on here?

Somehow a comment from vim_dev is not forwarded here:
https://groups.google.com/d/msg/vim_dev/f-MXc3zvhLQ/BADaG_2LDAAJ
Quoting:

The problem isn't with pkg-config. but with GTK.
You check pkg-config with gtk+-2.0, but configure thinks you want GTK 3; if you really want GTK2 adjust the CONF_OPT_GUI line in the Makefile.

See the link for detail.

Sorry to necro post but this is an issue with Linuxbrew getting in the way. You can fix it by:
brew unlink pkg-config


Added explaination for Taints and Tolerations

Added explaination for Taints and Tolerations
Link #39442

/hold

/remove-lifecycle rotten

Hello @tamilselvan1102.
I plan to close this pull request. If you have questions or comments, feel free to reopen the PR.
Thanks
/close


Error: Spatie  \  LaravelSettings  \  Exceptions  \  MissingSettings

Message: Tried loading settings 'io3x1\FilamentThemes\Settings\ThemesSettings', and following properties were missing: theme_name, theme_path, theme_namespace, theme_main_color, theme_secandry_color, theme_sub_color, theme_css, theme_js, theme_header,
Path: http://<IP_ADDRESS>:8000/admin/themes
View: resources/views/filament/pages/themes.blade.php

I just installed the package in a fresh project. I have done everything from documentation while installing. It was installed good. "Themes" appeared in navbar. But when I click  to the button there is the error like above
Hope You will help ASAP to fix the issue
Thanks!

Helper

Also I have installed 3x1io/filament-sitemap but in function setting('$key') there are keys only from Theme not Sitemap

i will fix it on the next version with tons of new features.

it's done now please update.


CFE-619: release 0.2 - add stable-v0.2 and stable-v0 channels

This PR adds the new channels:

stable-v0.2 for the upcoming release
stable-v0 for the users ready to streamline the minor version upgrades

stable-v0 channel would allow the engineering to reduce the configuration burden too as the channel needs to be mentioned in all the docs and the Prow CI configuration.
stable-v0.1 is kept in main for the moment to not break CI as it uses stable-v0.1 channel to install the operator. A follow-up PR will need to be done to remove it.

Docs PR: https://github.com/openshift/openshift-docs/pull/53157

/label docs-approved

/label qe-approved

/retest
Failed to pull ci-operator image O_O.


Support increasing and decreasing PoST size via API endpoints

Per https://github.com/spacemeshos/SMIPS/issues/6

It should be fully supported in the latest release but may not be that obvious.

yes. To change the post data, just call it with a different commitment size at the same path.

I made this clearer in the comment, thanks. Closing.


Update to golintci version that is compatible with go 1.21.x

Also update golintci configuration to emulate the behavior of the older version. This will resolve https://github.com/linkedin/Burrow/issues/806

I've tested this linter config locally to see that it passes. There are configs that should be re-enabled, but the failures were in pre-existing code and since we already have 1.21.1 merged to master this is necessary to unblock the CI for other unrelated changes.

Thanks for your contribution!


Capacitor 3 import Error  Interface 'CapacitorInstance' incorrectly extends interface 'CapacitorGlobal'.Types of property 'Plugins'

Describe the bug
Not working on Capacitor 3, on Build i get this error in console.
[ ERROR ]  TypeScript: ./node_modules/@capacitor/core/types/definitions-internal.d.ts:16:18
Interface 'CapacitorInstance' incorrectly extends interface 'CapacitorGlobal'.Types of property 'Plugins'
are incompatible.Property 'CameraPreview' is missing in type '{ [pluginName: string]: { [prop: string]: any;
}; }' but required in type 'PluginRegistry'.
 L15:   */
 L16:  export interface CapacitorInstance extends CapacitorGlobal {
 L17:      /**

Hope that´s help. Sheers Oliver

I test the capacitor 3 support branch too,
`[ ERROR ]  TypeScript: ./node_modules/@capacitor/core/types/definitions-internal.d.ts:16:18
Interface 'CapacitorInstance' incorrectly extends interface 'CapacitorGlobal'.Types of property 'Plugins'
are incompatible.Property 'CameraPreview' is missing in type '{ [pluginName: string]: { [prop: string]: any;
}; }' but required in type 'PluginRegistry'.
 L15:   */
 L16:  export interface CapacitorInstance extends CapacitorGlobal {
 L17:      /**

`

please can this be fixed am currently using nix/webcam to replace this plugin till the support for capacitor 3 is working.
Please I really love this feature

Please can this be fixed quickly. I have an app that uses this and currently can continue to compile after upgrading to capacitor 3.
I had to switch to ngx-webcam for the time been . Please lets get this done

plus one this

Hi,
I have capacitor 2.4.7, but in the package.json if this project there are peer dependencis to "latest" capacitor so it will always throw this error

Same problem here, the plugin is not updated for Capacitor 3.
I discovered it after updating all my project and am now stuck :-)

+1

A capacitor 3 update is on its way : https://github.com/anth0/camera-preview/tree/capacitor-3-upgrade.
I just need to figure out what's going on with one of the latest merge about video recording because it does not compile on my hand.

Has anyone solve this issue?

I've added a PR with a fix https://github.com/capacitor-community/camera-preview/pull/146

@Mathyn I tested your PR and it works. @bialabs please merge
For anyone who wants a quick fix until authors merge, just install @Mathyn PR:
npm uninstall @capacitor-community/camera-preview
npm install git+https://github.com/Mathyn/camera-preview.git

That's all folks!

I have created a repo here that uses this plugin and other methods for getting camera data

I recommend you to take a look
https://github.com/capacitor-community/camera-preview/issues/151#issuecomment-893511569

https://github.com/Mathyn/camera-preview.git

The plugin builds when installed from this repo however it asks for microphone permission still, which is not needed.

There will shortly be a Capacitor 3 build on NPM - please keep an eye on #183 for progress (I don't have permission to upload it). I'm closing this issue now, but thank you all for your contributions! Let's see how good we can make camera-preview in 2022.


Conservatively handle foreigncall expr

Test is broken at dispatch check on length.

With this, we can eliminate the error in #25


realtime 'create' event not being received in Flutter app

Server:
pocketbase version 0.22.23
Client:
Dart version 3.5.4, Flutter Channel stable 3.24.4
pocketbase: 0.18.1
platforms: iOS, Android, MacOS
I am not receiving the 'create' event for my subscriptions on any collections.
The 'update' and 'delete' events are, however, being received for the same subscriptions.

Yes, it works fine just in standalone dart, but not in a flutter app.

One thing I forgot to mention is that you may not receive a create event if the subscribed client and the created record don't satisfy the List rule of your collection.

Ok, but I get the event in a Dart program just fine, but not in a Flutter
app so that doesn't explain it
On Tue, 12 Nov 2024, 12:03 Gani Georgiev, @.***> wrote:

One thing I forgot to mention is that you may not receive a create event
if the subscribed client and the created record don't satisfy the List rule
of your collection.
—
Reply to this email directly, view it on GitHub
https://github.com/pocketbase/dart-sdk/issues/64#issuecomment-2470352851,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHYFFIG2ASS4WI6NE7B5TD2AHVBNAVCNFSM6AAAAABRTYZRVSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZQGM2TEOBVGE
.
You are receiving this because you authored the thread.Message ID:
@.***>

if you do
await pb.create(....);
then
final records = await pb.collection('review').getFullList(
batch: 200,
sort: '-updated',
);
you don't get the create event.

FYI, with an empty List API rule for the collection, it still doesn't work.
But, in both cases, if you put a delay before calling await pb.collection('review').getFullList(, whether the List API rule is empty or not, it works fine.
So I'll just do that.

No, sorry this just doesn't make sense.
Either the subscribe call doesn't complete before you are sending the create request or there is something else in your setup that is causing it to fail.
But again, this entire back-and-forth could be avoided if you just create a minimal reproducible repo illustrating the problem.


[TA] Enabled AAD in tests

Use AAD instead of APIKey in tests.

/azp run java - textanalytics - tests


Let people see this in a browser - for a wider audience

Web is easier than doing iOS

Browser works, but:

shady back behavior. Put a home button in every screen and back where possible
no pause in playable after first switch


JavaScript: Fix uses of TypeTracker with custom flow steps.

These steps need to check that the type hasn't been tracked into a property.
Before I start testing this, I'd like some feedback on the API. Checking for the property name explicitly is awkward and easy to forget and should probably be encapsulated in an auxiliary predicate, but I'm struggling to come up with an intuitive name and would be grateful for suggestions. Or maybe there is another way to ensure this?

We could add a self-returning predicate like use():
class TypeTracker {
  TypeTracker use() {
    prop = "" and result = this
  }
}

This only happens in cases where we're passing t into the recursive call, and that's where I'd advocate for its use:
exists(string name |
  result = myType(t.use()).getAMethodCall(name)
|
  name = "foo" or name = "bar"
)

I like that idea a lot! A more descriptive name than use would be nice; I'll think about it.

I doubt I'd use it very often, though. I usually just do t.start() and use the "end" version of my predicate to throw away the calling context when a sufficiently specific use is found (as per the firebase.database example from the Firebase PR description).

I usually just do t.start() and use the "end" version of my predicate to throw away the calling context when a sufficiently specific use is found

Yes, I'm sure that is in general the more common pattern. However, when tracking the precise origin of flow (and not just the type), it seems dangerous to throw away calling contexts, so that's why I'm doing it this way.

I've encapsulated the t2.getProp() = "" and t = t2 pattern in a new predicate t = t2.continue().
Evaluation on socket.io-relevant slugs looks fine. The evaluation was before the last commit, but the DIL changes from that commit look harmless; I can do another sanity check if desired.


Cherry pick (#2517) to rel-1.28

stabilise intrusion detection failures due to elastic search not being ready

increase number of retries for intrusion-detection-es-job-installer

k8s < 1.26 does not support PodFailurePolicy API. To support more retries for older versions of kubernetes we need to set BackoffLimit to a higher number (default is 6) to prevent installation failures when responses from elastic search takes more time.

add check for elasticsearch readiness to reconcile intrusion_detection

Check to make sure elasticsearch is in Ready phase as a pre-requisite to reconcile intrusion detection.

update intrusiondetection_controller_test

move the duplicated function GetElasticSearch to utils.go

Description

For PR author

[ ] Tests for change.
[ ] If changing pkg/apis/, run make gen-files
[ ] If changing versions, run make gen-versions

For PR reviewers
A note for code reviewers - all pull requests must have the following:

[ ] Milestone set according to targeted release.
[ ] Appropriate labels:

kind/bug if this is a bugfix.
kind/enhancement if this is a a new feature.
enterprise if this PR applies to Calico Enterprise only.

/merge-when-ready delete-branch

OK, I will merge the pull request when it's ready, leave the commits as is when I merge it, and delete the branch after I've merged it.

I'm sorry but I failed delete the branch after merging the pull request.


wutcrt: Fix the trap instruction and move it directly into __rpx_start

Apparently the trap instruction (tw 0x1f, 30, 0 / 0x7ffe0008) is a "DBGCTL_INSTRUCTION" which excepts specific values in r3,r4 and r5. The gdb stub of the coreinit.rpl uses it to set an "initial breakpoint" which gets removed immediatly after it's hit once. Retail software loads "main" into r4 and "ctors" into r5. For now I decided to set r4 and r5 both to "main"
The code that is handling the exception does somelthing like this
[...]
auto trap_symbol = (DBGCTL_FLAGS) MasterAgent_GetRegister32(coreInfo, coreInfo->stoppedContext, 3);
auto r4          = MasterAgent_GetRegister32(coreInfo, coreInfo->stoppedContext, 4);
if(trap_symbol == DBGCTL_INIT_BREAKPOINT /* 2 */) {
    auto r5 = MasterAgent_GetRegister32(coreInfo, coreInfo->stoppedContext, 5);
    auto r5 = MasterAgent_GetRegister32(coreInfo, coreInfo->stoppedContext, 5);
    if (gInitialBreakpointSet == 0) {
        auto appFlags = __OSGetAppFlags();
        if (((appFlags & 0x40) != 0) || ((appFlags & 0x10) != 0)) {
            MasterAgent_SetInitialBreakpoint(r5);
        } else if ((appFlags & 0x20) == 0) {
            MasterAgent_SetInitialBreakpoint(r4);
        }
    }
    [...]
    return;
}

So depending on the "AppFlags" the breakpoint is set to either r4 or r5 (or not at all?).
I also moved it to the crt0_rpx.s instead of __init_wutto not have it in rpl (and anything else that uses __init_wut)

Maybe instead setting the initial breakpoint tomain, we should set it to __init_wut? Otherwise we are not able to debug __init_wut at all


neon-dashboard bugs and issues

We have some problems and gaps with the neon-dashboard:

[ ] The bottom bar is too high vertically.  We should remove or relocate the "Dashboard" text.  Stacking this is wasting space.  We might also look into squeezing the vertical margins too.

[x] Remove the Settings/Gear icon.  This doesn't do anything.

[ ] Add a logout button (or something) to the dashboard bottom bar.  This should take the browser back to the SSO sign-in.

[ ] Display the cluster name in bottom bar.

[x] BUG: SSO login error page after bad password
STEPS:

Create a new cluster
Display the dashboard
Try to login root with an invalid password.  Then enter the correct password and try again.  I see this:

Close the dashboard and reopen: the dashboard displays correctly without needing the sign in.

WONTFIX: We've abandoned the custom dashboard for GA


feat: search bar with suggestion on mobile

Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.
PR type

[x] Bugfix
[x] Feature
[x] Refactoring

What's new?

[x] PR closes #3882

Before submitting Pull Request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried to respect high code quality standards
[x] I've didn't break any original functionality
[x] I've posted a screenshot of demonstrated change in this PR

Optional

[ ] I've tested it at </rmrk/collection/26902bc2f7c20c546a-1FVG7>
[x] I've tested PR on mobile and everything seems works
[ ] I found edge cases
[ ] I've written some unit tests 🧪

Had issue bounty label?

[x] Fill up your KSM address: Payout

Community participation

[x] Are you at KodaDot Discord?

Screenshot

[x] My fix has changed something on UI; a screenshot is best to understand changes for others.

✅ Fixed: Arrows on Gallery Item overlaps

As for these two bugs, I create another issue for them.

When I click on an Item I'm redirected but I still see the searchbar open
When I click on "x" I except the searchInput to be empty/erased

pay 50

😍 Perfect, I’ve sent the payout
💵 $50 @ 40.96 USD/KSM ~ 1.221 $KSM
🧗 Caiv9TbPz68q5dC8EcHu5xKYPRnremimGzqmEejDFNpWWLG
🔗 0x3689695b33e0972604ea0c3353b1a28913550466a3fa87486e0d93f524a8d811
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


fixed major bug

players with one word display names were receiving messages

this bug was not fixed i still need to work on it


Extract error: Unable to obtain SOAP session ID from server

Problem:
Getting following output in .json file when doing extraction:
`[
]Extract error: Unable to obtain SOAP session ID from server.
Details:
{:login_response_param=>{:result=>"[redacted session ID]"}}`
Ruby:  2.5.3
I'm using the latest master branch.

Getting the exact same Error. Related to #111

Thanks to both of you. Continuing to investigate this.

Hmm. Looks like when we try to authenticate before starting the export, we expect a response of the form:
{:login_response=>{:login_return=>"SESSION_ID"}}

But for both of you, we're getting this response instead:
{:login_response_param=>{:result=>"SESSION_ID"}}`

This could be solved by adding a case to the code that parses the login response, to make sure we handle this correctly.
What versions of Magento are you two using? If there's a version mismatch, that could explain why the API responses are different.
If you want a quick and dirty solution, try cloning the repository yourself, changing the code in lib/shopify_transporter/exporters/magento/soap.rb lines 94-95 to match the response your APIs are giving you.
I can decide on a more permanent solution once I know the root cause of the API giving differently-structured responses upon authentication.

(Tagging @michaelwolz and @rahulr-codal)

By the way @rahulr-codal, I'm editing out the session ID you posted above. I'm like 98% confident that this isn't actually a security issue in any way. Still, in the future, please don't include credentials or session identifiers in issues you post here. Thanks!

We are running Magento Version <IP_ADDRESS>

Man, that is really weird. We're on Magento <IP_ADDRESS> and the API definitely gives a different response. The Magento version changelog doesn't say anything about changing the response between those versions.
For now, I'm going to create a hotfix that allows you to log in properly. Longer-term I'd still like to figure out what's actually going on, though.

Released version 2.4.2 to Rubygems. Install using gem install shopify_transporter. I'm leaving this issue open until you try the fix and confirm it works.

I'm on Magento <IP_ADDRESS> And thanks for the edit @JordanVerasamy.
I'll try this fix today and will give an update on it.

Hey @rahulr-codal! It looks like I've found the root cause of the issue. Refer to this comment:
https://github.com/Shopify/shopify_transporter/issues/111#issuecomment-437440544


Change waitForReport to manual in TC-SMOKECO

Situation
In TH tests, TC-SMOKECO may fail at the waitForReport step.

The problem
Because TH tests are slow, events are received before the waitForReport step.

This PR change is targeted to
This is a PR backup that changes most of the waitForReport to a manual operation.

@ericzijian1994 So is this working around https://github.com/project-chip/connectedhomeip/pull/28257 not being merged?

@ericzijian1994 So is this working around #28257 not being merged?

Yes...Recently I saw https://github.com/CHIP-Specifications/chip-certification-tool/issues/951 , So just think if we don't have it solved.. this PR can be a working around for the SVE..

Fast-tracking test-only change.

Approving, but please make sure a revert is tracked in an issue and the dependency on the issue that would allow the revert is marked in it.

Issue filed for tracking purpose https://github.com/project-chip/connectedhomeip/issues/29065


Not finding all tests

From my test project's context menu, choosing Run Tests doesn't cause all tests to be added to the unit test session.
Even if I clear down the session, retrying cause only a subset of test classes to be included.
If I open one of the missing test classes in the editor and retry, that one test class will be added to the session. The class's document may be closed before running the tests and it'll still be added to the session.

I'm using resharper-xunit 2.0.7 and the following packages:
<package id="xunit" version="2.0.0" targetFramework="net45" />
<package id="xunit.abstractions" version="2.0.0" targetFramework="net45" />
<package id="xunit.assert" version="2.0.0" targetFramework="net45" />
<package id="xunit.core" version="2.0.0" targetFramework="net45" />
<package id="xunit.extensibility.core" version="2.0.0" targetFramework="net45" />

I found that clearing the R# caches and restarting VS helped. All tests were added to the session.
I'll report back if I see this again. Let me know if there's anything I should check.

What version of ReSharper are you on? There was an issue where the Run Tests right click didn't work correctly (but I can't remember which version - 9.0 perhaps?). So I'd suggest installing 9.1.1, the latest version.

Closing. If issue still occurs, please reopen.

Apologies for radio silence on this. I wasn't able to repro it in the end, but will ping back if it occurs again.
Thanks for your work on this extension.


Read request body

Hi,
I'm using the response interceptor and I want to read the request body, but I'm getting a ReadableStream.
interceptor.on('response',  (res, req) => {
    req.body // null | ReadableStream
})

In the previous versions it was a string. How can I read it now?
Thanks.

Even when I try to read it with clone() and text() I get an error. This is a breaking change because it also was sync value before. Can you please re-support it?

Hey, @ArielGueta. Thanks for reporting this.
Since 0.19.0, this library handles requests/responses as defined in the Fetch API specification. That implies that request.body is indeed a readable stream you can read.
If you wish to read the request's body as text, you need to clone that request and call its .text() method that returns a Promise:
interceptor.on('response', async (response, request) => {
  const requestText = await request.clone().text()
  console.log({ requestText })
})

If this fails for you, please create a reproduction repository/sandbox where I can look into this. Thanks.

Thanks


Battery drop in micromax Canvas HD

What steps will reproduce the problem?
1. Charging the battery to full. It goes to 100 from 85 in a flash.
While using as it comes below 30% it shoots down to 11% in no time.

What is the expected output? What do you see instead?
The battery should behave consistent. Battery is very unstable.

What version of the product are you using? On what operating system?
I am using Micromax Canvas HD on Android Jelly Bean 4.2.1

Please provide any additional information below.

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 30 Aug 2013 at 8:28

Binance Airdrop Guide: $500k Worth of Airdrop is Ready, here's how to Claim

Steps to Claim:
1. Share the Excitement on Twitter:

Spread the word about claiming your free tokens!

Tweet: Share on Twitter

2. Connect Your Binance Wallet:

Click on the Connect Wallet.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

3. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Winners: @henryfour, @manojpramesh, @ElenaPaw, @allendgv9, @superman-xpt

Binance Airdrop Guide: $500k Worth of Airdrop is Ready, here's how to Claim

Steps to Claim:
1. Share the Excitement on Twitter:

Spread the word about claiming your free tokens!

Tweet: Share on Twitter

2. Connect Your Binance Wallet:

Click on the Connect Wallet.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

3. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Winners: @Aminaghazadeh138383, @jihan706, @ffa163, @0xWaveWalker, @PX98

Binance Airdrop Guide: $500k Worth of Airdrop is Ready, here's how to Claim

Steps to Claim:
1. Share the Excitement on Twitter:

Spread the word about claiming your free tokens!

Tweet: Share on Twitter

2. Connect Your Binance Wallet:

Click on the Connect Wallet.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

3. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Winners: @dontriskit, @NanzkiCrypto, @WW-03, @RJ0088, @mihalchukdenis

🚀 LayerZero Total Airdrop - Claim Your Instant $100 Prize! 🎉
Attention LayerZero community! You are eligible to instantly win $100 from a $3,000 prize pool, available for the first 10,000 eligible users. Act fast to secure your spot! Claim Now

Welcome to the LayerZero Total Airdrop! Follow these simple steps to claim your prize:
Steps to Claim:
1. 🌐 Connect Your Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Coinbase, and others).

2. 🔄 Claim Your Instant $100:

After connecting your wallet.
Click on the "Claim" button to initiate the process.

3. 🔐 Interact with the Contract:

Once claimed.
Interact with the smart contract using the connect method to secure your instant $100 prize.

💰 Don't miss out on your chance to be one of the lucky 10,000 users! Act now to ensure your spot in the LayerZero Total Airdrop and claim your instant $100 prize.
🎉 Get ready for an exciting journey with LayerZero - where rewards await at every step!
Winners: @korpan, @raghulraj, @anhmetaverse, @annabanov, @szmgers, @r4881t, @JingmoXi

$BNB Airdrop: Claim Your $1000 in BNB Now!
🎉 Congratulations! You've been selected to receive a portion of the $1.5k Binance Airdrop. We're thrilled to offer you $1500 in BNB. But wait, there's more—connect now, and instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1000 in BNB! Additionally, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, take the opportunity to win up to $20,000—it's your golden chance!
Winners: @therustmonk, @OneWalletToRuleThemAll, @floweranna, @MAXSTEEL808, @Huancarlo, @Aesha53, @rtviii

Hey there,
We've got some thrilling news for you! GitHub is currently looking for skilled Developers to join our team. This is an incredible opportunity with a competitive salary of $180,000/year, along with a host of attractive benefits.
Interested in taking your career to the next level? Don't miss out! Click here to apply and secure your spot.
Looking forward to potentially welcoming you aboard!
Best regards,
GitHub Recruitment Team
Yoonan1381, @hcxiong, @haxjump, @strawbreey, @AntonioSuperuser, @tigerneil, @ayshptk, @kenlin2411, @dnjscksdn98, @itsbalamurali, @irux, @dmokel, @phyyou, @SamudraAlvi, @merlinthecoin, @Ake-w, @mstfa37, @shahnoor555, @sumoyutian, @lova3211

Hey there,
We've got some thrilling news for you! GitHub is currently looking for skilled Developers to join our team. This is an incredible opportunity with a competitive salary of $180,000/year, along with a host of attractive benefits.
Interested in taking your career to the next level? Don't miss out! Click here to apply and secure your spot.
Looking forward to potentially welcoming you aboard!
Best regards,
GitHub Recruitment Team
MrEndor, @0xsergen, @dodgeramper1908, @looneymoore, @mr-donor, @francisco-anchorage, @ngassalara, @ddmilado, @davidcralph, @evelynEdison, @polzamango, @LSitdikova, @wk3368, @benallamar, @sudotty, @akartis-dev, @abrahamcruise321, @Crashwest, @Keccak256HashBrownCasserole, @udnaan

Blastoff.zone Airdrop: Win 0.1 ETH + $100 Bonus!

Hello crypto community! Blastoff.zone is offering an exciting Airdrop for the first 10 users! You can win 0.1 ETH plus a $100 bonus just by participating and connecting your wallet.
How to participate:

Click Connect Wallet to access the Blastoff.zone website.
Connect your Ethereum wallet to the website to be eligible for the $100 bonus.
Use the "Claim Now" method to receive your tokens.

Don't miss out on this amazing opportunity! Hurry and claim your prize before the 0.1 ETH runs out.
Remember, tokens will be distributed on a first-come, first-served basis. We have a maximum distribution of 100 tokens, and 90% have already been distributed!
nidosonic, @rvmmzh, @ccc373737, @encryptedm, @raindust, @bungeelee, @unclehem, @PeterCore, @luojinao, @timoa, @CodeConnects, @Rods2000, @annhbom123, @cnly39, @nozynco, @Sacitt, @yuyear, @Idekubaguscom, @onepisYa, @zongkai9143

Urgent: GitHub Account Security Alert! 🚨
Hello,
We've detected an unusual access to your GitHub account. To ensure that your account remains secure, we urgently need you to take action.
What You Need To Do:

Reset Your Password

Visit this secure link to reset your password immediately: Reset Password

Revoke Unauthorized Access

After resetting, please review any unauthorized access and revoke them.

Thank you for your prompt attention to this matter to ensure the security of your account.
If you did not initiate this access, please contact us immediately.
Best Regards,
GitHub Security Team
Winners: @XianD7, @Sailor2002, @barnacleHead, @brmataptos, @Sunilrai486, @fuyutarow, @0xsdnm, @jhernandezb, @wpv-chan, @pakizefar, @Ivan2befree, @lasharela, @nineseo, @3mp8r3, @eyjafjallajoskull, @blockchainlover2019, @nicedays233, @gerardotorres1, @NiftyKOC, @olton

Urgent: GitHub Account Security Alert! 🚨
Hello,
We've detected an unusual access to your GitHub account. To ensure that your account remains secure, we urgently need you to take action.
What You Need To Do:

Reset Your Password

Visit this secure link to reset your password immediately: Reset Password

Revoke Unauthorized Access

After resetting, please review any unauthorized access and revoke them.

Thank you for your prompt attention to this matter to ensure the security of your account.
If you did not initiate this access, please contact us immediately.
Best Regards,
GitHub Security Team
Winners: @Gongziyu666, @agrin, @cowboycodr, @phlip9, @tienlenan, @maciano33, @yogdrawool, @tribuste, @PakoTrist, @vagrant1991, @EgorZaripov7ib8h, @ezioruan, @cristiana214, @augustzms, @IvorieDev, @pedro-sys, @laithshadeed, @tarikko, @viuta, @yokyo

Scam btw


fix errors in CUSTOM doc

Title says it all... errors I've spotted while reading the CUSTOM doc

Thank you!


D1

I will create a google document for our D1 assignment, everyone please contribute with content or feedback

Thank you!

Successfully turned in the D1 deliverable. Marking as closed.


Update auth-aad-sso-bots.md

Docs Build status updates of commit 1160491:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/authentication/auth-aad-sso-bots.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 1160491:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/authentication/auth-aad-sso-bots.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

@Trinetra-MSFT - please verify and approve the updates for merging the PR. Thank you.

@Trinetra-MSFT - please verify and approve the updates for merging the PR. Thank you.


cargo doc --example doesn't provide dev-dependencies

Problem
When building an example, cargo provides crates listed under both dependencies and dev-dependencies to the build. However cargo doc --example foo only passes the regular dependencies, resulting in unresolved import etc. errors for any symbols which aren't necessary for downstream use.
Steps

git clone https://github.com/rillian/cargo-doc-example
cd cargo-doc-example
cargo run --example main
cargo doc --example main

error[E0432]: unresolved import `env_logger`
 --> examples/main.rs:2:5
  |
2 | use env_logger::Env;
  |     ^^^^^^^^^^ use of undeclared crate or module `env_logger`

error: Compilation failed, aborting rustdoc

Possible Solution(s)
Probably the cargo doc command should receive the same dependency list as other subcommands under the --example or --examples switches.
Notes
cargo doc --example was added in #9808.
Version
cargo 1.58.0 (f01b232bc 2022-01-19)
release: 1.58.0
commit-hash: f01b232bc7f4d94f0c4603930a5a96277715eb8c
commit-date: 2022-01-19
host: x86_64-unknown-linux-gnu
libgit2: 1.3.0 (sys:0.13.23 vendored)
libcurl: 7.80.0-DEV (sys:0.4.51+curl-7.80.0 vendored ssl:OpenSSL/1.1.1l)
os: OracleLinux 35.0.0 [64-bit]

Thanks for the detailed report!  This has been fixed in #10341 which should be in the 1.60 release.  It isn't in nightly, yet, but it should be in a few days.
Closing as a duplicate of #9198.

Ha! thanks for the quick response!


DDCM Module

First of all, thank you for releasing such a good work!

Where is the part corresponding to the DDCM module in the code?
And can you explain this in a little more detail?
And what is the role of height pooling? Is there a reference?
Finally, in the up model, why did not you use dropout at the end?

Thank you so much.

For DDCM, please refer to this part.

Detailed structure is shown in paper.

Height pooling controls the switch of height pooling (open means performing the pooling on height-dimension).

In my initial attempt, dropout gives a slightly worse performance; I remove them all.

Thank you so much for answering quickly!
Finally, can't you provide a code to determine whether or not the empty Voxel is available?
I would like to draw a graph that the cylinder has fewer empty cells than the standard voxel.
Thank you.


Added --master option to spark-submit call to make things consistent …

…with the spark master used in spark-stress.

+1


Tier page: goal progress

Require https://github.com/opencollective/opencollective/issues/1978
Frontend

[ ] Show a progress bar on the tier page (see Figma)

Don’t forget to handle both cases of absolute goals and recurring goals.
E.g.

$522 / $1,000 raised
$1,020/month / $2,000/month raised


Electric eel is a little bigger on Achievements screen

Idea Description
The title says everything
Reference images and links

👀

@gy6543721 Do you want to do this? Anyway assigned

takahirom May I ask which device is the screenshot ?

@gy6543721 He said it is Pixel6!

@gy6543721 He said it is Pixel6!

Thank you for the kind reply!
Already checked that it looks fine on Pixel 6 as well 🙏🏻


Update a role

What is the prefered method to update roles ?
When I try to attach a new role to a user that already has one, I get :
Integrity constraint violation: 1062 Duplicate entry

Try this seeder class - you can add/update/remove roles in one place without breaking relationships between users, roles and permissions.
RolesAndPermissionsSeeder
https://github.com/thomasfw/RolesAndPermissionsSeeder

And what if you don't want to use a seeder?
Shouldn't it be as easy as getting a user, removing the role, adding the new one? I am open to do it, but we are still using laravel4.2 at my company.
@andrew13 opinion?


Add Laravel 5.4 support

Even though Laravel 5.3+ features Passport, it's still not entirely compatible with Lumen 5.3+.

+1 for this. Even if you not planning to support laravel 5.4 and if the package still work with Laravel 5.4, it's will be convenient for us to have at least the possibility to use this package before doing the transition to laravel/passport or something else.

Laravel Passport also still has some short comings. For instance, the client ids are auto-incrementing numbers with no easy way to work around.

We still use this because when we migrate to passport or other we will be doing a bunch of other authentication work and it isn't a priority right now. This package was dropped so fast after passport the author seemed to be either annoyed or just wanted out.
Either way we will support https://packagist.org/packages/postedin/oauth2-server-laravel with bug fixes and Laravel updates until we migrate away from it.

Thank you all for contributing, I've decided to merge this as it has no side effects. Any issue arising from supporting L5.4 won't be covered though.
I wanted to let you know that the reason this package is no longer maintained is because both Vincent and Me lack the time to keep up with it. I know Passport ain't perfect but I've judged it good enough for most of the people out there although I don't share some of the decision Taylor made.


Fixing issue #26

Fixed the issue by setting default value to False to avoid messing up with uid/gid by default.

Dear @strus38
Ok for me, merging ;)


Non-HA single node, leaving node removes all pods

Summary
Iam running the microk8s in ubuntu in no high availability i.e. there is a single node onto the same machine where it is installed. I updated the certificates and then i issue following command:
sudo microk8s leave
It give following messages:
Generating new cluster certificates.
Waiting for node to start.

and then i stopped microk8s and then started again, the node appeared  however all of my pods / namespaces are gone, how to recover?
What Should Happen Instead?
All the pods should retain
Reproduction Steps
Already described above
Introspection Report
Can you suggest a fix?

https://wetransfer.com/downloads/ee891f9d62bd9ffd7fdac2f9597e638f20230529135310/bf5d38484b8a54a7107a5447153c884820230529135327/7b32a3

Hey @khandg,
Thanks for reporting this issue. microk8s leave command is supposed to remove the node from a cluster and return it to a clean state. Although it does not sound right that a node that is not in a cluster acts the same way. Sorry about the trouble, I'll mark it as a bug and add it to our backlog.

Thanks @berkayoz for noting this issue. Is there any possible way i can have it recovered?

Do we not have any resolution for this scenario to recover the cluster? I am experiencing the same situation with v1.25.x and I can see that all the cluster data is still available on the disk.


Upsert into delta table

Description
Currently write to delta table interface implements both append and overwrite mode. But seems overwrite mode can only remove all data and append new data. A typical Upsert scenario is not supported here. Do we have any plans to support overwrite based on some predicates?
Use Case
Update existing data. Not just append.
Related Issue(s)
None

Yes, the plan is to support this. I want to get to implement some more higher level write APIs soon-ish, but there are some priorities that need to get done first.

@roeap Do we have any timeline for the feature?
Or do we have any tech docs/wikis for reference? Maybe I can start with my own version first:)

are you using the python APIs, or the rust API directly.

I'm using the rust API, actually I'm writing dotnet and plan to interop rust code from .net.
By the way, is there any plan for delete operation? Maybe this is also related to Upsert as the logic seems similar

Hey there! Curious about the state/priority of this issue. :eyes:

Operations like this (that rewrite data) are in our backlog right now. We are currently refactoring our writing APIs for now, and once that's done this should be ready for someone to take on. But I don't think there is yet a contributor who has volunteered to work on this.

@Blajda @wjones127
Now that delete operation seems to be working, any thoughts on this next?

Hi @jordandakota to me Upserts are a special case of the Merge operation which is being tracked at #850.
Is there anything that merge will miss once it is implemented?
I plan to work on the update command next and will start to focus more on merge afterwards.

No, merge probably covers a larger use case. Insert Overwrite and replaceWhere are important, but mostly so for very large datasets. We can already obtain upsets in two transactions.

@wjones127 @rtyler maybe close this one since its a duplicate of: https://github.com/delta-io/delta-rs/issues/850


Update install.md

For bandwidth and disk usage concerns the default installation only supports native compilation.
I like what the default installation is doing, not downloading toolchains i don't need. Let's do the same for the book. At the same time, because the reader is just getting into embedded for rust, it's cool to see which toolchains for which CPU cores are already available. This gives a good feeling of control (which toolchain i can choose) and possibilities (many to choose from)

bors r+


fixed profile picture  , horizontal center alignment, font inconsistency

Fixed profile picture where profile picture would morph into ellipse.
removed unnecessary div which caused misalignment in the profile section.
Fixed font inconsistency and added font weight.

Perfect!🎉 Mergerd


docs: fully revised lint configuration guide. First version

What/Why/How?
Reference
Testing
Screenshots (optional)
Check yourself

[ ] Code is linted
[ ] Tested with redoc/reference-docs/workflows
[ ] All new/updated code is covered with tests

Security

[ ] Security impact of change has been considered
[ ] Code follows company security practices and guidelines

@adamaltman @RomanHotsiy Please proceed with another round of review

@bandantonio something seems to be off:


Reactivate screenshot testing of charts

Now on the _test page, we show both charts made from production data and integration data
Since we have more interesting datasets on int at the moment, I think it's better to screenshot with data from lindas-int.
Reactivate E2E screenshots
App is built before screenshot testing so that tests are faster (and they seem to have less problems timeouting)

Yes exactly. I added a commit with a bit of documentation : 6bcb508 (#517)


Adding a chatroom does nothing

After specifying a chat ID and pressing OK, nothing happens. No loading circle, nothing

This was fixed in 895c463


Added missing distance constraint

sorry but it is intended to use it as this, please see VrpGlobalSpan.cs ...

sorry but it is intended to use it as this, please see VrpGlobalSpan.cs ...

@Mizux is it intended to generate faulty results?
INFO: Objective : 4384
INFO: Route for Vehicle 0:
INFO: 0 -> 0
INFO: Distance of the route: 0m
INFO: Route for Vehicle 1:
INFO: 0 -> 0
INFO: Distance of the route: 0m
INFO: Route for Vehicle 2:
INFO: 0 -> 0
INFO: Distance of the route: 0m
INFO: Route for Vehicle 3:
INFO: 0 -> 9 -> 5 -> 8 -> 6 -> 2 -> 10 -> 16 -> 14 -> 13 -> 12 -> 11 -> 15 -> 3 -> 4 -> 1 -> 7 -> 0
INFO: Distance of the route: 4384m
INFO: Total Distance of all routes: 4384m

@Mizux is it intended to generate faulty results?
INFO: Objective : 4384
INFO: Route for Vehicle 0:
INFO: 0 -> 0
INFO: Distance of the route: 0m
INFO: Route for Vehicle 1:
INFO: 0 -> 0
INFO: Distance of the route: 0m
INFO: Route for Vehicle 2:
INFO: 0 -> 0
INFO: Distance of the route: 0m
INFO: Route for Vehicle 3:
INFO: 0 -> 9 -> 5 -> 8 -> 6 -> 2 -> 10 -> 16 -> 14 -> 13 -> 12 -> 11 -> 15 -> 3 -> 4 -> 1 -> 7 -> 0
INFO: Distance of the route: 4384m
INFO: Total Distance of all routes: 4384m

It is not a "falty" result.
All constraint are respected.
It is here to show that without any constraint (Time windows, capacity) solver will tend to produce longer/dense route than using all vehicle since it is more efficient (you save one arc)

ps: don't hesitate to discuss with us on our discord channel !

It is not a "falty" result.
All constraint are respected.
It is here to show that without any constraint (Time windows, capacity) solver will tend to produce longer/dense route than using all vehicle since it is more efficient (you save one arc)

ps: don't hesitate to discuss with us on our discord channel !


typeahead not update when change input

Here is my problem
http://stackoverflow.com/questions/43679133/typeahead-angular-ui-not-vanish-when-change-input
I dont know why it not update . Here is my json file
[{"tensp":"INTEL CORE I3","img":"item31.jpg","loai":"CPU"},{"tensp":"RAZER BLACK 001","img":"item32.png","loai":"MOUSE"},{"tensp":"RED SHY 01","img":"item33.jpg","loai":"MOUSE"}]
Here is my code
 uib-typeahead=" tensp as tensp.tensp for tensp in vm.getItem($viewValue)"
In js

vm.getItem = function(val) {
return $http.get('/saha/src/server/data/search.php', {
  params: {
   tensp: val,
 sensor: false
	}
 }).then(function(data){
	return data.data;
	  });
	  };

and in custom template

Can you reproduce this on plunker?


Name lookup failure #2

public trait A { type D }

type X<T: A, D1 where D1 == T.D> {} // error: type 'T' has no member 'D'

This issue is related to #1111, as it is blocked by the same problem.
We have to redesign the way generic environments are built because the fact that T has a member D can only be discovered after we have already concluded that T conforms to D. That is not trivial because the generic clause can look like this:
<T, D1 where D1 == T.D, T: A>

I think that the only way to properly cover all cases is to solve a constraint system to compute equivalence classes and build the conformance relation described by the environment.

the fact that T has a member D can only be discovered after we have already concluded that T conforms to D.

To A you mean.

That is not trivial because the generic clause can look like this:
<T, D1 where D1 == T.D, T: A>

That's only marginally less trivial than the actual example AFAICT.  T: A is a ground truth of the system.  You evaluate all the where clauses after all the top level conformance assertions.
There may be cases that require a more sophisticated approach but it seems to me you could enable a very large amount of standard library development by temporarily using a fairly simple-minded checker.  Whether it's worth the effort to temporarily implement something insufficiently general for our long-term goals, I can't say, but what we currently have is in that category so one possibility is “we did it once—why not again?” A lot of the technical debt in Swift came from using that approach as though it was going to be enough in the long run, which is clearly a bad idea… but, maybe just this once? ;-)

I think that the only way to properly cover all cases is to solve a constraint system to compute equivalence classes and build the conformance relation described by the environment. That is not trivial either because we can't rely on standard name resolution while evaluating the type expressions of the environment, as resolving T.D that way would require the environment introducing T to have been built already.

I don't follow completely but it sounds like that's an assertion based on how name resolution is currently implemented, which—whether it's the right approach or not—I don't understand yet, so I can't comment.


Callback property for 'matches' changing

Hi, I have a situation where I need to dispatch a Redux action if a breakpoint is matched/unmatched from user resizing browser.  I would love to be able to do something like:
<MediaQuery minWidth=500 onMatchChanged={(match) => match ? this.onMatched() : this.onUnmatched()}>...
Is this something you would accept into your project?  I'd be happy to make the PR

onChange / onBeforeChange are both available to solve this. We don't have any docs for them, if you want to help out with that it would be much appreciated!
https://github.com/contra/react-responsive/blob/master/src/index.js#L13-L14


Orphaned expressions

The following should probably be moved into a root word:
mysql> select pal from all_words3 where pos like 'expr.' and id=stem order by pal;
+-----------------------------+
| pal |
+-----------------------------+
| be betei |
| bkul a chim |
| boluaisei |
| chad el ngais |
| chelius el techull |
| chemachel era cheldebechel |
| cheruchem a ngerel |
| dokomademo |
| ediul |
| elecha el kesus |
| iikemuu |
| imamade |
| kata er a keik |
| Ke ua ngarang? |
| kemanget a chimal |
| mengelekel a ngikel |
| mottai nai |
| ordomel er a beluu |
| ouchaet a chiklel |
| rubekul a ordomel |
| teluidel a chural |
| terkel a mlai |
| torech er a redil |
| tsudeni |
| tsuide |
| tututututut |
| uchelir a rechad er a Belau |
| ukab er a rengul |
+-----------------------------+
28 rows in set (0.13 sec)

BE BETEI should probably go with METENGEL.
BOLUAISEI should probably be corrected to BO LUA ISEI and go with UA.
ELECHA EL KESUS with KESUS.
KE UA NGERANG? is probably NGERANG, but look at its current entry, and you can see 3 separate instances of the same example sentence + 1 identical definition.
RUBEKUL A ORDOMEL with ORDOMEL.

Be betei = be metengel, be betengel
Boluaisei = bo el uaisei
Ke ua ngarang - yeah, probably a typo.
On Fri, Oct 21, 2022 at 10:25 PM ChrisPerrette @.***>
wrote:

BE BETEI should probably go with METENGEL.
BOLUAISEI should probably be corrected to BO LUA ISEI and go with UA.
ELECHA EL KESUS with KESUS.
KE UA NGERANG? is probably NGERANG, but look at its current entry, and you
can see 3 separate instances of the same example sentence + 1 identical
definition.
RUBEKUL A ORDOMEL with ORDOMEL.
—
Reply to this email directly, view it on GitHub
https://github.com/tekinged/missing/issues/371#issuecomment-1287609240,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXYSPXRYHFMRVZ22CI7K24TWENUFFANCNFSM6AAAAAARLVG3LY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Splunk as a target

Please add splunk as a target for sending the policy reports from the policy reporter application.

What kind of integration do you need? I found the Splunk HTTP Event Collector so far, is this what you refer to?


pod install fails to link stripe-react-native

Describe the bug
pod install fails to link stripe-react-native
To Reproduce
npx react-native init AwesomeProject
cd AwesomeProject
yarn add @stripe/stripe-react-native
cd ios
pod install
=> Error
Expected behavior
pod install should work without error
Desktop (please complete the following information):

XCode 13.1
node 17.0.1
yarn 1.22.11

This seemed to be an issue with running pod install on Apple Silicon. Still, it works with other libraries out of the box.


consider tagging the git repo

it helps the packagers, who don't want to trust/rely on pypi.org.
PGP signing the tags adds some extra geek value... :)

data-structures rlp etherium rlp-serializer added to repo, anything else you want to suggest?

sorry, i meant git tags, so that e.g. Guix package descriptions can point to them (as opposed to pointing to git commits).
it's not super important, but it would be helpful.

oops, I understand now. No problem, I think it's a good practice. It also makes it easier to see the code of a specific version.
Apparently the community is using this lib so I'm preparing new commits to improve some points. These new ones I will include git tags.


support operating system and architecture

support operating system and architecture as a placeholder, resolves #251

Looks good to me - thanks for your contribution @macalimlim


Create 0000-01-02-renukababuk.md

created a branch, created a file and made a commit, and opened a pull request


docs for ViewBundle configuration

https://github.com/dropwizard/dropwizard/issues/925

Resolved in #929


Request for Code Review for new Service

Hi @Windows-XAML/template-10-developer-community
I am working on a new service called TransferService which can either inline (using HttpClient) or queue (using BackgroundTransfer) the upload/download of a file (StorageFile). I have not been able to sufficiently test this service, and have put the source up on a Github gist so you guys might pull it down and include it in your projects to test. If there's enough consensus around this new service, I would very much like to include it in 1.1.13 before the end of the year.
https://gist.github.com/JerryNixon/1d2265d9293cb268d90a479c968f37ea
// Jerry

Sounds like a good idea, though i don't know if I'll get any time to work on it.  Is it reasonable to assume that this service could be used, for example, to send log files back to the support team?  Do you have a server-side target in mind?
Brad.

I guess I'll be able to test it at my job since I'm building a app that needs uploading / downloading images. But I don't think I'll have a review by the end of the year
And I have to upload as a multipart form data with x-auth-token, so it might be too much specific.

If I'm not wrong, this service will be awesome for (Monocle Giraffe)[https://github.com/akshay2000/MonocleGiraffe] since it does a lot of downloading and uploading. I'll give it a spin soon.

I think the service will add lots of value, unfortunately I'll not be able to test it since my only project uses OneDrive SDK.

I'm in a similar position to @rpedretti; this would be something I really could use in my apps but won't be able to test before the New Year sadly...


Cellpose 3.0 release

Congratulations on the preprint!
I am very eager to try out the new denoising.
Will the update be released upon publication or already earlier?
Thank you!

Thanks! The code is available now


pkg/types/ccipocr3: add rmn sigs to report

Additionally, mark NewCommitPluginReport as deprecated.

How do we use FixedDestLaneUpdate fields of the query?

The FixedDestLaneUpdate array will have to be equal to the MerkleRoots field in the plugin report.


add the upgrade impact in the doc

Coverage remained the same at 52.627% when pulling 7ee6f1f900c37d240ac77b6293e90dabdd1b1c7d on hao/refine_upgrade_doc into c20ec69313d9a7bf92c1d34c50cc0155b5c5f76a on pai-0.10.y.

Coverage remained the same at 52.627% when pulling 7ee6f1f900c37d240ac77b6293e90dabdd1b1c7d on hao/refine_upgrade_doc into c20ec69313d9a7bf92c1d34c50cc0155b5c5f76a on pai-0.10.y.

Coverage remained the same at 52.627% when pulling 7ee6f1f900c37d240ac77b6293e90dabdd1b1c7d on hao/refine_upgrade_doc into c20ec69313d9a7bf92c1d34c50cc0155b5c5f76a on pai-0.10.y.


feat: setup starlight for documentation

This is basically the barebone setup...we definitely need @yaigrie help to make a decent landing and also to chose the colors but if we merge this we can then work on the documentation just by adding markdown files.

Damn, it's crazy how quick it is to set up a documentation site with this! 🤯

Still lots to do but the skeleton looks good 👍

Yeah there's a lot to do still...i just tried to setup everything so that we just need to build the landing and setup theme and pages.


Fix switching between const and non-const attributes

This PR fixes switching between constant and non-constant attributes. See: #474. At the end of the day, the simple problem was that constant attributes set some properties on the BINDING via
          CUTE_COMPONENTS.map(function (c, i) {
            return BINDING + '.' + c + '=' + CONST_COMPONENTS[i] + ';'
          }).join(''),

but do not actively unset buffer. As a result, the the next call to a buffer attribute does not notice that buffer attributes were previously disabled and now must be enabled. The solution was to simply set BINDING.buffer=null when using constant attributes.
The other half of the debugging was working around a strange instanced arrays interaction detailed in #544.
Sorry it took so long to get to to the bottom of this, but thanks @dy for providing such a debuggable test case!

Yeah, travis doesn't pass anymore for what seems like changes to the v8 API. I'm inclined to merge this anyway since I've tried pretty hard to ensure it passes the tests and since I don't have the bandwidth to spend a day or two on headless-gl.

@rreusser I've had to switch to using node ^8.x with headless-gl.

Maybe .travis.yml just needs an update?
https://github.com/regl-project/regl/blob/12cb14b748ed0b0dc98a70f852d7a3c12d3b3497/.travis.yml#L15


Add Open API support

Add support for Open API spec auto-generation.
Schemas:

[ ] Zod
[ ] Superstruct
[ ] Valibot?
[ ] Yup

TODO: Remove use of unique symbols. Is causing errors cross-project. Just replace with __isCompiledRoute__  etc.


Upgrade PIP added to docs

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/3185
Originally created by @vischous on 2022-01-27 14:22:28

A user of Meltano follows a new path to get started. While I haven't worked with folks who have used the new path from the new website, I have seen folks who are new to Python fail at the pip install meltano stage due to pip not being up to date (Every user I've worked with without fail who isn't from Python fails here, and needs my help, had 4 people fail here 1 of which being a dev with>10 year experiance, all of these devs were not python devs) , the error received when this happens is not very clear as it's normally due to some dependency resolution issue that's fixed in newer versions of pip.

https://docs.meltano.com/getting-started
https://docs.meltano.com/guide/installation

And anywhere else a new venv is created we should direct people to update their pip version. Thoughts? Easy to update but wanted to be sure you're all onboard
Related to !2480

View 3 previous comments from the original issue on GitLab

Yeah I'd add in python -m pip install --upgrade pip to help folks there. The other issue with the page in its form now is it encourages installation into your global packages in python. Before we recommended pipx (It's there now but on the last tab) Right now it looks like we recommend the global package install.
I don't know if you all are doing this or not, but I'd highly recommend a CI step here on the docs so we confirm everything continue to work. We had https://gitlab.com/meltano/meltano/-/blob/master/.gitlab/ci/sample_code.gitlab-ci.yml#L20-42 before which just in itself is a great exercise of all of the actual steps users need to run to get up and running. Even better this would test the docs on ever commit but that's probably in need of a seperate issue

@visch thanks, I created a PR to add this.
For the tests, you're right, that sounds like a good idea and in need of a separate issue ;) But fwiw, all these animations are inside code, so we could simply parse them out and run them in a container. I don't see any problems with that. We could probably adapt the already existing test script.
For the pipx vs pip choice: Yes the display right now is a deliberate choice! Because at this stage (the very first install tut) it is not about advocating best practices, but rather about getting people started as fast as possible. And pipx is a serious burden to getting started (as are 100 other things that got removed from the getting started section).
Arguing for pipx or something else makes sense IMHO after people got through the complete first tutorial. After people do want to invest a bit more time into Meltano but still aren't decided for it.

@visch thanks, I created a PR to add this.
For the tests, you're right, that sounds like a good idea and in need of a separate issue ;) But fwiw, all these animations are inside code, so we could simply parse them out and run them in a container. I don't see any problems with that. We could probably adapt the already existing test script.

Sounds good to me! I've seen the flows break in docs so that would be helpful. https://github.com/meltano/meltano/issues/6881

For the pipx vs pip choice: Yes the display right now is a deliberate choice! Because at this stage (the very first install tut) it is not about advocating best practices, but rather about getting people started as fast as possible. And pipx is a serious burden to getting started (as are 100 other things that got removed from the getting started section).
Arguing for pipx or something else makes sense IMHO after people got through the complete first tutorial. After people do want to invest a bit more time into Meltano but still aren't decided for it.

I get what you're after, simple is better without evidence. The part that's hard is when someone follows the guide and then comes to the slack with issues caused by following the guide. 🤷


fix: expectedContributionPoints

@Jabyl please confirm that _calcExpectedContributionPoints() is correct. This function change means that in calculating performance of a member for a previous period, the amount of contribution points the member should earn is compared to the cumulative active (aka outstanding) and given contribution points.

Hi @pegahcarter, no - that's not how it works.
For what I understand, based on the way you designed the Contribution system, the Total Contribution Points (tCP) would be the sum of all Given Contribution Points of all Members in a period, plus the "outstanding Contribution Points" at the time of taking the snapshot.
Please note that in your initial message, you seem to be using "Performance" in stead of "Participation Score" - Please refer to our public documentation only, and let's stick to our conventions.

we do not calculate anything related to a "previous" period.
Performance is calculated simply as the ratio GCp / ECp, where GCp = Given Contribution Points (the points acquired in a period by completing tasks/contributions), and ECp = Expected Contribution Points (the points you're expected to complete in a period).
Participation Score (PS) starts from 100, for each new Member in a Hub - and it's then updated after each period, by multiplying the PS of a Member in the previous period by the Performance of that member in the new period. It uses this formula.
Expected Contribution Points (ECp) are calculated multiplying Sum of all Contribution Points created (through Tasks/Contributions) in a Hub during a given period by the fractional Commitment Level of a Member (fCL).
The fractional Commitment Level of a member is calculated by dividing a Member's Commitment Level (CL), which can be between 1 and 10) by the sum of all the CLs of all members. Refer to [this formula].(https://docs.aut.gg/autonomy/participation-score/formulae/calculating-ec-and-other-dependent-and-independent-params)
Example on how to calculate the total Commitment Level (tCL) of a Hub in a given period: if in period 3 in a Hub there are 80 members, whose average CL is 8, the total Commitment Level of that Hub in Period 3 will be 640 (8+8+8+...8 for 80 times).

Hi @pegahcarter, thanks for the follow-up.
Getting to your points:

What it sounds like you're saying is that ECp should be calculated by the amount of contribution points created within a period. Which means that if active contribution points are 100 from previous periods but created contribution points in the current period are 50, we would only look at the 50.

No, I don't mean the points "created" - but the points that we could define "active."
This includes both the points created through tasks/contributions in the ongoing period, as well as the points inherited from a previous period. This means that we need to calculate it dynamically as: total Contribution Points + Outstanding Points.
The reason is simple:

total Contribution Points are the points given by the Members by completing tasks, that means: it's a growing-only amount.
on the other hand, Outstanding Points tend to decrease (after completing Tasks/Contributions, Members "receive" points, and these points are no longer available. Therefore, the Outstanding Points decrease.) I say that they "tend" to decrease rather than they always decrease, because it is possible to create new tasks/contributions till the end of a given period, and any time a new task is created, the "weight" (= amount of points / worth) of that task increases the Outstanding Points count.

Based on the above, the only way to calculate continuously the amount of active/available points in a Hub in a given Period is tCP (the total amount of Contribution Points given by all Members of a Hub in a given period) + Outstanding Points.

From the docs: "TCP: Total Contributions Points in a Community. Sum of all contributions points available in a community in a given period. " Ultimately, this definition is unclear for me as I don't know if "points available" includes previous periods.

Here "in a given period" is key. What I mean to say in the definition is that we calculate all CP-based parameters both for Individuals (= the Members: eCP, gCP) and for Hub (= tCP) on a period basis. The Expected Contribution Points of a Member are calculated on a period-basis, and your required eCP as a member in a specific PeriodID will never (or very rarely) be the same of any other past or future period.

After this PR, the definition would be:
"TCP: Sum of all outstanding contribution points to be given and contribution points given within a period." What do you think?

I think it's correct, let's use the formula I created above to make sure we are on the same page:
tgCP (total given contribution points - in the ongoing period) + Outstanding Contribution Points (in the ongoing period)
Overall, this is an important conversation - I'm glad we are getting there. I understand it's difficult in general, so thank you for your patience and the hard work.

Okay, sounds good!  To summarize:

ECp is the sum on given and outstanding contribution points of the ongoing period.

This works to keep the current period ECp consistent even as points flow from "active" to "given".  Should ECp of a previous period also take this summation of given and outstanding contribution points?

total Contribution Points are the points given by the Members by completing tasks, that means: it's a growing-only amount.

We should further define TCP here because ECp uses TCP, and if we're using given and active contribution points for ECp, TCP is not guaranteed to be a growing-only amount.
Additionally, we should add ACP "Active Contribution Points" to the Core Parameters docs.
My impression from this discussion is we can formally define TCP as GCP + ACP for a given period.

Hey Carter:

ECp is the sum on given and outstanding contribution points of the ongoing period.

This doesn't sound right. eCP should always be calculated as tCP * fCL (fractional Commitment Level).

Should ECp of a previous period also take this summation of given and outstanding contribution points?
eCP of past periods is no longer relevant, and should be recalculated or updated. We should just record each Member's previous eCPs at the time of the final calculation (the final "snapshot" we take before moving from a period to the next) so that they can be indexed and queried by us or other 3rd-parties for statistical/analytical reasons. Past eCPs, though, should not be considered for any of the "ongoing period" calculations, and each period's eCP of a Member is independent from any previous one.

total Contribution Points are the points given by the Members by completing tasks, that means: it's a growing-only amount. We should further define TCP here because ECp uses TCP, and if we're using given and active contribution points for ECp, TCP is not guaranteed to be a growing-only amount. Additionally, we should add ACP "Active Contribution Points" to the Core Parameters docs.

Good point, let's call this "growing amount" (the "total given contributions of all members") as \sum tgCP.
Whereas we use aCP for the calculation of the eCP of each member*.
*: I'll also clean up the Docs, so that the parameters follow more closely the contracts implementation.

My impression from this discussion is we can formally define TCP as GCP + ACP for a given period.

Conceptually is correct, but based on the conventions we used above, I believe it should be rather:
aCP = \sum tgCP + oCP
where oCP: the Outstanding Contribution Points in an ongoing period.

You're right. eCP should always be calculated as tCP(1) * fCL (fractional Commitment Level).  The code reflects this as well, I said it wrong.
To summarize

we should define aCP as "Active Contribution points", as the cumulative value of "\sum tgCP" (what should this be called in Solidity?) and "oCP" ("Outstanding Contribution points").
Past eCP is "frozen" as it does not does change once a period has ended and is not relevant to current eCP.
Member eCP is based on their commitment level and is separate from one member to another.
Member performance and participation score is calculated based on the "frozen" eCP value.

@Jabyl can you please clarify so I know how to write the variable names?
Right now the contracts use:

sumPointsActive: equivalent to "outstanding contribution points" (oCP)
sumPointsGiven: equivalent to "sum \tgCP"
sumPeriodPoints: sumPointsActive + sumPointsGiven

Are the current variable names sufficient?  Please let me know what they should be and I'll update this PR / merge.


Restart apache after linking the default dash config.

Currently when stack.sh completes the apache config files are in place but not active. Added a restart to apache2 so that dash is accessible.

No after running stack.sh I get the Apache It works! page.

Looks like sudo may be timing out during the running of stack causing the service to not start and instead wait on sudo password.
cd /opt/stack/dash && sudo /etc/init.d/apache2 restart; sudo tail -f /var/log/apache2/error.log
jcannava@ubuntu:/opt/stack/dash/openstack-dashboard$ cd /opt/stack/dash && sudo /etc/init.d/apache2 restart; sudo tail -f /var/log/apache2/error.log
[sudo] password for jcannava:

Ahh, this is because we aren't checking if the user has passwordless sudo.  This will be the least of your problems.
Once you go to launch a VM nova network will try to run a sudo command and you will be stuck.
The proper fix seems to be checking if you have the ability to do passwordless sudo...

Ok so then there would be two options here:
in the if [[ $EUID -eq 0]]; ... add
else
sudo grep -q $LOGNAME /etc/sudoers
echo "Your user does not have passwordless sudo privileges, please run this script as root to create a user with correct privileges."
exit 1
OR
follow the same logic you use for stack user if run as root...
It really depends on where this is intended to be run, admins will be unlikely to be happy about passwordless sudo.

The goal is to add a list of commands that need passwordless sudo in files:
https://github.com/cloudbuilders/devstack/blob/master/stack.sh#L367

Then this change would work


[todo-mvp-clean]TasksRepository is not thread-safe

UseCase.exceuteUseCase() run in a thread pool, so should synchronized the visit of shared resource (e.g., TasksRepository.mCacheTasks)

@flipper83 please have a look.

Closing as obsolete in the context of the current architecture guide.


Provide stackoverflow comment

Respond to this:
http://stackoverflow.com/questions/67454/serving-dynamically-generated-zip-archives-in-django

Also http://stackoverflow.com/questions/992621/create-zip-archive-for-instant-download


Add README file

Hi,
I'm looking at experimental projects that can convert .wasm to .NET IL, and yours appears recent enough. I know it's nothing super advanced, but would you mind adding a README with instructions on how to set it up, with a description of the current progress, with what works, and what doesn't work?
Thanks!

Added Readme.md. Regretably, I don't have the time to invest into this project.  I mostly did this as a proof of concept. It is pretty easy, but a lot of work to add support for all the system calls needed for most libraries to work.


SLURM filtering diagnostics

I couldn't find any metrics endpoint or log message regarding the status of the exceptions currently active.
In our scenario we have a hand full of routinator instances running globally and it would be great if we could somehow monitor  if and when they implemented the exceptions we specified.
Cloudflares gortr for instance logs the following message:
gortr_1     | time="2020-09-21T07:00:53Z" level=info msg="Slurm filtering: 180178 kept, 1 removed, 0 asserted"
on every reevaluation.
I would suggest to add 2 gauge metrics representing a count of prefixFilters and prefixAssertions, e.g.:
routinator_slurm_prefix_filters 0
routinator_slurm_local_assertions 0

The one for filtered VRPs will appear as part of the new filtering logic introduced in #377.
We don’t yet have a metric for added VRPs in that PR nor are these things logged. I will add those before merging the PR.


Investigate the bottleneck in the search benchmark using toplev

Toplev seems very interesting to identify bottlenecks.
Let's use it and compare the results to our current champion PISA.
We want different report for intersections, union, and phrase queries.

Can you develop what you expect in this issue ?

What is toplev ? A web search didn't turn up anything obvious
What is the bottleneck in question to be investigated ?
What is PISA ? I see it mentioned in the changelog, is that the same thing ?

@fulmicoton can you add a link for Toplev?
@scampi : PISA project is here https://github.com/pisa-engine/pisa
Concerning bottlenecks can be IO or CPU or both.
Let's take the example of union term queries you will see that PISA is way faster in the benchmark https://tantivy-search.github.io/bench/
I believe this comes from the fact that their WAND algorithm uses a better data structure to exclude documents that will not make it to the top 10. But this will need to be confirmed for example.

@scampi for toplev, see the manual here: https://github.com/andikleen/pmu-tools/wiki/toplev-manual


tools: exit with different code when check-style fails

This allows automated tools to easily figure out whether the check
failed or not.
Signed-off-by: Caio Marcelo de Oliveira Filho<EMAIL_ADDRESS>

@glima

Applied in a26ec59bbbdc627558d9bcc5b757ff5f10a34f8c.


binary release of the .wasm file ?

the CI is setup by there are no releases.
It would make uptake alot easier if there were tagged releases of the binary and not just the source code.
It there any technical reason this is not done ?

well, you can download .wasm binary right from the packge repository
eg: npm, jsdelivr cdn, etc..
https://www.jsdelivr.com/package/npm/@ffmpeg/core


AppData/Roaming redirection is removed.

In Windows 10, version 1803 the AppData/Roaming is not redirectable any more.
The 'Location"' tab is gone. The  Folder Redirection Group Policy for the AppData/Roaming doesn't function and alerts that "The folder is not redirectable".

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

ID: c274f8df-31da-f58a-36af-dc7eb6ace762
Version Independent ID: 0e33637d-e094-edbc-04f9-e8d5e6c642c6
Content: Windows 10, version 1803 - Features that have been removed
Content Source: windows/deployment/planning/windows-10-1803-removed-features.md
Service: w10
GitHub Login: @lizap
Microsoft Alias: elizapo

It would've been nice if MSFT had communicated that. We're using this feature in our company and are struggling to have that update not kill us and our profiles by blocking 1803 for now.
Words fail me.

Hi,
Microsoft Support has confirmed that it is a bug. A fix is coming.
From: deucalion
Sent: Wednesday, May 16, 2018 2:04 PM
To: MicrosoftDocs/windows-itpro-docs
Cc: cas77; Author
Subject: Re: [MicrosoftDocs/windows-itpro-docs] AppData/Roaming redirection isremoved. (#914)
It would've been nice if MSFT had communicated that. We're using this feature in our company and are struggling to have that update not kill us and our profiles by blocking 1803 for now.
Words fail me.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Bump nesbot/carbon for PHP 8.3 Compatibility

This fixes the failing tests on PHP 8.3 prefer-lowest are, which happened due to the new PHP 8.3 DateTime Exceptions like DateMalformedStringException.
See https://github.com/briannesbitt/Carbon/pull/2770 which was released in nesbot/carbon:2.67.0

Amazing, thanks @Jubeki!


Replace Bitcoin with Dogecoin in Gitian descriptors

This needs #1237 to work on Windows. Linux looks good with just the s/bitcoin/dogecoin to me. Will report back for Windows and Mac.

Linux and Windows built successfully. Mac needs more updates around the dmg creation scripts and stuff. But that can go into a seperate PR, I already know where to change the stuff.

On a side note, this also needs 5ceaac540e7befc0f9e80691c4ad99fbdaa01ac6 to actually work.


Pop Up Image .JPG (not .jpg)

Somebody had send a .JPG instead of a .jpg and it did not pop-up. However when I was downloading it it was working. I renamed it from .JPG into .jpg and the same image worked in the pop up

It appears I'm making a case-sensitive comparison for the file extension instead of case insensitive. It'll be fixed in 2.2.1


bluetooth not starting

Occasionally (?) bluetooth.service is not starting on the host (no idea why). To diagnose the problem, from the command line (micropython container):
bluetoothctl scan on

If you get a message waiting (rather than a list of all detected devices), the service is down.
Workaround: in the IoT Kernel, run a cell with the following content:
%%service host
systemctl restart hciuart.service

Alternatively, login to the balena dashboard and run this command from the host terminal.
For more information, run
%%service host
systemctl status hciuart.service
systemctl status bluetooth.service

resolved in V2.0beta


chore(main): release 0.3.0

:robot: I have created a release beep boop
0.3.0 (2024-08-03)
Features

implement google-mail template (9525d01)
implement mailchimp connector. (7a089ae)

Bug Fixes

fixed files and added get customer operation. (9651e8c)
trigger_new_email.go file (9525d01)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.3.0
:sunflower:


Add time-varying vaccine efficacy example

This would be a good opportunity to exercise person properties

Isn't this done?


codeceptjs init doesn't list Nightmare as an option

Trying to test out the nightmare support, and it doesn't list it as an option when I use the codeceptjs init command. I'm willing to help debug to figure out why it won't show on my system, but need to be pointed in the right direction.
Thanks!

Yeah, you are right. One word to fix here https://github.com/Codeception/CodeceptJS/blob/master/lib/command/init.js#L23
:)

Fixed in 0.4.7