Generator option to allow View to have nullable columns

Is your feature request related to a problem? Please describe.
The previous Drift version allowed views that were built from drift files to be nullable, if the column was specified to be null. Now they are all required
Generated from my Drift file.
  late final GeneratedColumn<int> objectNumber = GeneratedColumn<int>(
      'ObjectNumber', aliasedName, true,
      type: DriftSqlType.int,
      requiredDuringInsert: false,
      $customConstraints: 'NULL');

Snippet from View
  IntColumn get objectNumber => attachedDatabase.employee.objectNumber;
Result
  EmployeeViewData(
      {required this.employeeID,
      required this.objectNumber,
 ...

Describe the solution you'd like
I use my views as quick inner joins and manipulate the business logic from there. Its important to store it as a view as the data in the database can change at anytime.
You would make my day by adding a method to allow the column to be nullable in a view DataClass

Hi Simon,
Unfortunately, the repo did not work.
Still required
'EmployeeViewData(
{required this.employeeID,
required this.objectNumber,

'
Kind Regards,
M.Eng Computer & Electronic
FS Eng (TÜV Rheinland, #15376/ 17, HW/SW Design)
On Mon, Sep 12, 2022 at 11:04 PM Simon Binder @.***>
wrote:

You're right, I've unfortunately overlooked this case in drift 2.0.
In 1681c83
https://github.com/simolus3/drift/commit/1681c83bea719f8940d54e5526721eb3b358f4f4
(which is not released yet), there's an updated algorithm to determine
whether columns are nullable in views: When they reference an existing
table coming from an inner join, they're non-nullable. In all other cases,
drift will generate a nullable field in the data class. It's not an
explicit nullability flag which you could control, but hopefully a much
saner default.
You can try out this version by adding this to your pubspec:
dependency_overrides:
drift_dev:
git:
url: https://github.com/simolus3/drift.git
ref: 1681c83bea719f8940d54e5526721eb3b358f4f4
path: drift_dev
If you want to try it out, I'd love to hear your feedback on how well this
works. Please let me know if you're running into any issues with this, I'll
re-open this issue in that case.
—
Reply to this email directly, view it on GitHub
https://github.com/simolus3/drift/issues/2043#issuecomment-1243877661,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABLUKUC7VQHMYNJVFRZSSL3V55BABANCNFSM6AAAAAAQKPT5KA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Thanks for following up. Can you share the definition of the view and references tables so that I can reproduce this issue?

I couldn't fully reproduce your example because it references some imports not available in that archive.
However, adding only the view and referenced tables seems to work for me:  On the latest state of the develop branch in this repository, this repro generates a view with nullable columns.

I have created a project to simulate my issue. I think it is the option generate_values_in_copy_with : false. I tested without the build.yaml and with the option set as true then I also receive nullable columns. With the flag set to false to keep the copyWith Constructor backward compatible it does not go to nullable. I hope this helps, let me know what you think and if I can do anything to assist you.
drift_test.zip

Thanks for taking the time to provide a complete repro! Unfortunately, I still couldn't reproduce this.
I downloaded your second project (drift_test.zip) and re-ran the build. Inside the build.yaml, generate_values_in_copy_with has already been disabled. And yet, all of the fields in EmployeeViewData are nullable and none of them are required.
For completeness, I also ran a fresh build with generate_values_in_copy_with: true. Still, all columns are nullable and none of them are required.
In case anything weird is going on, does flutter pub run build_runner clean help?


Feat: Changing favicon in home page

Describe the feature
I have observed favicon is not visible in home page.
I want to make it clear and visible.
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Hello @harinisayani
Its been a long timee since we heard from you on this issue.
Do let me know how you will improve or what favicon you will insert in place of this.
Happy Coding!! ✨

Hi @himanshu-03
I want to change favicon to the webpage.
Because the favicon is not visible.

Please let me know what is your approach will u be inserting a new favicon or changing the dimensions and properties of the current one?

@harinisayani  are you still interested in working on this issue. If not, this issue will be closed in 2 days.

Hi @himanshu-03,
I want to insert new favicon because the current favicon is unable to visible clearly.

Hi @himanshu-03, I want to insert new favicon because the current favicon is unable to visible clearly. Will you please assign me this issue.

I asked you earlier which favicon are you going to use instead off this

Hi @himanshu-03,
I want to add this logo as favicon.

Sure thing, you can work on this issue.


Virtual Piano

Describe the project you want to add with tech stack
I want implement virtual piano as a new project by using html css and javascript.
Expected behavior
i want create some fun and enjoyable instrument :- Piano
Screenshots (optional)

Additional context (optional )
Hi! I would like to contribute to this issue under the GSSoC'23. It seems interesting and aligned with my skills. I would be happy to take it up and work on this project.@pranjay-poddar

please assign me this issue under gssoc23

@pranjay-poddar @Saurabh-kumar09 @MohitGupta121 Sirs, please assign this task to me to create a pull request and contribute in this repository under GSSoC'23 program


Removing unused import on RCTMultilineTextInputNativeComponent & RCTSingelineTextInputNativeComponent spec.

Summary
This pr removes unused import on RCTMultilineTextInputNativeComponent & RCTSingelineTextInputNativeComponent spec.
Changelog
[General] [Changed] - Removing unused import on RCTMultilineTextInputNativeComponent & RCTSingelineTextInputNativeComponent spec.
Test Plan
@TODO

cc @sammy-SC. because this is spec file for fabric i don't know how to test it. but should be working fine.

@gedeagas thank you!
The change looks good.


Schema::ComponentElementUse#id seems to be missing

Hey!
it seems like Schema::ComponentElementUse#id is missing. If I understand correctly, it ComponentElementUse is a concrete class derived from AbstractElementUse < AbstractUse (which defines id as abstract).
Am I understanding thing correctly, or am I missing something?
Thanks so much for your time!

Hi Nate, I won't have time right now to check into it, but you are probably correct. I never got around to finding a way to enforce (at definition time or in a spec) the rule that abstract methods should be implemented.
But I do have just enough time to say thanks for taking a look, it is appreciated! It's good to have someone review now and again -- some of the code is nearly a decade old, so it really just fades into the background for me! Keep submitting things as you find them, I will have more time later in the week.

Another similar note: Schema::SegmentDef#required?
I'm guessing this one would delegate to @requirement?

Hmm, actually I don't think SegmentDef has a @requirement, because that information only is known when a SegmentUse is created. Maybe this method could throw a more descriptive error message, rather than "required? is abstract" -- like "NoMethodDef: SegmentDef doesn't have requirement inforation".
But skimming the code, I think it's rare (or doesn't happen at all) that required? or optional? is called on a FooDef object. The reason is the requirement value in the corresponding FooUse overrides whatever the definition says. For instance, a SegmentDef might say the 1st element is optional, but when the segment is actually used in a particular place, that element might be required.


Updating UVs on a surface behave differently between v4.1.2 and v4.2-beta3

Godot version
v4.2.beta3.mono.official [e8d57afae]
System information
Godot v4.2.beta3.mono - Windows 10.0.19045 - Vulkan (Mobile) - dedicated Radeon RX 580 Series (Advanced Micro Devices, Inc.; 31.0.21031.1005) - Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz (12 Threads)
Issue description
On v4.1.2 I was working on a process to combine all static meshes (glb) into 1 in order to improve performance. Additionally, each mesh needed to have their UVs adjusted so it could utilize a single material more efficiently. This involved collecting a list of surfaces, adjusting vertices, normals, and UVs, and then adding the surfaces back to a new ArrayMesh.
This had been working fine in v4.1.2, but after upgrading to v4.2-beta3 I noticed all the colors were not correct.
I did notice that once I ticked the "Force Disable Compression" box on the mesh import, that it appears to be working again in v4.2-beta3.
Is this possibly related to bug https://github.com/godotengine/godot/issues/84270?
Left side is v4.1.2 and the right side is v4.2-beta3

I've attached a zip which contains a very minimal project for both v4.1.2 and v4.2-beta3 that only focuses on the UVs. Line 11 is where I'm setting the Scale and Offset for the UV on the mesh.
Steps to reproduce
See attached projects
Minimal reproduction project
godot.zip

Please try beta5, several issues has been solved in the last weeks

Understood, I'll try the updated beta and report back when I'm able.

In the future make sure you have an up-to-date version when making a report :)

This is most likely fixed by https://github.com/godotengine/godot/pull/84159 which is included in Beta4 and Beta5.

I can confirm it is fixed in a later beta. Will close this issue.


setValue(String value) method in TextField component sometimes doesn't work

Sometimes first letter/-s isn't filled. See screenshot

Hello @GurtAlex
Could you share more details about the problem? What version of masquerade is used? What browser (driver) and its version is used?


studyTarget

While working on a first dataset, we noticed that the studyTarget options aren't very extensive. I talked to @lzehl about it and we also noticed that maintenance could become challenging. In short, termSuggestions should be evaluated and grouped regularly, but then all the schemas using the property studyTarget would need to be updated as well with these new groups.
So, we wanted to ask @olinux if it would be possible replace this by a list of all terms (allowed as studyTarget) that is stored somewhere else for better maintenance?
Or, if that is not possible, we may want to consider making the studyTarget its own schema after all. Then we only need to update one place instead of several with the new controlledTerms terminology options.

Also, perfect example for maintenance issues is controlledTerms/cellType. We made changes to the origin in tissueSamples and added this as an option (next to controlledTerms/organ), but oversaw that this should be added as option to studyTarget.
(So, in case we don't want to/can't change anything, we should at least add cellType to all studyTargets.)

@UlrikeS91 thanks for raising and formulating the issue. For now please go ahead and include controlledTerm/CellType in all "studyTarget" properties.
@olinux I was thinking of something like the following:
...
"_linkedTypes": "https://openminds.ebrains.eu/studyTargetTypes",
...
With studyTargetTypes being a list of all allowed controlledTerms types and the suggestedTerm stored as a csv in either the controlledTerm Github or the main openMINDS Gihub. We could also define a specific template property / dialect for this if it would facilitate the compilation of the full schemas.
What do you think?

How about this:
We specify a
"_categories": ["studyTarget"]
in those schemas which are actually suitable for study targets.
In the consumer, we define
"_linkedCategories": ["studyTarget"]
TODO: We need to resolve the schemas based on their categories and resolve them in the generation step so the resulting json schema contains the full list of involved types.

@olinux thanks ! that's even a better idea! I'm starting a PR for this. :)

@olinux as you can see above the commits for the required/discussed changes were committed in PR #168

This issue was solved in PR #168


Redundant entry for options in the man page.

".SH OPTIONS" is enough.

Thanks @juanfra684 .
You are correct.
Could you please redirect your patch into the "dev" branch instead ?
Direct PR to master are not permitted by our Branch Policy.
Alternatively, I can also apply your patch manually if you prefer.


Implement support for comment tags

Implement support for comment tags as defined in the CQL 1.5. ballot

Addressed in the 1.5.2 release


Update overridden Morph extensions to match new trunk versions

Issue report: http://forum.world.st/Fractional-bounds-and-flickering-contains-images-that-may-be-disturbing-to-some-readers-td5105811.html
@marceltaeumel

By the way, what is difference between master and master-squot? I struggled committing to the first using Squot and master-squot has a red bar ...

"master" has no Squot format. I will merge "master-squot" back to "master" again because Squot works quite nicely. :-)


feat: improve relation screen

Description
Relation screen now shows find members when you aren't in a relation :)
Fixes #41
Flutter Channel:

[x] I have used the Flutter Beta channel on my local machine

Type of Change:
Delete irrelevant options.

User Interface

How Has This Been Tested?
Physical device, check  gif below.

Checklist:
Delete irrelevant options.

[x] My PR follows the style guidelines of this project
[x] I have performed a self-review of my own code or materials
[x] I have commented my code or provided relevant documentation, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] Any dependent changes have been merged

Code/Quality Assurance Only

[x] My changes generate no new warnings

@anitab-org/qa-team can someone give this a quick test? Thank you

Also imo we should keep the Details and Tasks tab, when the user is not in a relation also. The user gets to know what kind of user interface the app has without being in a relation. What do you think @isabelcosta ?

@robotjellyzone can you give it another try? should be fixed ig

hmmm, ok I'll look into this later, Thanks for testing. :)

@Techno-Disaster I am changing the label of this PR to Needs Review because there should be at least 2 approval before QA can test.

@robotjellyzone this should hopefully be fixed now, can you give it a quick go?

sure, but before merging can someone from @anitab-org/qa-team test if the text inside the button looks fine? or did you test it @isabelcosta ?

Thanks for the review.


New scope in Reactor in inner subscription

Hello,
I am using SQS for sending and receiving messages using the new async AWS SDK.
When sending messages, I am setting the tracing attributes into the message and when I receive them I would like to update the trace context with those.
This is more or less the polling logic:
Span pollSpan = tracer.newTrace()
  .name("poll");

try (Tracer.SpanInScope span = tracer.withSpanInScope(pollSpan.start())) {
  Flux < Message > flux = Flux.create(sink -> sink.onRequest(num -> receiveMessages(sink)));

  flux
    .flatMap(message -> {
      var mono = deserialize(message, MyObjectWithTracing.class);
      var traceId = message.messageAttributes().get("traceId").stringValue();
      var spanId = message.messageAttributes().get("spanId").stringValue();

      var newContext = TraceContext.newBuilder()
        .traceId(Long.parseLong(traceId))
        .spanId(Long.parseLong(spanId))
        .build();

      return mono.flatMap(myObject -> {
          // process object
          try (Tracer.SpanInScope ws = tracer.withSpanInScope(tracer.toSpan(newContext)
            .start())) {
            logger.info("Do something"); // wrong tracing information in the logs
          }
        })
        .contextWrite(Context.of(Span.class, tracer.toSpan(newContext).start(), TraceContext.class, newContext));
    })
    .subscribeOn(Schedulers.boundedElastic())
    .subscribe();
}

In the above code, I constantly poll for messages, for each of them, I retrieve the tracing info and I would like to use them in a new span as part of its processing. The problem I am facing is that the log always have the same traceId and spainId, the outer SpanInScope.

Have you tried setting the reactor instrumentation mode to manual and doing things manually? Most likely we're instrumenting too much there and we're polluting a thread that we never clear or sth like that

@marcingrzejszczak  I tried with 'decorate_queues' and same problem. I can't use 'manual' as I need the automatic instrumentation on the service, it's a webflux application that also does webClient calls. Is there a way to enforce the Reactor context? I saw some code samples using contextWrite but not sure if I am missing something. Thanks!

Can you create a sample that replicates this problem? BTW We will be revisiting how we do instrumentation with Reactor in Spring Framework 6 and Boot 3.

@marcingrzejszczak  actually, I don't think the problem is with the Reactor instrumentation.
While creating the sample project I realised that bit was working fine, the problem seems to be with the Async AWS SDK 2.0.
On my app, inside the flatMap, I am making a call to DynamoDB:
 var table = dynamoDbEnhancedAsyncClient.table("MyTable", TableSchema.fromClass(Item.class));
 var request = GetItemEnhancedRequest.builder()
                                            .key(Key.builder()
                                                    .partitionValue("MyKeyId")
                                                    .build())
                                            .build();
 Mono.fromFuture(table.getItem(request));

It appears the response creates a new context always.
I am setting a Spring ExecutorService to the SDK which Sleuth injects as a TraceableExecutorService:
  @Bean
    public ThreadPoolExecutor awsSdkExecutor()
    {
        ThreadPoolExecutor executor = new ThreadPoolExecutor(10,
                                                             500,
                                                             10,
                                                             TimeUnit.SECONDS,
                                                             new LinkedBlockingQueue<>(),
                                                             new ThreadFactoryBuilder().threadNamePrefix("sdk-async-response")
                                                                                .build());
        executor.allowCoreThreadTimeOut(true);
        return executor;
    }

 @Bean
    public DynamoDbAsyncClient dynamoDbAsyncClient(
                                                   ExecutorService awsSdkExecutor)
    {
        return DynamoDbAsyncClient.builder()
                                  .asyncConfiguration(b -> b.advancedOption(SdkAdvancedAsyncClientOption.FUTURE_COMPLETION_EXECUTOR, awsSdkExecutor))
                                  .build();
    }

@marcingrzejszczak  let me know if you would prefer to have a different issue or if we can use this thread for this. Thanks for your help and support.

Isn't this related to this https://github.com/spring-cloud/spring-cloud-sleuth/issues/2014 ?

I can see trace/spans on the CompletableFuture response which I subscribe to using Mono.fromFuture, so the instrumentation works however it always create a new context.

You are using Brave API directly from what I see. What you can do is use the Propagator API from Sleuth that allows you to inject and extract headers. The propagator will create a SpanBuilder for you from the headers and it will create a proper span out of the headers.

I don't know how the Propagator API will help.
I was able to create a small webflux application that reproduces the problem here: https://github.com/jonathannaguin/sleuth-issue-future
The source of the problem seems to be CompletableFuture:
return Mono.fromFuture(() -> {
                                               return CompletableFuture.completedFuture(myObject);
                                           });

Is there a way I can force the trace context after the fromFuture?

Hey @marcingrzejszczak, did you have a chance to review the sample project? Thanks!

Hi! Sorry, not yet. I have it on my radar and will try to look into it ASAP.

Sorry for not having done this yet... That method should help, the problem is that it's bug-prone cause it's putting stuff in thread local. The whole way we're instrumenting Reactor at this point can lead to such bugs but we'll try to address those in Spring Observability by rethinking the whole Observability & Reactor instrumentaion (and maybe do some patching in Sleuth).

I noticed the effort is going to those new libraries, as long as I have a similar utlity, I should be able to move out of Sleuth. Thanks

I'll close this since we have a manual solution to this. If we make the Reactor & Sleuth interop more stable then the manual work might not be necessary


Installing extra Node-Red nodes

Hi,
What is the best way to deploy new nodes ?
I'd like to have e.g. geohash node available.
Thanks !

Do an install in the docker file. E.g.:
#RUN npm install node-red-contrib-ttn
RUN npm install<EMAIL_ADDRESS>
(I wonder why I was using 2.0.1? Hmm. And perhaps we should get the version of node-red from the environment? I'll file a few issues.)


Show both date and lastmod in the page metadata

Feature Request
Is your feature request related to a problem? Please describe.
At this moment, a post with both date and lastmod set in the front matter only gets lastmod shown as Last updated on Dec 13, 2020 for example in:
https://academic-demo.netlify.app/post/getting-started/
Describe the solution you'd like
I'd like to see both the original published date and the last modified date like Apr 20, 2016 · Last updated on Dec 13, 2020.
Describe alternatives you've considered
Currently I've forked layouts/partials/page_metadata.html in my template with the following diff. Would be nice if the feature is available in the wowchemy module itself.
diff --git a/layouts/partials/page_metadata.html b/layouts/partials/page_metadata.html
index cdcd549..5dc519a 100644
--- a/layouts/partials/page_metadata.html
+++ b/layouts/partials/page_metadata.html
@@ -20,7 +20,7 @@
       {{ $date = $page.Date.Format (site.Params.publications.date_format | default "January, 2006") }}
     {{ else }}
       {{ if ne $page.Params.Lastmod $page.Params.Date }}
-          {{ i18n "last_updated" }}
+          {{ $page.Date.Format site.Params.date_format }} · {{ i18n "last_updated" }}
       {{ end }}
     {{ end }}
     {{ $date }}

Do you think you could submit a PR solving this @nobuto-m ? I'd be interested in it as well.

Do you think you could submit a PR solving this @nobuto-m ? I'd be interested in it as well.

I'm also looking for this feature. Any updates on this?

I also want to retain the original date as I've migrated some old posts from another blog and this is important to have that original date preserved. Is there any easy way to apply this - I don't see any layouts folder in the site structure?

@jpmorr the original patch should still work. It's not there because it's used modularly from https://github.com/wowchemy/wowchemy-hugo-themes/blob/main/wowchemy/layouts/partials/page_metadata.html


TypeError: tuple indices must be integers or slices, not str

What is your question?
I am trying to pre-train a masked language model on an arabic dataset, but I have been getting this error "TypeError: tuple indices must be integers or slices, not str".
Code
Data pre-processing command
fairseq-preprocess --trainpref arabic_training_split.spm --validpref arabic_validation_split.spm --destdir data_bin_ar --bpe sentencepiece --only-source
Training command
fairseq-train data_bin_ar/ --task masked_lm --encoder-layers 6 --encoder-attention-heads 16 --sample-break-mode eos --arch masked_lm --encoder-ffn-embed-dim 4096 --encoder-embed-dim 1024 --encoder-learned-pos --encoder-normalize-before --share-encoder-input-output-embed --activation-fn gelu --max-epoch 150 --max-tokens 8000 --optimizer adam --adam-betas '(0.9,0.98)' --lr 0.005 --warmup-init-lr '1e-07' --min-loss-scale 0.0 --lr-scheduler inverse_sqrt --warmup-updates 2500 --update-freq 6 --criterion label_smoothed_cross_entropy --label-smoothing 0.1 --dropout 0.1 --save-interval 5 --keep-last-epochs 5 --save-dir masked_lm_checkpoints --fp16 --ddp-backend=no_c10d
This is what I get:
Traceback (most recent call last):                                                                                File "/home/met/.local/bin/fairseq-train", line 8, in <module>     sys.exit(cli_main())   File "/home/met/.local/lib/python3.8/site-packages/fairseq_cli/train.py", line 448, in cli_main     distributed_utils.call_main(cfg, main)   File "/home/met/.local/lib/python3.8/site-packages/fairseq/distributed_utils.py", line 337, in call_main     main(cfg, **kwargs)   File "/home/met/.local/lib/python3.8/site-packages/fairseq_cli/train.py", line 144, in main     valid_losses, should_stop = train(cfg, trainer, task, epoch_itr)   File "/usr/lib/python3.8/contextlib.py", line 75, in inner     return func(*args, **kwds)   File "/home/met/.local/lib/python3.8/site-packages/fairseq_cli/train.py", line 244, in train     log_output = trainer.train_step(samples)   File "/usr/lib/python3.8/contextlib.py", line 75, in inner     return func(*args, **kwds)   File "/home/met/.local/lib/python3.8/site-packages/fairseq/trainer.py", line 532, in train_step     loss, sample_size_i, logging_output = self.task.train_step(   File "/home/met/.local/lib/python3.8/site-packages/fairseq/tasks/fairseq_task.py", line 428, in train_step     loss, sample_size, logging_output = criterion(model, sample)   File "/home/met/.local/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1110, in _call_impl     return forward_call(*input, **kwargs)   File "/home/met/.local/lib/python3.8/site-packages/fairseq/criterions/label_smoothed_cross_entropy.py", line 80, in forward     loss, nll_loss = self.compute_loss(model, net_output, sample, reduce=reduce)   File "/home/met/.local/lib/python3.8/site-packages/fairseq/criterions/label_smoothed_cross_entropy.py", line 110, in compute_loss     lprobs, target = self.get_lprobs_and_target(model, net_output, sample)   File "/home/met/.local/lib/python3.8/site-packages/fairseq/criterions/label_smoothed_cross_entropy.py", line 98, in get_lprobs_and_target     lprobs = model.get_normalized_probs(net_output, log_probs=True)   File "/home/met/.local/lib/python3.8/site-packages/fairseq/models/fairseq_model.py", line 547, in get_normalized_probs     encoder_out = net_output["encoder_out"] TypeError: tuple indices must be integers or slices, not str
What have you tried?
I tried a similar approach the solution proposed in #2971  but it did not work with my problem
What's your environment?
I cloned the repository from the main branch and used this command
pip install fairseq/

PyTorch Version: 1.11.0
OS (e.g., Linux): Linux
Python version: 3.8.10
GPU models and configuration: NVIDIA-SMI 470.103.01   Driver Version: 470.103.01   CUDA Version: 11.4

Same issue. Is this solved? @salma-elshafey


Pagination example

I'm trying to setup a table with pagination but with this new version I haven't been able to do it yet.
I've read the Upgrade Guide but I can't really understand what I've to do in order to display the pagination. (I'm kind of new in VueJS). Also the vuetable:pagination-data is never called in my component.
Here's what I've coded at the moment:
<template>
    <vuetable
        :api-url="apiUrl"
        :fields="columns"
        :pagination-path="paginationPath"
        :css="css"
        :pagination-component="paginationComponent"></vuetable>
</template>
<script>
    export default {
        props: ['apiUrl'],

        mixins: [require('../components/Mixin.vue')],

        data: function data() {
            return {
                columns: [
                    'first_name',
                    'last_name',
                    'email',
                    'company',
                    'job_title',
                    'groups'
                ],
                paginationPath: 'meta.pagination.links',
                paginationComponent: 'vuetable-pagination',
                css: {
                    tableClass: 'table',
                    ascendingIcon: 'fa fa-angle-up',
                    descendingIcon: 'fa fa-angle-down',
                    detailRowClass: ''
                }
            }
        },

        mounted: function () {
            //
        },

        methods: {
            registerEvents: function () {
                var self = this;

                this.$on('vuetable:pagination-data', function (pagination) {
                    console.log('vuetable:pagination-data', pagination);
                });
            }
        },

        created: function () {
            this.registerEvents();
        }
    }
</script>

And I'm calling this component like this :
<laravel-participant-vuetable api-url="/vue/api/events/{{ $event->id }}/participants"></laravel-participant-vuetable>

Thanks for your help

@depsimon The VuetablePagination is no longer embedded in Vuetable. So, you have to manually put it in your template and wire it to Vuetable. Please see the example here. This is where it gets wired to VuetablePagination.

Thanks it helped me to view both files at the same time.


running on mac brings pain. or at least does not work in xcode with paths set

howdy,
rather than post an email to you, someone else may have got this as well on mac.
so...
ive done the set up, just translated the spanish wiki for doing it with mac, and whilst making things like glfw3 work and compile, and have also setup the location of raylib.h by clicking and dragging in the location to the Search paths > header search paths/library search paths it brings up an error. screenshot shows error.

now i have tried again and again. but no dice, same message
xcode version is 7.3.1, plus used cmake to do the generation, and all that worked. so dont know whats up.
raylib looks interesting, a break away from my more bigger things ;)

also my other settings, for the library settings & the search paths. screenshots given

Hi lewislepton, just for record, you have tried adding to Library Search Paths: "/Users/lepton/Developer/raylib/RAYLIBGLFW/../../../Downloads/raylib-master/release/osx"?

yeah, that also does not work

Just reviewed tutorial and translated to english: https://github.com/raysan5/raylib/wiki/Compile-for-OSX
Tomorrow I'll try to check it on a Mac...

Do you have a libraylib.a on the release/osx folder of the library source code?

Do you have a libraylib.a on the release/osx folder of the library source code?

this is the setup with the library, which is right, also did compile etc. though i will move raylib to my developer folder just so it doesnt get lost in my downloads ;)

ok. so i have tried the latest update to the tutorial to build with mac, plus have tried the develop version, just to see. but the same problem happens.
but did notice that a raylib.h has compiled when i compiled the release/osx. before that did not happen

ah ha. noticed the error message is actually now saying that GLFW3 can not be found. which is weird, since i went through the same process. very odd

but everything is set up right. followed everything well and to the point. very strange. even the master is not building, does come up with the cant find glfw3 the same as the develop version, but master does not generate a raylib.h inside the release/osx folder

here is the project im working, with xcode
RAYLIBGLFW.zip

its set up with raylib just above the project folder, which was pointed to it

Hi @lewislepton, not sure what's the problem, it seems related to paths, it should work ok; actually @paezao is developing on OSX with raylib and it works fine... Maybe he can give you some feedback on your issue...

ok. so after some folling, did do a new project. everything works now. dont know why it did. because everything was the same settings, even c was used
here is the new, working project
RAYRAY.zip

Nice! Im glad it worked!


Backported frontend/implementation/api updates

What is the reason for these frontend changes?

ABI spec is outdated on main_stable (scripts/tool_check_abi.sh would produce changes already even without this PR) like functions are not mentioned which are public (some of the _v2 functions are removed on main already like libxsmm_dmmdispatch_v2 and libxsmm_smmdispatch_v2).

Implementation wise, there are some corrections for corner cases previously untested. Otherwise it's about clarifying code comments on existing functions. The src/libxsmm_matrixeqn.c change is a bugfix.

The changes about coprime/2 and shuffle have no impact for existing code and are related to own research.

Thanks, can we please for now limit the PR to:
ABI spec is outdated on main_stable (scripts/tool_check_abi.sh would produce changes already even without this PR) like functions are not mentioned which are public (some of the _v2 functions are removed on main already like libxsmm_dmmdispatch_v2 and libxsmm_smmdispatch_v2).
Implementation wise, there are some corrections for corner cases previously untested. Otherwise it's about clarifying code comments on existing functions. The src/libxsmm_matrixeqn.c change is a bugfix.
For all the other changes in main, I need to find to some to review how we can merge most of them and move main to a feature branch which has such private research features which we then can merge afterward.  But that at least would allow us the merge some refactor now, make main_stable main and we can merge into feature branches. The remainder (hopefully small) would live in a feature branch for now.

The PR is now narrowed to the item you selected.


Component Demo Pages Link Invalid

Describe the bug
The component demo pages linked from Readme.md is invalid.

Hello @BenjaminWatts,
Thank you for submitting this issue.
A fix has now been merged. The documentation site referenced in the develop branch README.md will not be accessible until the upcoming major v1.0.0 is shipped. We expect this to happen imminently.
I have closed this issue.


cls.toggle is not very nice to use.

I feel like cls.toggle is in stark contrast to other class definitions in outwatch.
Take a look at the following code:
val disabled: Rx[Boolean] = ???

button(
  cls := "btn",
  cls.toggle("disabled") <-- disabled
)

It feels like this should be the other way round. cls.toggle(disabled) := "disabled".

Do you have a good idea for another name or should we just repurpose the method?

I am not sure if and how we could handle it cleanly.
We could just inverse the relation, but since we have both <-- and  := that isn't very nice.
Maybe we should really get rid of <-- first.
But constructs like cls.toggle(someRx) := someRxOfString can still exist which is kinda ugly.

Agreed to get rid of <--.
Another syntax could be:
(cls := "disabled").toggle(someBoolRx)

I do not feel that strongly about <-- and until now we did not manage to write proper overloads for the := function - so I would put this on hold for now.
We could use the same construct as with VModifier.ifTrue(...)(...). Thereby, we can make the second parameter list call-by-name and thereby lazy. This is useful if we are toggeling bigger VModifiers - that you do not want to construct when you do not render them.

I think we should make an effort to keep this feature concise. It is mostly a convenience feature anyways and should flow nicely with other class declarations.
If it weren't present at all one could also do the following:
div(
  someObservableBool.map(b => Option.when(!b)(cls := "disabled"))
)

On that note. We should align with the std library (Option here) and rename VModifier.ifTrue to when and ifNot to whenNot.

Good point about concise. How about we keep it similar and even name it when. Toggle is a bit ambiguous anyhow.
div(
cls.when(Boolean or Observable[Boolean]) := "disabled"
)

An alternative could be to add operators to colibri for observables. Something like this:
div(
  // could also be named ifElse/ifElseEmpty
  boolObservable.whenOr(cls :=  "disabled", VModifier.empty)
  // or even for monoid
  boolObservable.whenOrEmpty(cls := "disabled")
)

The toggle method is now deprecated without replacement :)
Please reopen if you think, we still need something else than asIf.


Add clotributor link to README

Part of https://github.com/knative/community/issues/1403
Adds a link to the CLOTRIBUTOR page for Knative to the README

/approve

@evankanderson seems like owner files are out of date - can you update them to unblock the PR

Seems like your the last person in the current files who can approve


Add ability to enable touch events on target view

Add ability to enable touch events on target view (issue #19)
Fix enabling/disabling dismissal during the entry animation (issue #18)
Protect against showing/hiding SpotlightView when it's not attached to a window
Consume touch events so user can't interact with views underneath the SpotlightView

Have a couple of fixes to add to this one.


The application of Zmap

Can zmap be used for scanning network layer or transport layer?

Yes,both ip layer and transport layer are ok.

It's the first time I use this tool,can you tell me what should I do?
------------------ 原始邮件 ------------------
发件人<EMAIL_ADDRESS>发送时间: 2020年1月3日(星期五) 下午5:24
收件人<EMAIL_ADDRESS>抄送<EMAIL_ADDRESS><EMAIL_ADDRESS>主题: Re: [zmap/zmap] The application of Zmap (#584)
Yes,both ip layer and transport layer are ok.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Maybe this article can be helpful for you!
link: https://linux.cn/article-5860-1.html#bestpractices

OK,thank you so much!


MTU is wrong for Pod's eth0 interface when using Wireguard

Describe the bug
When using Wireguard, the MTU configured for each Pod's eth0 interface does not look correct.
It should be set to the same value as for the antrea-wg0 interface: transportMTU - 80.
# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: tunl0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000
    link/ipip <IP_ADDRESS> brd <IP_ADDRESS>
3: ip6tnl0@NONE: <NOARP> mtu 1452 qdisc noop state DOWN group default qlen 1000
    link/tunnel6 :: brd :: permaddr 4677:d46a:24b1::
4: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 6a:9f:1c:f5:5b:2c brd ff:ff:ff:ff:ff:ff
5: genev_sys_6081: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 65000 qdisc noqueue master ovs-system state UNKNOWN group default qlen 1000
    link/ether 46:ab:5d:06:3f:85 brd ff:ff:ff:ff:ff:ff
6: antrea-gw0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 65485 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ether 6a:46:b8:75:db:ef brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global antrea-gw0
       valid_lft forever preferred_lft forever
7: antrea-wg0: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 65455 qdisc noqueue state UNKNOWN group default
    link/none
    inet <IP_ADDRESS>/32 scope global antrea-wg0
       valid_lft forever preferred_lft forever
8: antrea-egress0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default
    link/ether 7a:74:3e:b5:66:11 brd ff:ff:ff:ff:ff:ff
9: coredns--70cbe6@if4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 65485 qdisc noqueue master ovs-system state UP group default
    link/ether ae:b6:f9:99:20:c7 brd ff:ff:ff:ff:ff:ff link-netnsid 1
10: eth0@if11: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 65535 qdisc noqueue state UP group default
    link/ether 02:42:ac:12:00:03 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet <IP_ADDRESS>/16 brd <IP_ADDRESS> scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fc00:f853:ccd:e793::3/64 scope global nodad
       valid_lft forever preferred_lft forever
    inet6 fe80::42:acff:fe12:3/64 scope link
       valid_lft forever preferred_lft forever
11: local-pa-daf9ad@if4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 65485 qdisc noqueue master ovs-system state UP group default
    link/ether 26:33:e9:2b:1d:2a brd ff:ff:ff:ff:ff:ff link-netnsid 2
12: coredns--3bcc0c@if4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 65485 qdisc noqueue master ovs-system state UP group default
    link/ether b6:f5:55:02:8e:5d brd ff:ff:ff:ff:ff:ff link-netnsid 3
13: antrea-t-579008@if4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 65485 qdisc noqueue master ovs-system state UP group default
    link/ether 22:78:19:2f:c2:81 brd ff:ff:ff:ff:ff:ff link-netnsid 4

This is a Kind cluster, which is why the MTU for the transport interface (eth0) is 65535.
For antrea-wg0, the MTU is set to 65535 - 80 = 65455, but for Pod veths, it is set to 65535 - 50 = 65485.
The MTU for Pod interfaces is computed by https://github.com/antrea-io/antrea/blob/792e2447ae4ed0ad6f6293f4b1a39cf98e936e5b/pkg/agent/config/node_config.go#L267-L285
which ignores the fact that we are using Wireguard, and deducts Geneve overhead (even though we are not actually using Geneve here, it is just the default value of tunnelType in the config).
The function should be updated, and the MTU should be reduced by 80B instead of 50B when using Wireguard.
To Reproduce
Create a Kind cluster and install Antrea with helm install -n kube-system antrea antrea/antrea --set trafficEncryptionMode="wireGuard".
Deploy an iperf client Pod and an iperf server Pod on 2 different Nodes.
On the server Pod, run iperf3 -s.
On the client Pod, run iperf3 -c <server IP> -u -b 0 -l 65457. 65457 is computed by taking the MTU of the eth0 interface (of the Pod) and subtracting 28B (UDP & IPv4 headers).
You should get one of the following:

An error:

iperf3: error - unable to write to stream socket: Message too long

Or, iperf runs successfully, but packets are fragmented (can be confirmed by capturing traffic on receiver Node):

22:27:04.528644 IP (tos 0x0, ttl 64, id 44941, offset 0, flags [none], proto UDP (17), length 65515)
    <IP_ADDRESS>.51820 > <IP_ADDRESS>.51820: [bad udp cksum 0x5813 -> 0xbaa9!] UDP, length 65487
22:27:04.528649 IP (tos 0x0, ttl 64, id 44942, offset 0, flags [none], proto UDP (17), length 124)
    <IP_ADDRESS>.51820 > <IP_ADDRESS>.51820: [bad udp cksum 0x58a3 -> 0x8feb!]
We may want to adjust the MTU for antrea-gw0 as well, assuming it is possible for traffic that will eventually be encapsulated to be output through this interface. Currently we set it to the same value as for Pod's veth interfaces.
Credit goes to @AlexisDucastel for reporting this.

@xliuxu @tnqn @luolanzone