"X More" dialog does not sort items based on the timestamp

Version
2.1.3
Test Environment
Chrome
Current Behavior
Our users are active calendar users and they have a very busy calendar. X More dialog does not sort the events and it drives them absolutely insane. Here is an example:

I hope it is a simple fix somewhere in here: https://github.com/nhn/tui.calendar/blob/b53e765e8d896ab7c63d9b9b9515904119a72f46/apps/calendar/src/components/popup/seeMoreEventsPopup.tsx#L87
Expected Behavior
The events sorted by time just like in the main view.

I'm having this same problem. Waiting anxiously for suggestions to how to solution this.

I managed to develop the following solution without the need to change the plugin's source code
Solution
cal.on({'clickMoreEventsBtn': function(day) {

    // Variable to store the events for the selected day
    const allSchedules = [];

    // Loop through the div to capture all events and store them in the allSchedules array
    day.target.querySelectorAll('.toastui-calendar-weekday-event-block').forEach(function(htmlEvent) {

        var eventId = parseInt(htmlEvent.getAttribute('data-event-id'));
        var calendarId = parseInt(htmlEvent.getAttribute('data-calendar-id'));

        // ADD THE EVENT AND ITS HTML TO THE ARRAY
        allSchedules.push({'event' : cal.getEvent(eventId, calendarId), 'html' : htmlEvent});
    });

    // Sort the events by start time
    allSchedules.sort((a, b) => {
        const timeA = new Date(a.event.start).getTime();
        const timeB = new Date(b.event.start).getTime();
        return timeA - timeB;
    });

    // Customize the popup with the sorted events (Replace the existing content)
    const popupContent = day.target.querySelector('.toastui-calendar-month-more-list');

    if (popupContent) {
        // Clear the existing content
        popupContent.innerHTML = '';

        // Add the sorted events
        allSchedules.forEach(schedule => {
            popupContent.appendChild(schedule.html);
        });
    }

}});

Explanation:
1. Storing Events: We use a variable allSchedules to keep track of all the events for the selected day.
3. Getting Events: We loop through the HTML of the popup to capture each displayed event. By extracting the event ID and calendar ID from the HTML, we can access the event data using the getEvent function. Both the event data and its HTML are stored in the allSchedules array.
4. Sorting: We sort the events based on their start time.
5. Updating the Popup: After retrieving and sorting the events, we update the popup content with the sorted events.
Before

After


Multiple images per date returned for Sen-2 L2A COGs AWS search

Hi, I have been using sat-search quite a bit, and when making a time series graph , noticed that there are 2 observations per date, for Sen-2 L2A from AWS.
So I simply went back to look at the items listed from catalog -
dates = '2020-08-01/2020-08-30'

# request goes with wgs84 bounding box
URL='https://earth-search.aws.element84.com/v0'
results = satsearch.Search.search(url=URL,
                                  collections=['sentinel-s2-l2a-cogs'],
                                  datetime=dates,
                                  bbox=wgs_bound,
                                  sort=['<datetime'],
                                  query=['eo:cloud_cover<=1'])
items = results.items()
catalog = intake.open_stac_item_collection(items)

print(list(catalog)) gives -

 ['S2A_43QFA_20200829_0_L2A',
 ['S2A_43QFB_20200829_0_L2A',
 ['S2B_43QFA_20200824_0_L2A',
 ['S2B_43QFB_20200824_0_L2A',
 ['S2A_43QFA_20200819_0_L2A',
 ['S2A_43QFB_20200819_0_L2A',
 ['S2B_43QFA_20200814_0_L2A',
 ['S2B_43QFB_20200814_0_L2A',
 ['S2A_43QFA_20200809_0_L2A',
 ['S2A_43QFB_20200809_0_L2A',
 ['S2B_43QFA_20200804_0_L2A',
 ['S2B_43QFB_20200804_0_L2A']

some rough string manipulation on items.summary(['date', 'id', 'eo:cloud_cover']) gives the below list -

[['2020-08-29', 'S2A_43QFA_20200829_0_L2A', '0'],
 ['2020-08-29', 'S2A_43QFB_20200829_0_L2A', '0'],
 ['2020-08-24', 'S2B_43QFA_20200824_0_L2A', '0'],
 ['2020-08-24', 'S2B_43QFB_20200824_0_L2A', '0'],
 ['2020-08-19', 'S2A_43QFA_20200819_0_L2A', '99.94'],
 ['2020-08-19', 'S2A_43QFB_20200819_0_L2A', '99.33'],
 ['2020-08-14', 'S2B_43QFA_20200814_0_L2A', '97.38'],
 ['2020-08-14', 'S2B_43QFB_20200814_0_L2A', '97.37'],
 ['2020-08-09', 'S2A_43QFA_20200809_0_L2A', '96.97'],
 ['2020-08-09', 'S2A_43QFB_20200809_0_L2A', '99.5'],
 ['2020-08-04', 'S2B_43QFA_20200804_0_L2A', '91.72'],
 ['2020-08-04', 'S2B_43QFB_20200804_0_L2A', '86.68']]

So, im wondering why are there two images per date?
And, they have different "cloud cover" percentages too.
sat-search version - (v.0.3.0)
Thanks in advance for any leads on this.

Anyone have any comments/updates on this? Thank you!


Change MD font

Hey all,
Is there an easy way to overwrite the font used by the material design components? I'm trying to mix and match a few frameworks in a project I'm working on and the multiple fonts thing is making it look a bit crazy.
Thanks

material design components  provides all kinds of method to custom your style

This is tracked by #205


What happened to version 2.0?

The SBCL version mentioned in the README sounds good. Is it ever going to happen?
Is the source available in a beta form?

Looking forward to sbcl …


Seems There is a Bug in Route::apiResources

I use Route::apiResources(['staff-management' => StaffController::class]); along with anoher route API inside middleware below.
Route::group(['prefix' => 'staff', 'middleware' => ['auth:staff-api', 'scopes:staff']], function () {     Route::get('staff-management/search/{keyword}', [StaffController::class, 'searchStaff']);     Route::get('staff-management/download-pdf', [StaffController::class, 'downloadPDF']); });
The result is, download-pdf route getting blank when I access it using Postman. So, I decide to remove Route::apiResources and now, it's working. Try to fix this problem. I think this problem is considered to be bug.
For more clear, you can refer to https://stackoverflow.com/questions/68147080/laravel-api-getting-blank-response

Hi there,
Thanks for reporting but it looks like this is a question which can be asked on a support channel. Please only use this issue tracker for reporting bugs with the library itself. If you have a question on how to use functionality provided by this repo you can try one of the following channels:

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

However, this issue will not be locked and everyone is still free to discuss solutions to your problem!
Thanks.

I report the bug, not asking the solution. I just tell you that Route::apiResources considered to be bug related to this problem. The problem itself has been solved by me. So, I am here not to ask to the solution. I just tell the bug. That's it!


NR-284035 - Added WatchOS tests to PR builds.

Adds running of WatchOS tests to automated PR builds.

I think main.yml is the file that you want to add to for this.


https / bug fixes / secutity

Resolves #7
https Will auto generate crypto / cert if not found in config - Will save generated crypto
MANY major bug fixes
Found how to catch server listen error
https option is literally just https (serverconfig.https)
Ask me if you have questions

So, https instead of optUseHttps?
And key and cert for custom https certs?
Does it catch invalid keys/certs if the user enters something wrong?

@terreng Correct, although the server will auto generate the cert/key if none if found or when the server is created. Changes will be saved to config.json. I do not recommend putting the key and cert options into the UI - As everything is handled in the backend

So should there be an option for the user to provide a custom cert or no?

@terreng We could, I dont see why someone would need to do so, doing this may open the server to not being able to start due to the key being inputted even a little wrong. What do you think?

We could also have this as an option just not in the UI, and we could have a guide on how to manually put a custom cert in the config file. If it's not something that people will do very often, then I think this makes sense. Want to go with that?

@terreng I like that idea. Should I write it in a read me or put it in the website for when we make it

You can make a new page in the howTo folder. It will be easy to convert everything to the website once it's ready.

I think we should rename cert  and key to httpsCert and httpsKey.
I notice that you run the same piece of code to generate certs and keys, once when the user saves, and once when servers start. I think you should make this a function that takes the array of servers as input.
Also, please remove the temporary arg1.servers[i].https = true

I notice that you run the same piece of code to generate certs and keys, once when the user saves, and once when servers start. I think you should make this a function that takes the array of servers as input.

I don't quite understand what you're saying. I made it to where when the config saves it will generate key and cert as needed. I also put it when the server starts to make sure (mainly when testing) if the https is enabled, but there is no key/cert in the config it will generate and save the key/cert
I will make other changes when I get a chance

What I meant by create a function is do something like this so you aren't repeating code.
function setMissingCrypto(servers) {
    for (var i=0; i<servers.length; i++) {
        if (servers[i].https) {
            if (!servers[i].cert || !servers[i].key) {
                var crypto = WSC.createCrypto()  // Create HTTPS crypto
                servers[i].key = crypto.privateKey
                servers[i].cert = crypto.cert
            }
        }
    }
}

@terreng All done and ready to merge!

Add the macOS save location to the how to: $HOME/Library/Application Support/Simple Web Server/config.json
The point of moving the crypto thing to a function was so that you aren't repeating it twice, which it looks like you still are. If the function doesn't solve that, then there's no point.
For the errors, I think we should use this format:

Error 500: Internal Server Error

Error with your script, check the logs

I think you should update the error function to only take the message part in the defaultMsg argument, and then use the status code to determine what the primary error message should be.
For example, you would call this.error("Error with your script, check the logs", 500) and it would output the HTML above.

I would prefer to use
500 - Internal Server Error
 rather than
Error 500: Internal Server Error
 because I don't feel the need to
put error at the beginning (Because that is what the error message is for)
Could I do this?
Also, the reason I repeat executing the code twice is for a failsafe, when
there is an error saving and the crypto didn't save - It generates a new
one and starts the server

I would prefer to use
500 - Internal Server Error
 rather than
Error 500: Internal Server Error

That works!
I understand why you're running the code twice. Because you're doing the same thing in two places, using a function would mean you only need to update this in one place instead of two in the future. But it's not a big deal. What you have works.

@terreng Go ahead and merge

Could you add the macos save location to howTo/custom https cert&key.md real quick?
$HOME/Library/Application Support/Simple Web Server/config.json

@terreng done


null in list breaks ng:repeat (Cannot read property '$$hashKey' of null)

This happens in 0.10.5 and 0.10.6-871252ab.  At least some of the time this causes $digest() to time out.
http://jsfiddle.net/gronky/YqML5/

I think that this is because typeof null is object, which confuses the repeater into thinking that it's a real object, but null while claiming to be an object can't have its properties dereferenced, which causes problems.
special-casing the null should do the trick. I'll explore that.


Task 1: (C)reate

As a user, I want to INSERT INTO table so that I can create new employees, departments, and companies.

Done in #2


ci: improve goreleaser workflow

closes #1100

updated to latest goreleaser
using gomod proxy
improve version command to use build info only:

on on proxy builds (e.g. go run) it will show cue version devel just as before
on proxied builds it will show the mod version + its checksum

also just noticed you are not using goreleaser to create the docker images, any particular reason? Looking at it it seems it would be doable through goreleaser as well... 🤔

OK, fixed what you pointed out, and also:

fixed an invalid tag version in go setup
using goreleaser to build docker images
creating a docker manifest with both arm64 and amd64 images

@caarlos0 this is awesome thanks.
One final request: please can you squash the commits down to a single commit message, ready for import into Gerrit? I'd also suggest we prefix the first line of the commit message with ci:  - correctly categorises it with CI-related changes then (we need to do better at documenting this rather "loose" selection of categories).
.. and one question. How should I be testing this locally? Or better still, how can we automate the testing of this setup? Perhaps not something to trigger on every build matrix entry, but I've been concerned for some time that we don't really trigger this workflow until we come to a release... at which point it's "too late".

@myitcv squashed and changed message prefix!

About your question: you can run goreleaser release --rm-dist --snapshot... it will test everything but the publishing part... I can do that as well if you want :)

you can run goreleaser release --rm-dist --snapshot... it will test everything but the publishing part... I can do that as well if you want :)

Ah cool. Let's tackle that in a follow-up PR. That check need only run for the Linux entry of the latest stable Go version, so we can use a guard much like this:
https://github.com/cue-lang/cue/blob/7d25ee232fe7ee57c502baee7e82417a03a7e297/internal/ci/workflows.cue#L87-L89
Unlike that linked step, I think it does make sense to run as part of a non-master build. i.e. we do want to check it as part of any contribution. Limiting the check to just Linux and just the latest stable Go version will keep runtimes low.

Ok - we're all set here... and we've run into the first little issue post migration - I can't import the PR into Gerrit. Strange, because that definitely worked during my testing. So I've raised https://bugs.chromium.org/p/gerrit/issues/detail?id=14807 as a follow up.
@caarlos0 - whilst we wait for a resolution there, I tested things locally using https://github.com/cue-lang/cue/pull/1105#issuecomment-882503089, and found that go.sum was modified as a result. The reason being, we currently have go mod download as a before hook:
https://github.com/cue-lang/cue/blob/7d25ee232fe7ee57c502baee7e82417a03a7e297/.goreleaser.yml#L5
That seems superfluous to my mind. I removed it and tested again, and all seemed fine.
Is it safe for me to remove this in a follow up?

That seems superfluous to my mind. I removed it and tested again, and all seemed fine.
Is it safe for me to remove this in a follow up?

hmm... usually I set it to go mod tidy to make sure there are no changes in build time... but if removing works I think its ok as well...

hmm... usually I set it to go mod tidy to make sure there are no changes in build time... but if removing works I think its ok as well...

That raises an interesting question. Because having go mod tidy as a before hook actually means that the goreleaser workflow can make changes to go.{mod,sum} files. I would have thought it probably best to not have go mod tidy, because then any of the build steps that run as part of goreleaser would fail if they did need to make changes (this is the new behaviour with Go 1.16, where build commands fail if any of go.{mod,sum} is not tidy/complete), thereby alerting the user. As it stands, have go mod tidy would mean that these changes are missed, unless the user then checks the commit is clean.
I'll make the change in a follow-up in any case because just so long as I doesn't break goreleaser, I think it's the right change for us here.

hmm, I usually do the go mod tidy thing to make sure the go.* files are "clean"... if not, goreleaser will change them and fail the build later when it checks for a clean git state...

hmm, I usually do the go mod tidy thing to make sure the go.* files are "clean"... if not, goreleaser will change them and fail the build later when it checks for a clean git state...

Interesting, great to hear that goreleaser checks that. So is there an issue here then? Because we have go mod download as our before step, and that does modify go.sum. So why is goreleaser not failing in this case?

anyway, removed the before hook and rebased with master

Ok, I've gone with manually importing this into Gerrit for now. See progress at:
https://review.gerrithub.io/c/cue-lang/cue/+/521069


Decide on CAST behaviour for invalid inputs

Note: migrated from original JIRA: https://issues.apache.org/jira/browse/ARROW-10793
This is a placeholder for now. See discussion on [https://github.com/apache/arrow/pull/8794]
Briefly, the issue is do we want CAST to return null for invalid inputs or throw an error. Spark has different behavior depending on whether ANSI mode is enabled or not.
I'm not sure if this is a DataFusion specific or a more general Arrow issue yet. It needs a discussion.

Comment from Mike Seddon(MikeSeddonAU) @ 2020-12-02T22:44:31.207+0000:
I strongly feel that DataFusion should adopt the ANSI-style strict typing rather than silent error suppression and return of NULL values as intuitively (due to years of using DBMS) users expect that if an error was not thrown then all operations were completed successfully.

The default Spark behavior was inherited from Hive SQL which I assume was originally built to support a business where absolute precision was not necessarily important. As part of the Spark 3.0 release a huge amount of effort was put in to comply with ANSI standard SQL ([https://spark.apache.org/docs/3.0.0/sql-ref-ansi-compliance.html|https://spark.apache.org/docs/3.0.0/sql-ref-ansi-compliance.html)]) which is obviously a lot harder to retrofit than start with.

This also goes wider than type conversions as adopting ANSI SQL standards (including functionality like [https://github.com/apache/arrow/pull/8688] which I think requires a CASE statement in ANSI SQL) should maybe be agreed by the PMC to give a framework for assessing PRs against. Perhaps this ticket should be changed to a discussion of which dialect of SQL DataFusion aims to support.


Incomplete compatibility with Pino logger

There are conditional tests using logging methods that behave differently when using Pino vs Bunyan, e.g. like this one in lib/server.js:
if (log.trace()) { log.trace('data on %s: %s', c.ldap.id, util.inspect(data)) }
The Pino methods always return void while Bunyan's eval to true. Further, the arg-less Pino method calls fire off a bare event to the output stream so we see a slew of message-less events.
It would seem that those tests are not necessary given the abstract-logger noop methods and the log level options built into the other packages.
Node source to reproduce:
const log = require('pino')({level: 'trace'});
require('ldapjs').createServer({log: log}).listen(1389, 'localhost', () => log.info('Hello'));

Run it then call: ldapsearch -H ldap://localhost:1389 -x -b o=my gawd=*
Console output from nodejs is:
{"level":30,"time":1605124530404,"pid":450,"hostname":"LAPTOP-fed","msg":"Hello"}
{"level":10,"time":1605124534421,"pid":450,"hostname":"LAPTOP-fed","msg":"new connection from <IP_ADDRESS>:55384"}
{"level":10,"time":1605124534423,"pid":450,"hostname":"LAPTOP-fed"}
{"level":10,"time":1605124534425,"pid":450,"hostname":"LAPTOP-fed"}
{"level":10,"time":1605124534425,"pid":450,"hostname":"LAPTOP-fed"}
{"level":20,"time":1605124534426,"pid":450,"hostname":"LAPTOP-fed"}
{"level":20,"time":1605124534431,"pid":450,"hostname":"LAPTOP-fed"}
{"level":10,"time":1605124534433,"pid":450,"hostname":"LAPTOP-fed"}
{"level":10,"time":1605124534433,"pid":450,"hostname":"LAPTOP-fed"}
{"level":10,"time":1605124534434,"pid":450,"hostname":"LAPTOP-fed"}
{"level":20,"time":1605124534434,"pid":450,"hostname":"LAPTOP-fed"}
{"level":20,"time":1605124534436,"pid":450,"hostname":"LAPTOP-fed"}
{"level":10,"time":1605124534437,"pid":450,"hostname":"LAPTOP-fed"}
{"level":10,"time":1605124534437,"pid":450,"hostname":"LAPTOP-fed"}
{"level":10,"time":1605124534437,"pid":450,"hostname":"LAPTOP-fed"}
{"level":20,"time":1605124534437,"pid":450,"hostname":"LAPTOP-fed"}
{"level":10,"time":1605124534438,"pid":450,"hostname":"LAPTOP-fed","msg":"<IP_ADDRESS>:55384: unbinding!"}
{"level":10,"time":1605124534440,"pid":450,"hostname":"LAPTOP-fed","msg":"<IP_ADDRESS>:55384 shutdown"}
{"level":10,"time":1605124534441,"pid":450,"hostname":"LAPTOP-fed","msg":"<IP_ADDRESS>:55384 close; had_err=false"}

This is with ldapjs 2.2.0 and Pino 6.7.0.

Nice catch. Would you like to submit a PR to clean up the tests?

Happy to give it a go.

⚠ This issue has been locked due to age. If you have encountered a recent
problem that seems to be covered by this issue, please open a new issue.
Please include a minimal reproducible example
when opening a new issue.


Create change.md

change test

@Kyooong Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@Kyooong use your own fork to test Github's features.


adding selenium testing for instance section

What was fixed?  (Issue # or description of fix)
Were the changes tested on

[ ] Firefox (Desktop)
[ ] Safari (Desktop)
[ ] Chrome (Desktop)
[ ] Internet Explorer (Desktop)
[ ] iOS (Mobile)
[ ] Android (Mobile)

Running validation tools

[ ] https://validator.w3.org/checklink
[ ] https://validator.w3.org
[ ] Dymanic Accessability Plugin (DAP)

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your<EMAIL_ADDRESS>seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

also you might have to copy these into a new branch PR now that you got your account email fixed so CLA will only make kidus60 sign it


undefined is not an object (evaluating 'window.navigator.userAgent.indexOf')

After I include react-flatpickr and run expo start, I get this error. My include lines are as follows:
import React, { Component } from 'react';
import Flatpickr from 'react-flatpickr';
I have not invoked or used flatpickr in any part of the project yet
react-flatpickr v3.9
react-native v0.59
npm 6.9
node 11.15

I believe this issue would be better raised upstream: https://github.com/flatpickr/flatpickr
However, I don't believe flatpickr has any intention of supporting React Native, so I believe you may need to look elsewhere.
Please feel free to write back if you're sure it's an issue with this library in particular.

I believe this issue would be better raised upstream: https://github.com/flatpickr/flatpickr

I'd be interested to know why that is so. I get this is a fork of sorts, but why would the error be from there?

This is not a fork, it's a wrapper component for the underlying library. It still uses flatpickr under the hood to do virtually all of the heavy lifting.

OK, point taken. I'd still be interested to hear why you think this is an upstream problem though.

Because this library doesn't attempt calling window.navigator.userAgent.indexOf(), flatpickr does.


Remove libodb dependency from vcf-validator

In several instances libodb dependency has prevented the build of vcf-validator on linux or macos-x.
It is used to generate reports that can be easily read by a program namely the vcf-debugulator.
It was decided that the libodb dependency  should be removed but to achieve this we need to

[ ] remove the database report output from vcf-validator
[ ] remove any use of libodb in the vcf-validator code
[ ] remove installation steps in the install_dependencies.sh and install_dependencies.bat
[ ] remove documentation mention of libodb

This is all done since release v0.10.0


Support roasted sweet potato

https://emojipedia.org/roasted-sweet-potato/

Great work! Trym will be pleased with this new feature


Wikidata IDs and updated Wikipedia article titles for all

Got Wikidata IDs for the rest of them by starting with the Wikipedia
titles, auditing them to make sure they were referring to the right
person, and then adding the ID in. I updated page titles for articles
that were renamed; in the future, a script will be able to do this
automatically based on the Wikidata ID. The question is to how to do
this automatically in the long term.

:+1: Thanks!
Yeah, sometimes it's inevitable that there's an audit phase, or that you need to use two fields to help keep each other up to date. We do that with the social media data. My suggestion is to keep the work to one script, and to provide two different modes. Ideally, it'd be fully automatable, but if not, then something that isn't too onerous to run a few times a year.


slower than loop?

I test the threadpool with this code:
#include "util/time_util.h"
#include "ThreadPool/ThreadPool.h"

size_t i = 0;
void test() {
  // printf("hah\n");
  i++;
  i++;
}

#define N 1000000
void fun1() {
  printf("func1\n");
  ThreadPool pool(10);
  for (int i = 0; i < N; ++i) {
    pool.enqueue(test);
  }
}

void fun2() {
  printf("func2\n");
  for (int i = 0; i < N; ++i) {
    test();
  }
}

int main(int argc, char** argv) {
  util::time_util::Timer t;
  t.StartTimer();
  if (argc == 1) {
    fun1();
  } else {
    fun2();
  }
  printf("i=%d\n", i);
  t.EndTimer("1");
}

I found thread pool cost 5s, but loop just cost 0.005s
why threadpool not speed up?

You have basically re-discovered Amdalh's law. Creating the threads and maintaining the queue costs time and the code you execute in the threads is very short. Also, it probably synchronizes on the output as well.

Creating a thread does not mean that dealing with tasks will be fast. u create a pool with 10 threads. creating thread is quiet more expensive than u think.   That's exactly why we need threadpool , avoiding create and destroy threads too many times


Angular workspace with projects

Hi, I was looking into creating a monorepo type project with multiple angular applications, and I decided to go for a project structure workspace, supported by default using the angular cli.
# Create workspace without default application
ng new project-name --createApplication=false
cd project-name
# Generate application, will by default output to /projects/{appName}
ng generate application app1
ng generate application app2
# Add single-spa-angular to configuration for both projects
ng add single-spa-angular@beta --project app1
ng add single-spa-angular@beta --project app2
# Make sure they are both valid single-spa apps
ng build app1 && ng build app2

This will crash, because the builder is unable to locate src/main.single-spa.ts, and in this case the main should be projects/{appName}/src/main.single-spa.ts.
https://github.com/CanopyTax/single-spa-angular/blob/4d396e2961a082b5dc703d64feeeb1ec1d51b9e0/src/schematics/ng-add/index.ts#L74
Also I found an issue with what I'm guessing is this line:
https://github.com/CanopyTax/single-spa-angular/blob/4d396e2961a082b5dc703d64feeeb1ec1d51b9e0/src/builders/single-spa-webpack-builder.ts#L7
Which causes all apps to be exported with the same module name, and replacing the global object when including them e.g.: if app1 is default project:
(function webpackUniversalModuleDefinition(root, factory) {
	if(typeof exports === 'object' && typeof module === 'object')
		module.exports = factory();
	else if(typeof define === 'function' && define.amd)
		define([], factory);
	else if(typeof exports === 'object')
		exports["app1"] = factory();
	else
		root["app1"] = factory();
})

It will actually crash if during registerApplication() as it cannot find the window["appName"].default object.
By manually editing defaultProject to empty string in angular.json:
"defaultProject": ""
You get the expected result.

Fixed with #67

@joeldenning , I started working on a fix for the case where:
https://github.com/CanopyTax/single-spa-angular/blob/4d396e2961a082b5dc703d64feeeb1ec1d51b9e0/src/schematics/ng-add/index.ts#L74
Would solve the fact that every application generated in a workspace points to src/main.single-spa.ts. Unfortunately I didn't have time to finish. But I figured it would be something like:
clientProject.architect['single-spa'].options.main = `${project.workspace.sourcePath}/src/main.single-spa.ts`;

And altering the test case to:
  test('should modify angular.json', () => {
    const tree = testRunner.runSchematic<NgAddOptions>('ng-add', { routing: true, project: 'ss-angular-cli-app' }, defaultAppTree);
    ...
    expect(ssApp.architect['single-spa'].options.main).toBe('src/main.single-spa.ts');
    ...
  });

And the tests passed, but the cli was acting strange. Steps to reproduce would be:
# create new workspace with default application
ng new project
cd project
# add single-spa-angular to default project, seems to work
ng g single-spa-angular:ng-add
# generate new application in project (non-default)
ng generate application app1
ng g single-spa-angular:ng-add --project app1
# This executes successfully, but points to the wrong main.single-spa.ts file, if you delete /projects/app1/src/main.single-spa.ts and re-run: ng g single-spa-angular:ng-add --project app1, it would correct the entry in angular.json to be correct.


Container image

Hi,
I came across this linter project and I'm interested in incorporating it into my CI/CD pipeline. I noticed that the project is not currently available as a container image. Is there any plans to provide the linter as a container image, preferably GHCR or Docker Hub?

Hi @loekensgard 👋 We didn't make it a priority for the first release, but publishing images for those that want that makes sense to me. What CI/CD pipeline platform are you using? Any that only works with containerized tools?
Either way, we'll look into this soon.

We are using GitLab CI/CD, which supports both containerized and non-containerized workflows, however we are strictly using containers to run our pipelines 😄

Good to know! Do they have anything equivalent to GitHub actions that we might want to look into in addition to publishing images for Regal?

This is WIP following #164, I'm just trying to press the right buttons on goreleaser.

Example use
$ cat thing.rego
package things

things {
	thing      = [1, 2, 3][_]
	thing == 4
}

$ docker run -v ${PWD}/thing.rego:/app/thing.rego -it ghcr.io/styrainc/regal:latest lint /app/thing.rego
Rule:         	opa-fmt
Description:  	File should be formatted with `opa fmt`
Category:     	style
Location:     	/app/thing.rego
Documentation:	https://github.com/StyraInc/regal/blob/main/docs/rules/style/opa-fmt.md

1 file linted. 1 violation found.

Yay! Thanks a lot @charlieegan3 👏

Thanks a lot guys @anderseknert @charlieegan3 👏 💯
Already tested and can confirm that it works in my pipeline.

Sweet! We should probably mention this in the README somewhere, but I’m making a note for that later.

That's great, thanks for testing & confirming @loekensgard!
If you've any interest, it'd be great to see Intility on the OPA adopters list 😊


Added spigot and paper 1.14.2 support

Added spigot and paper 1.14.2 support

Closed by my last commit. Please add the next time the commits first.


add INSAT

@SoulaimakH You might miss my previous comment. Please react.

@SoulaimakH I am sorry, this request remains unanswered for a while. I have to close it without merging. Please reopen and comment if you have an update regarding the aforementioned issue. Thank you for your understanding!

On Thu, 11 Nov 2021 at 09:56, soulaima kahla @.***>
wrote:

On Wed, 3 Nov 2021 at 08:23, Philip Torchinsky @.***>
wrote:

Closed #12736 https://github.com/JetBrains/swot/pull/12736.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/JetBrains/swot/pull/12736#event-5559943935, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ARRDZAWTKPSWRXDNMR4X5KLUKDPQ3ANCNFSM5GGLFYAQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Insufficient capacity on K3s (apparently incorrectly)

Describe the bug
On a fresh deployment of k3s, I try to deploy a 1Gi PVC, and the associated pod can't start because:
0/1 nodes are available: 1 Insufficient topolvm.cybozu.com/capacity.

The pod expects:
    Limits:
      topolvm.cybozu.com/capacity:<PHONE_NUMBER>
    Requests:
      topolvm.cybozu.com/capacity:<PHONE_NUMBER>

And the node has:
topolvm.cybozu.com/capacity:<PHONE_NUMBER>6

Environments

Version: K3s 1.17.3
OS: Ubuntu 1804

To Reproduce
Steps to reproduce the behavior:

Deploy TopoLVM per instructions
Create a 1Gi PVC
Create a pod to consume the PVC

Expected behavior
The PVC is correctly allocated from the available space on the node

Update : Turns out that since K3s is not kubeadm-created, I need to manually specify extra scheduler args and volumes. K3s has a --kube-scheduler-arg argument, but nothing to add additional volumes, so for now, I don't see how it's possible to run topolvm on k3s :(


Feature Request: Make export format a bibliography style

Idea
The feature to export a list of citation keys using the LaTeX Citation translator works great. However, I frequently want to send information about a paper to someone and it would be great to have a quick way of copying bibliographic information in a human readable format (e.g. one of the default styles like the Chicago one) as well.
How it could work
If the LaTeX Citation translator could be converted to a Zotero style, one would have two options: copy the citation or the bibliography. Copying the citation could give the citation key whereas the bibliography could give e.g:
Crick, Francis. “Central Dogma of Molecular Biology.” Nature 227, no. 5258 (August 8, 1970): 561–63. doi:10.1038/227561a0.

This would give users two convenient shortcuts (Ctrl + Shift + A and Ctrl + Shift + C) to access both features.
Or is there a way to achieve something similar using translators? To me, the Zotero documentation suggests that this requires a style instead of a translator.

It's a little more complicated than adding a new style. It would require adding a formatter, not a style; writing a formatter is not prohibitively complicated (BBT includes a Markdown formatter, for example), but hooking into the UI is nigh impossible because of the way Zotero implements it. The closest I could come to hooking into the UI is to replace the RTF or HTML export under the covers.
What you want, however, seems doable with the way things are. The LaTeX citation translator isn't really meant to use as an exporter, but to set it as a quick-export, to be used as either drag-and-drop, or to copy to the clipboard using ctrl-shift-c. To copy the bibliography you show above to the clipboard can be done by right-clicking the desired items, selecting "Create bibliography", "Copy to Clipboard", "OK".

To configure the quick-export, see https://zotplus.github.io/better-bibtex/Citation-Keys.html, under "Drag and drop/hotkey citations"

Thank you for the explanations. Since it is not as basic as I thought, I'll close the issue.
I was well aware of the right-click method you mentioned but was hoping that this could be solved more conveniently.
Thank you for your quick reply!

The right-click thingy has a shortcut, I think the default (but configurable) shortcut is Ctrl-Alt-A


chore: Update CHANGELOG.rst

What this PR does / why we need it:
Update CHANGELOG.rst to conform to semantic versioning of the collection.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

None

/approve
/lgtm


sysdump: remove support for standalone hubble

Standalone Hubble is pre-1.8, and hence not supported anymore. This commit removes support for dumping the daemonset + logs + etc..

@bmcustodio looks like this PR needs a rebase after #513 was merged.

Rebased and force pushed because I want to merge this before opening another PR for sysdump, i.e. to avoid merge conflicts on the new PR as well.

After quickly syncing with @michi-covalent out-of-band, it seems we still have some 1.8 users of standalone Hubble. For them it would be useful to still be able to collect standalone hubble info in their sysdump, so l'll postpone merging this PR for a bit to give them a chance to migrate. Thus moving this PR to draft for now.


Docopt, Setuptools, avconv compatibility

I can put this script on PyPi now if you like -- or you can do it yourself! :)
python setup.py register
python setup.py sdist upload [--sign]

That will do the trick.
Hope you like the improvements, thanks for the project.

Btw it works on Python 3

Awesome, thanks! Let me pull this later today!

I'm not on a computer, so if you want, feel free to upload it!

Btw I would recommend that you put it on PyPi yourself, I know almost nothing about ffmpeg, I was just cleaning up the script to support avconv a slight bit... some of the options are not actually implemented for avconv.

Oh okay. Will do, thanks!

Cool, you can find it here:
https://pypi.python.org/pypi/avconv-normalize
Send me your username on PyPi and I'll make sure to add you as admin!

I'm slhck there, too.
I just had a bit of a closer look. To be honest I am not too happy with the name avconv because the tool relies on ffmpeg and those are quite different.
Do you think you could rename everything to audio-normalize as originally created by me when I made this script? That'd make it more easily searchable, too, and it wouldn't imply a dependency on avconv, especially if it's not working with avconv as expected—even the README says ffmpeg.
I can make the commits here in order to rename it, too, just let me know.

That's a good question!! I was under the impression that ffmpeg was being replaced by libav and avconv -- but that was something I didn't even research!
It seems that ffmpeg was abandoned for Debian and Ubuntu around when Jessie and 14.04 + 14.10 were released. But it's been back since 15.04 and is in Debian testing and unstable again.
Would you like if we name the project ffmpeg-normalize ? I think it'd be cool to have "ffmpeg" in the name, because its so tightly coupled to it.

Yeah, that'd make much more sense! I
('m also not quite happy with the way avconv was put into Ubuntu, making it sound like ffmpeg was dead, which it certainly isn't.)


Test failed: requirements.txt

Keras version not found. We need to change it

We are using the newer version of tensorflow and so we do not require an extra keras library. I will remove the keras library in requirements file and add the appropriate tensorflow version.

We need to remove the excess libraries now: pandas, scikit learn

Yes, I am removing scikit-learn, pandas, wheel, pip and keras.

I have updated the requirements.txt file to add an appropriate TensorFlow version and removed excess libraries.


2.0 - splitting normalised types

A breaking change will remove the normalized types, as those could change and have a bit more opinion embedded.

First half added here: https://github.com/IIIF-Commons/presentation-3-normalized
Second half is to remove from this library (2.0 - as it's breaking)


Removing PHP short tags as per WP theme review standards

PHP short tags, such as <?=$variable?>, are disabled by many web hosts and therefore discouraged according to the WP theme review standards
Removing all instances of short tags being used in favor of more verbose alternative <? echo $variable ?>

@basteln3rk This is going to get closed. Sage by default requires PHP5.4+, where short_open_tags are always available.

What @mAAdhaTTah said.

Thank you for taking the time to put together a pull request. However, like @mAAdhaTTah said, Sage requires PHP 5.4+. 5.4 came out in 2012 and has even reached the end of its active support cycle.  http://php.net/supported-versions.php.


Sip proxy

Hello,
is there anyway to add sip proxy to the configuration?
for example in sipML5 there is proxy server 'ns313841.ovh.net'
can be found here
https://github.com/DoubangoTelecom/sipml5/search?utf8=✓&q=ns313841.ovh.net
it's useful to fix audio problems
please advice
Thanks

sipML5 is a different product that sip.js. I don't have a proxy setup to test, but try this...
In scripts/app.js, edit the config object to add a registrarServer property.
config : {
            password        : user.Pass,
            displayName     : user.Display,
            uri<EMAIL_ADDRESS>            wsServers       : user.WSServer,
            registerExpires : 30,
            traceSip        : true,

            //
            registrarServer: 'sip:registrar.mydomain.com'
            log             : {
                level : 3,
            }
        },
       ...

If it works, submit a PR or let me know and I will add it.

i think the the outbound proxy could be set by using the following config option
usePreloadedRoute: true
but then, line 3906 in sip.js
this.setHeader('route', ua.transport.server.sip_uri);
need to be fixed to accommodate this config option


Python3 Unit Test Error test_tree_editor_text

The following unit test error occured on the Python 3 branch:
======================================================================
ERROR: test_tree_editor_text (app.tests.LicenseXMLEditorTestCase)
Test for adding, editing and deleting text inside tags using tree editor
----------------------------------------------------------------------
Traceback (most recent call last):
  File "C:\Users\gary\git\spdx-online-tools\src\app\tests.py", line 856, in test_tree_editor_text
    finalXML += i.text.strip()
  File "C:\Users\gary\git\spdx-online-tools\venv\lib\site-packages\selenium\webdriver\remote\webelement.py", line 76, in text
    return self._execute(Command.GET_ELEMENT_TEXT)['value']
  File "C:\Users\gary\git\spdx-online-tools\venv\lib\site-packages\selenium\webdriver\remote\webelement.py", line 633, in _execute
    return self._parent.execute(command, params)
  File "C:\Users\gary\git\spdx-online-tools\venv\lib\site-packages\selenium\webdriver\remote\webdriver.py", line 321, in execute
    self.error_handler.check_response(response)
  File "C:\Users\gary\git\spdx-online-tools\venv\lib\site-packages\selenium\webdriver\remote\errorhandler.py", line 242, in check_response
    raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.StaleElementReferenceException: Message: The element reference of <pre class=" CodeMirror-line "> is stale; either the element is no longer attached to the DOM, it is not in the current frame context, or the document has been refreshed

Hi @goneall, does this issue still persists or it has been solved?
If not, I would be happy to contribute to this

@BassCoder2808 I don't recall this being fixed - although there have been a few changes to the unit tests since this issue was opened.  If you could run the unit tests locally and see if this error occurs, we can either close this as resolved or fix.  Thanks.

Hi @goneall. I ran the test in my local machine and the test is passed.  I think the issue has been fixed now.

Hi @BanulaKumarage - Thanks for checking - I'll go ahead and close this issue.


Express Issue-2893

Added a logical check in express response send to keep from setting the content-length header when the transfer encoding is set to chunked.

Hi! The Transfer-Encoding is actually a comma-separated field, so may be chunked and other values, which this pull request is not handling correctly. Also, please see my comments in https://github.com/expressjs/express/issues/2893#issuecomment-185844440 regarding my thoughts on a fix, which doesn't seem to be reflected here.
You can see our contributing guide https://github.com/expressjs/express/blob/master/Contributing.md to help with contributing, in particular, this pull request was made against the wrong branch.
Can you alter the pull request to better handle all the different Transfer-Encoding cases, like comma-separated values? It should also use this.get rather than .getHeader to use our API internally.

I'm going to close this, because of the issues with this PR above, but mainly because it turns out, this is a bug in the express-http-proxy module with a fix here: https://github.com/villadora/express-http-proxy/pull/47
The changes in Express here is just a weird band-aid that just hides the bug in another module, rather than a truly desirable change.


Update to latest reflex-platform with GHC 8.4

Tests are failing and I have no idea why all good now!

Does GHCjs support GHC 8.4?

Oh, interesting. @mightybyte

Tested with Stack locally and I'm seeing the same hash change, so I'm marking this no longer WiP.

CI is happy \o/

*Addressed.

@slpopejoy I'm good with merging this whenever you think is appropriate.

Thanks!


Consider dropping or using the fetch polyfill

I like what I've seen of Aurelia, but I was surprised with such a forward focus that you still have a http module.
given the new fetch standard (implemented in chrome today, firefox very soon - http://caniuse.com/#feat=fetch) and fetch polyfill - https://github.com/github/fetch, would it be better to either abandon this part of Aurelia or if it does provide functionality over fetch (sorry, have only looked at the basic features) then base this on top of fetch instead of XmlHttpRequest ?

We have looked into fetch and we were considering whether or not we should base our http library on it or if we should create a separate library. I haven't thought about it a little bit though. @bryanrsmith would you look into this and see what your recommendation would be? Is there a way to alter our HttpClient implementation without making a breaking change in the API? If not, could be build a fetch-based implementation that was similar and easy to migrate to, with the same features?

There are two significant features that aurelia-http-client provides that fetch doesn't directly support.

JSONP
Application-level management of requests. Interceptors, default configuration for things like base URL, centralized request tracking for global activity indicators, etc.

IMO, the fetch API is quite nice and well suited for direct use without a wrapping library. We certainly could integrate it here, but I don't think we'd stand to gain much. fetch already provides most of the same functionality, and it would be awkward to map some of fetch's more advanced features to this API.
I think we should aim for building a new library with a very thin wrapper around fetch. Just enough to let us inject the application-level stuff like interceptors, and maybe make testing a little easier. I think JSONP is different enough that we could tack on a little helper method adjacent to the fetch wrapper instead of abstracting it away. That would give us a lot less code to maintain, and help avoid breakages as the fetch API evolves.

Sounds good!

We've got a new fetch plugin which you can not use in place of the http-client in you prefer :)

Link for convenience: https://github.com/aurelia/fetch-client. Docs coming :-)


Hamamatsu

Description

Type of change

[ ] Bug-fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

References

How has this been tested?

[ ] example: the test suite for my feature covers cases x, y, and z
[ ] example: all tests pass with my change

Final checklist:

[ ] My PR is the minimum possible work for the desired functionality
[ ] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works

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

In the file piescope/fibsem.py:

Line 39:29: E231 missing whitespace after ':'

In the file piescope/lm/dcam/dcam.py:

Line 5:80: E501 line too long (94 > 79 characters)
Line 62:80: E501 line too long (86 > 79 characters)
Line 63:80: E501 line too long (101 > 79 characters)
Line 88:80: E501 line too long (90 > 79 characters)
Line 89:80: E501 line too long (81 > 79 characters)
Line 93:80: E501 line too long (108 > 79 characters)
Line 96:80: E501 line too long (99 > 79 characters)
Line 184:80: E501 line too long (81 > 79 characters)
Line 191:80: E501 line too long (108 > 79 characters)
Line 194:80: E501 line too long (97 > 79 characters)
Line 265:80: E501 line too long (86 > 79 characters)
Line 287:80: E501 line too long (86 > 79 characters)
Line 290:80: E501 line too long (84 > 79 characters)
Line 309:80: E501 line too long (86 > 79 characters)
Line 323:80: E501 line too long (85 > 79 characters)
Line 330:80: E501 line too long (86 > 79 characters)
Line 334:80: E501 line too long (96 > 79 characters)
Line 353:80: E501 line too long (86 > 79 characters)
Line 357:80: E501 line too long (95 > 79 characters)
Line 372:80: E501 line too long (94 > 79 characters)
Line 375:80: E501 line too long (86 > 79 characters)
Line 380:80: E501 line too long (86 > 79 characters)
Line 398:80: E501 line too long (86 > 79 characters)
Line 401:80: E501 line too long (93 > 79 characters)
Line 420:80: E501 line too long (86 > 79 characters)
Line 427:80: E501 line too long (87 > 79 characters)
Line 444:80: E501 line too long (80 > 79 characters)
Line 447:80: E501 line too long (86 > 79 characters)
Line 454:80: E501 line too long (80 > 79 characters)
Line 462:80: E501 line too long (95 > 79 characters)
Line 465:80: E501 line too long (86 > 79 characters)
Line 482:80: E501 line too long (86 > 79 characters)
Line 544:80: E501 line too long (86 > 79 characters)
Line 572:80: E501 line too long (86 > 79 characters)
Line 585:80: E501 line too long (86 > 79 characters)
Line 606:80: E501 line too long (86 > 79 characters)
Line 609:80: E501 line too long (89 > 79 characters)
Line 624:80: E501 line too long (86 > 79 characters)
Line 634:5: E303 too many blank lines (2)
Line 636:5: E301 expected 1 blank line, found 0
Line 689:80: E501 line too long (84 > 79 characters)
Line 714:1: W391 blank line at end of file

In the file piescope/lm/dcam/dcam_live_capturing.py:

Line 35:1: W293 blank line contains whitespace
Line 63:80: E501 line too long (84 > 79 characters)
Line 69:80: E501 line too long (87 > 79 characters)
Line 73:80: E501 line too long (103 > 79 characters)
Line 78:80: E501 line too long (81 > 79 characters)
Line 89:80: E501 line too long (82 > 79 characters)
Line 97:80: E501 line too long (90 > 79 characters)
Line 100:80: E501 line too long (84 > 79 characters)
Line 102:80: E501 line too long (82 > 79 characters)

In the file piescope/lm/dcam/dcam_show_device_list.py:

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

In the file piescope/lm/dcam/dcam_show_properties.py:

Line 14:1: E302 expected 2 blank lines, found 1
Line 21:1: W293 blank line contains whitespace
Line 35:80: E501 line too long (84 > 79 characters)
Line 37:80: E501 line too long (82 > 79 characters)

In the file piescope/lm/dcam/dcam_show_single_captured_image.py:

Line 62:80: E501 line too long (87 > 79 characters)
Line 74:80: E501 line too long (91 > 79 characters)
Line 77:80: E501 line too long (93 > 79 characters)
Line 81:80: E501 line too long (90 > 79 characters)
Line 84:80: E501 line too long (84 > 79 characters)
Line 86:80: E501 line too long (82 > 79 characters)

In the file piescope/lm/dcam/dcamapi4.py:

Line 28:80: E501 line too long (81 > 79 characters)
Line 29:80: E501 line too long (81 > 79 characters)
Line 31:80: E501 line too long (85 > 79 characters)
Line 33:80: E501 line too long (102 > 79 characters)
Line 34:80: E501 line too long (81 > 79 characters)
Line 35:80: E501 line too long (112 > 79 characters)
Line 40:80: E501 line too long (104 > 79 characters)
Line 51:80: E501 line too long (122 > 79 characters)
Line 54:80: E501 line too long (80 > 79 characters)
Line 55:80: E501 line too long (82 > 79 characters)
Line 66:80: E501 line too long (117 > 79 characters)
Line 67:80: E501 line too long (111 > 79 characters)
Line 68:80: E501 line too long (106 > 79 characters)
Line 69:80: E501 line too long (104 > 79 characters)
Line 70:80: E501 line too long (101 > 79 characters)
Line 71:80: E501 line too long (212 > 79 characters)
Line 72:80: E501 line too long (94 > 79 characters)
Line 73:80: E501 line too long (82 > 79 characters)
Line 74:80: E501 line too long (88 > 79 characters)
Line 75:80: E501 line too long (90 > 79 characters)
Line 76:80: E501 line too long (118 > 79 characters)
Line 78:80: E501 line too long (81 > 79 characters)
Line 79:80: E501 line too long (100 > 79 characters)
Line 80:80: E501 line too long (130 > 79 characters)
Line 81:80: E501 line too long (124 > 79 characters)
Line 82:80: E501 line too long (121 > 79 characters)
Line 83:80: E501 line too long (98 > 79 characters)
Line 84:80: E501 line too long (150 > 79 characters)
Line 85:80: E501 line too long (114 > 79 characters)
Line 88:80: E501 line too long (83 > 79 characters)
Line 89:80: E501 line too long (85 > 79 characters)
Line 90:80: E501 line too long (94 > 79 characters)
Line 92:80: E501 line too long (122 > 79 characters)
Line 94:80: E501 line too long (85 > 79 characters)
Line 95:80: E501 line too long (85 > 79 characters)
Line 96:80: E501 line too long (85 > 79 characters)
Line 97:80: E501 line too long (85 > 79 characters)
Line 98:80: E501 line too long (85 > 79 characters)
Line 99:80: E501 line too long (82 > 79 characters)
Line 101:80: E501 line too long (81 > 79 characters)
Line 104:80: E501 line too long (83 > 79 characters)
Line 105:80: E501 line too long (98 > 79 characters)
Line 106:80: E501 line too long (102 > 79 characters)
Line 108:80: E501 line too long (122 > 79 characters)
Line 109:80: E501 line too long (110 > 79 characters)
Line 110:80: E501 line too long (86 > 79 characters)
Line 111:80: E501 line too long (106 > 79 characters)
Line 112:80: E501 line too long (127 > 79 characters)
Line 113:80: E501 line too long (88 > 79 characters)
Line 114:80: E501 line too long (84 > 79 characters)
Line 130:80: E501 line too long (127 > 79 characters)
Line 132:80: E501 line too long (97 > 79 characters)
Line 133:80: E501 line too long (87 > 79 characters)
Line 136:80: E501 line too long (142 > 79 characters)
Line 137:80: E501 line too long (125 > 79 characters)
Line 138:80: E501 line too long (122 > 79 characters)
Line 140:80: E501 line too long (92 > 79 characters)
Line 143:5: E303 too many blank lines (2)
Line 147:80: E501 line too long (81 > 79 characters)
Line 235:80: E501 line too long (91 > 79 characters)
Line 236:80: E501 line too long (87 > 79 characters)
Line 238:80: E501 line too long (100 > 79 characters)
Line 239:80: E501 line too long (99 > 79 characters)
Line 241:80: E501 line too long (97 > 79 characters)
Line 242:80: E501 line too long (106 > 79 characters)
Line 243:80: E501 line too long (87 > 79 characters)
Line 244:80: E501 line too long (89 > 79 characters)
Line 245:80: E501 line too long (87 > 79 characters)
Line 246:80: E501 line too long (82 > 79 characters)
Line 247:80: E501 line too long (83 > 79 characters)
Line 248:80: E501 line too long (81 > 79 characters)
Line 249:80: E501 line too long (96 > 79 characters)
Line 250:80: E501 line too long (100 > 79 characters)
Line 252:80: E501 line too long (89 > 79 characters)
Line 254:80: E501 line too long (97 > 79 characters)
Line 255:80: E501 line too long (83 > 79 characters)
Line 256:80: E501 line too long (90 > 79 characters)
Line 260:80: E501 line too long (87 > 79 characters)
Line 261:80: E501 line too long (88 > 79 characters)
Line 262:80: E501 line too long (89 > 79 characters)
Line 263:80: E501 line too long (88 > 79 characters)
Line 264:80: E501 line too long (87 > 79 characters)
Line 273:80: E501 line too long (81 > 79 characters)
Line 275:80: E501 line too long (83 > 79 characters)
Line 276:80: E501 line too long (83 > 79 characters)
Line 277:80: E501 line too long (82 > 79 characters)
Line 278:80: E501 line too long (98 > 79 characters)
Line 279:80: E501 line too long (86 > 79 characters)
Line 280:80: E501 line too long (81 > 79 characters)
Line 282:80: E501 line too long (80 > 79 characters)
Line 284:80: E501 line too long (93 > 79 characters)
Line 285:80: E501 line too long (82 > 79 characters)
Line 287:80: E501 line too long (88 > 79 characters)
Line 288:80: E501 line too long (88 > 79 characters)
Line 289:80: E501 line too long (88 > 79 characters)
Line 290:80: E501 line too long (95 > 79 characters)
Line 291:80: E501 line too long (93 > 79 characters)
Line 293:80: E501 line too long (80 > 79 characters)
Line 298:80: E501 line too long (89 > 79 characters)
Line 300:80: E501 line too long (96 > 79 characters)
Line 301:80: E501 line too long (97 > 79 characters)
Line 302:80: E501 line too long (104 > 79 characters)
Line 307:80: E501 line too long (97 > 79 characters)
Line 308:80: E501 line too long (90 > 79 characters)
Line 310:80: E501 line too long (111 > 79 characters)
Line 311:80: E501 line too long (112 > 79 characters)
Line 312:80: E501 line too long (117 > 79 characters)
Line 315:80: E501 line too long (87 > 79 characters)
Line 318:80: E501 line too long (80 > 79 characters)
Line 320:80: E501 line too long (83 > 79 characters)
Line 321:80: E501 line too long (100 > 79 characters)
Line 323:80: E501 line too long (104 > 79 characters)
Line 324:80: E501 line too long (86 > 79 characters)
Line 325:80: E501 line too long (95 > 79 characters)
Line 326:80: E501 line too long (80 > 79 characters)
Line 327:80: E501 line too long (91 > 79 characters)
Line 328:80: E501 line too long (102 > 79 characters)
Line 329:80: E501 line too long (82 > 79 characters)
Line 330:80: E501 line too long (82 > 79 characters)
Line 331:80: E501 line too long (108 > 79 characters)
Line 332:80: E501 line too long (87 > 79 characters)
Line 333:80: E501 line too long (98 > 79 characters)
Line 334:80: E501 line too long (116 > 79 characters)
Line 335:80: E501 line too long (82 > 79 characters)
Line 337:80: E501 line too long (90 > 79 characters)
Line 342:80: E501 line too long (80 > 79 characters)
Line 343:80: E501 line too long (80 > 79 characters)
Line 344:80: E501 line too long (90 > 79 characters)
Line 345:80: E501 line too long (90 > 79 characters)
Line 347:80: E501 line too long (89 > 79 characters)
Line 348:80: E501 line too long (104 > 79 characters)
Line 349:80: E501 line too long (105 > 79 characters)
Line 351:80: E501 line too long (83 > 79 characters)
Line 354:80: E501 line too long (83 > 79 characters)
Line 355:80: E501 line too long (81 > 79 characters)
Line 368:80: E501 line too long (99 > 79 characters)
Line 369:80: E501 line too long (99 > 79 characters)
Line 372:80: E501 line too long (89 > 79 characters)
Line 376:80: E501 line too long (87 > 79 characters)
Line 378:80: E501 line too long (81 > 79 characters)
Line 383:80: E501 line too long (81 > 79 characters)
Line 391:80: E501 line too long (87 > 79 characters)
Line 392:80: E501 line too long (81 > 79 characters)
Line 393:80: E501 line too long (81 > 79 characters)
Line 396:80: E501 line too long (81 > 79 characters)
Line 397:80: E501 line too long (98 > 79 characters)
Line 398:80: E501 line too long (101 > 79 characters)
Line 400:80: E501 line too long (101 > 79 characters)
Line 402:80: E501 line too long (93 > 79 characters)
Line 403:80: E501 line too long (90 > 79 characters)
Line 404:80: E501 line too long (98 > 79 characters)
Line 405:80: E501 line too long (81 > 79 characters)
Line 406:80: E501 line too long (89 > 79 characters)
Line 407:80: E501 line too long (80 > 79 characters)
Line 408:80: E501 line too long (82 > 79 characters)
Line 409:80: E501 line too long (88 > 79 characters)
Line 411:80: E501 line too long (81 > 79 characters)
Line 412:80: E501 line too long (82 > 79 characters)
Line 413:80: E501 line too long (91 > 79 characters)
Line 414:80: E501 line too long (90 > 79 characters)
Line 423:80: E501 line too long (82 > 79 characters)
Line 431:80: E501 line too long (86 > 79 characters)
Line 432:80: E501 line too long (80 > 79 characters)
Line 433:80: E501 line too long (97 > 79 characters)
Line 435:80: E501 line too long (98 > 79 characters)
Line 438:80: E501 line too long (80 > 79 characters)
Line 439:80: E501 line too long (86 > 79 characters)
Line 440:80: E501 line too long (98 > 79 characters)
Line 444:80: E501 line too long (80 > 79 characters)
Line 446:80: E501 line too long (80 > 79 characters)
Line 449:80: E501 line too long (82 > 79 characters)
Line 454:80: E501 line too long (81 > 79 characters)
Line 455:80: E501 line too long (90 > 79 characters)
Line 456:80: E501 line too long (89 > 79 characters)
Line 457:80: E501 line too long (81 > 79 characters)
Line 458:80: E501 line too long (87 > 79 characters)
Line 462:80: E501 line too long (80 > 79 characters)
Line 463:80: E501 line too long (99 > 79 characters)
Line 465:80: E501 line too long (83 > 79 characters)
Line 467:80: E501 line too long (83 > 79 characters)
Line 468:80: E501 line too long (84 > 79 characters)
Line 473:80: E501 line too long (83 > 79 characters)
Line 479:80: E501 line too long (88 > 79 characters)
Line 481:80: E501 line too long (94 > 79 characters)
Line 483:80: E501 line too long (94 > 79 characters)
Line 484:80: E501 line too long (96 > 79 characters)
Line 486:80: E501 line too long (104 > 79 characters)
Line 488:80: E501 line too long (80 > 79 characters)
Line 489:80: E501 line too long (80 > 79 characters)
Line 491:80: E501 line too long (80 > 79 characters)
Line 494:80: E501 line too long (80 > 79 characters)
Line 496:80: E501 line too long (82 > 79 characters)
Line 497:80: E501 line too long (80 > 79 characters)
Line 498:80: E501 line too long (90 > 79 characters)
Line 503:80: E501 line too long (93 > 79 characters)
Line 504:80: E501 line too long (94 > 79 characters)
Line 598:80: E501 line too long (91 > 79 characters)
Line 602:1: E303 too many blank lines (3)
Line 1038:1: E302 expected 2 blank lines, found 1
Line 1089:80: E501 line too long (87 > 79 characters)
Line 1336:1: W391 blank line at end of file

In the file piescope/lm/detector.py:

Line 122:1: E302 expected 2 blank lines, found 1
Line 154:1: W293 blank line contains whitespace
Line 157:80: E501 line too long (82 > 79 characters)
Line 159:80: E501 line too long (87 > 79 characters)
Line 167:35: W291 trailing whitespace
Line 168:1: W293 blank line contains whitespace


Move all class parameters to delcaration

Anything that acts as input to Class needs to sit in function declaration

fixed in #40


Themekit compatibility with new schema options

Is your feature request related to a problem? Please describe.
There is a new way to build themes which was just announced. It's in preview as of this moment, but I'd like to play around with it: https://help.shopify.com/en/themes/development/section-themes
Currently when I try out the new code, I get "Invalid schema: 'content' is not a valid attribute".
Describe the solution you'd like
What is the timeline for this functionality being added to themekit so anyone developing with it won't fall behind, or be forced to use only the in store developer?
Describe alternatives you've considered
Waiting. Patiently. :)

Themekit already supports this. The sections feature currently only enabled on development stores which have the dev preview enabled.
You can find documentation for how to create a development store here: https://help.shopify.com/en/partners/dashboard/development-stores#create-a-development-store
And documentation on developer previews here:
https://help.shopify.com/en/api/versioning/developer-preview
If you are working on a dev-store with previews and it is still not working, I think you should contact support as they will be more likely to be able to help from there.

That was fast. 👍
Thank you @tanema

@shikkaba You also can't develop any new section features on old Dev stores. You need to create a new Dev Store to be able to enable developer preview mode.


Database of open neuroimaging datasets

Let's build up a list of data sets that might be interesting.

UK Biobank

Don't need to do this any more! Chris Madan (@cMadan) has done it already!! https://github.com/cMadan/openMorph
Possibly add link to his repository to our documentation :smile:


Rasa X installation taking long<

[Rasa X installation taking   ##long<]

windows10 64bit
Rasa Version : 2.3.0
Rasa SDK Version : 2.3.1
Python Version : 3.7.6
pip  Version : 21.0.1

Thanks for raising this issue, @alopez will get back to you about it soon✨
Please also check out the docs and the forum in case your issue was raised there too 🤗

Hey, have you found a solution to solve the issue? It is a pip issue. Please see the discussion here.


Feature: Function arguments autocomplete

Is your feature request related to a problem?
When autocompleting a function you get the name but not what arguments it takes, it would be handy to get this info hinted too
(name: type, name2: type, name3: type)
Initial hint

First arg hint

Second arg hint

Describe the solution
Adding tooltip hinting for args:types, and hinting while typing arguments(dismissable(esc), rehintable at current arg with ctrl+space/, next arg
Are you willing to contribute this feature
No
Surrealist Environment
Version: 3.0.0-beta.1
Flags: feature_flags: false, query_view: true, explorer_view: true, graphql_view: true, designer_view: true, auth_view: true, functions_view: true, models_view: true, apidocs_view: true, cloud_view: true, themes: true, newsfeed: true, database_version_check: false, highlight_tool: false, legacy_serve: false, cloud_endpoints: production, cloud_access: false, changelog: hidden
Contact Details
<EMAIL_ADDRESS>Is there an existing issue for this?

[X] I have searched the existing issues

Code of Conduct

[X] I agree to follow this project's Code of Conduct

While intelligent function completion will take me some more time, on a related topic, I did improve the auto completion of arguments within the function editor (#417)


Entry point assertion class for custom assertions

Currently, assertThat methods from custom asserts(SpanAssert,
SpansAssert, TracerAssert) do not have an entry point assertion
class. Hence, users need to static import individual assert classes.
This change introduces an entry point assertion class. Users now simply
static import this class and all assertThat methods are available for
use.

@ttddyy The build is failing because of tabs vs. spaces, could you please fix it?
(The .editorconfig contains this rule so if you get your IDE to use it, it should fix it automatically.)

@jonatan-ivanov ok, I have applied the rule and updated the PR.


Unable to select or identify these autocompletion suggetions

I am unable to identify where this autocompletion is coming from. I cannot even select them either through tab/enter/shift-tab/enter.  This type of suggestion comes when I have already chosen an autocompletion from the buffer or something then after that they are auto-suggestions and it even makes it harder to navigate after that.  Please see the screenshots attached below.
The second screenshot with the suggestion with [A]/[B] is the one I am talking about. Thanks for the help.

The autocompletion(false: keyword) is from the LSP.
Regarding the issue with tab etc, what terminal are you using?

iterm
In the second screenshot suggestion(task_runner [A]) is what I asking about. Cause I am unable to toggle it off.

Have you tried using the escape button?

Yes, That works as it's going to normal mode. So all suggestions get toggled off automatically. Do you know where does this specifically comes from ?

 I will try checking every plugin.  Thanks for the help!

That is very weird. Do you have your configuration somewhere so I can debug it locally?

I was using your config with some changes. I am not sure what was the problem when I updated to this new it went off. I had the same configuration on my other machine with arch Linux on it. It didn't have that issue.


Chinese: MARC field option is ignored

Source string: 欒保羣
Result: Luan bao qun
Expected result: Luan, Baoqun
Other examples involving the MARC field option are behaving similarly. This may be a regression from the DB migration.
@tventimi FYI

On a second look, it looks like I had never implemented this functionality. I had used the MARC field for numeral parsing, but in https://github.com/lcnetdev/scriptshifter/blob/main/tests/data/script_samples/chinese.csv some tests mention fields 100 and 700 are to be handled as names where a comma is added. @tventimi can you provide more details on this logic?

See the following code snippet from Parallelogram:
https://github.com/pulibrary/parallelogram/blob/main/cloudapp/src/app/pinyin.service.ts#L135-L149
This code is run on the romanized version of the name.  It is assumed that the name consists of two or three separate "words".  The first word is capitalized and followed by a comma.  The second word is also capitalized.  If there is a third word, it is appended to the second one with no capitalization and no space in between.  However, if the third word begins with a vowel, then an apostrophe is placed between the second and third words.  Thus,
Luan bao quan --> Luan, Baoquan
Wen dao an --> Wen, Dao'an
Xia jing --> Xia, Jing
Sima qian --> Sima, Qian
Note that in the last example, the surname is multisyllable and corresponds to two Chinese characters (司马).  However, the code doesn't need to know this because these characters have already been romanized and written as a single word by the time it reaches this point in the code.
Also note that the code snippet above applies this logic to subfield r of any MARC field, but in such cases, the comma after the first word is omitted.

In the code snippet you linked to, what do the tag, ind1, and code variables represent?

Fixed in #139.

@tventimi can you please test? I only had Sima, Qian in Chinese script to test with.
I might have to adjust the code to select the MARC field. At the moment it only applies to 100, 600, 700, 800.

I tested some more examples and confirmed that the name formatting is correct.


Search filters

We should be able to apply a search filter on a column and only display results that fit the filter.  Probably just a simple substring match to start.

Watching this repo, any progress? Is pull request is welcome?

Hey there, I haven't had a chance to work on this issue yet.  Pull request is welcome for this one!

@alswl I've implemented sorting which may have some overlap in terms of dealing iwth string values and nested StyledColumn values as part of #27 , but it's all mostly in new files so hopefully it doesn't collide too much if you've started work on this.  Let me know.

@Evertras I haven't started yet.

Will close this after I bump the coverage back up 🎊


Adrino: new native adapter

This is a new adapter for Adrino unique demand.

Hello @bretg. Thanks for approval. Our adapter has been merged into master branch and released within 6.15.0 version. Should we do something to make this documentation available on the prebid official site or should we simple wait?

@tmielcarz just merged this in 👍 So you should be good to go on docs for your new adapter.

@ChrisHuie, thanks :)


Proper error handling

Currently most rejected promises are handled by the node process. Errors should be properly caught and logged. The error handling should ~not~ be done as simple as possible as the whole mine code is under heavy development.
Acceptance Criteria:

no more (node:51252) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): AssertionError [ERR_ASSERTION]: mineAddress should be a hexstring
light, minimum invasive approach to logging (do not wrap each command)

Hi! First time contributor to OpenMined here, I would like to take this up, if possible.

Hey @OrthoDex feel free to jump in. I just realised I wrote should not be done as simple as possible however it SHOULD. Fixed the original text. Will assign the issue to you and looking forward to a PR.


Removes hard-coding to /bin/bash

On OS/X /bin/bash is not new enough to work.

Oh, so you do have a newer bash, it just doesn't overwrite /bin/bash. Makes sense, thanks!

yepperie homebrew likes to stay in /usr/local


fix: add build step for types

I think we need to add the build step to generate the types as they are used in the packages like @warp-ds/react and was generated in https://github.com/fabric-ds/css
https://github.com/fabric-ds/css/blob/next/tsconfig.json#L13

dist folder feels weird here just for the types.
Is it a problem to just gitignore the type-declaration file and use that in-place? Typescript would pick up on that automatically then.

dist folder feels weird here just for the types.
Is it a problem to just gitignore the type-declaration file and use that in-place? Typescript would pick up on that automatically then.

Yea, I agree. Thought that it was some sort of standard way to do it looking at @fabric-ds/css setup. I'll adjust 🙌

The types declaration in package.json isn't needed, but doesn't hurt anything being there.

I thought it could be there for some sort of transparency


Storaji don't save prefered language

When I quit program it's in english again, not polish like I set.

Fixed on https://github.com/IndomaximTechID/storaji-ui/commit/02b1fda58862c35e51d6cceff10cae5a10c79de9 :+1:


Make targets package a dev dependency and fix package supplier trimming

Fixes https://github.com/microsoft/sbom-tool/issues/713
Fixes https://github.com/microsoft/sbom-tool/issues/714

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 66.72%. Comparing base (7b69133) to head (80a51b8).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #726      +/-   ##
==========================================
- Coverage   70.00%   66.72%   -3.28%
==========================================
  Files         277      277
  Lines        8630     8630
  Branches     1004     1004
==========================================
- Hits         6041     5758     -283
- Misses       2071     2362     +291
+ Partials      518      510       -8

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[google_maps_flutter_web] An example to update a marker position

How I update a marker's position, does anyone have an example? I've tried in several ways

Checkout here
https://github.com/flutter/flutter/issues/65255

@celsoncustodio
Check above comment and see if it answers your question.

Checkout here
#65255
& example is https://dit-maps-tests.web.app/#/

I did not understand.. i have try use setstate, but have not sucess, do u have a simple code example

@celsoncustodio
Check out this issue and this solution and see if it helps.

But such example is with List objectand Google Map accepts as marker parameter only Set object.

@neoacevedo  Originally when you  change the markers list and then call set state that should update the markers automatically because setState(){} while updating the app states sees that the original list data has been changed and in turn, this should update the GoogleMap widget.  but for some reason it is not happening, that is the reason I explicitly called the implementation functions.
Now I think there is no need of calling the functions explicitly, pass a key to the google map widget and then call setState((){}); after updating the marker list
pass it to the map by using Set<Marker>.from(myMarkers)
this should work now, because now didUpdateWidget(oldWidget) is overridden in the new version of the plugin and this should update the markers position without need of explicitly calling the implementation methods.

@darshankawar @Maverick099
didn't work yet
i'm using in flutter web, i think maybe is different then mobile, because of some bug
obs: in mobile i can update marker position normaly.
` setState(() {
var setmarkersnew= markersnew.toSet();
      MarkerUpdates.from(
          Set<Marker>.from(setmarkers), Set<Marker>.from(setmarkersnew));
      setmarkers = [] as Set<Marker>;
      setmarkers = setmarkersnew;
    });`

Cc: @ditman

Thanks for bringing this to my attention. I'm going to close #65255 and use this one as tracking for both the issue of markers not updating correctly, and making sure the example is understandable.
I'll revisit this soon, once the first wave of web plugins migrated to null-safety lands!

@Maverick099 Good, I created another project, only with google maps, Location package and a marker, without navigation, no timers or any other widget needed to be updated via setState, and it works good; in my current and private project I navigate from one screen to the next one where I have 1 timer firing around each 10 secs, the Location package and may widgets including google maps and the marker I want to update its location. Inside the location listener I try to update the marker location when the location changes and here is when I get the map flickering.
The code where I update the marker is inside the onMapCreated method:
  void _onMapCreated(GoogleMapController controller) {
    mapController = controller;
    _locationSubscription =
        location.onLocationChanged.listen((currentLocation) {
      // Controlar que con cualquier salto del GPS, no se mueva si no se está en movimiento.
      if (currentLocation.accuracy <= 8 && currentLocation.speed >= 1) {
        _center = LatLng(currentLocation.latitude, currentLocation.longitude);
        if (mapController != null) {
          markerDriverLocation =
              markerDriverLocation.copyWith(positionParam: _center);

          // Centrar el mapa
          mapController.animateCamera(CameraUpdate.newCameraPosition(
              CameraPosition(
                  target: LatLng(_center.latitude, _center.longitude),
                  zoom: zoom)));
          setState(() {
            _markers[markerDriverId] = markerDriverLocation;
          });
        }
      }
    });
  }

The screen has more or less the following structure:
WillPop
- MaterialApp
-- Scaffold
--- AppBar
--- SizedBox
---- Column
----- Container
------ Widget1
----- Container
------ Container
------- GoogleMaps

I did it this way, but the markers are flashing, someone would have another alternative ?

In a very basic example, the map never flicks, for instance: https://github.com/flutter/flutter/issues/43785#issuecomment-790855719
But in a very more complex implementation, as I described in a previous comment, the map flicks on each location update.

I'm migrating the google_maps_flutter_web package to null-safety, and the latest version of the example app seems to work as expected; in the "Place marker" demo, after clicking "add" to add a marker, then selecting the marker and clicking "toggle draggable", the marker can be moved around.
The UI of that demo is not the best, but it seems that moving the marker is working?
The refreshing of the map, might be this issue issue related to platform views in general.
(A video recording of what you're seeing might be useful to determine if the issue is the same or not.)

@ditman does it applies to for google_maps_flutter for mobile too?

@neoacevedo the mobile plugin shouldn't have a flickering issue (or at least, not the same flickering issue as the Web version). Are you running into this in a native Android App, or on a mobile web browser, or on a desktop web browser?

I'm running it in a native Android device. I also ran it into an emulator and I got the same results.

I'm running it in a native Android app device. I also ran it into an emulator and I got the same results.

@neoacevedo Can you please file a new issue for this? If your problem is happening in Android, you're not using the google_maps_flutter_web package at all.

Does anybody found any solution? I am also experiencing this on the mobile side too.

I'm migrating the google_maps_flutter_web package to null-safety

Is there an issue I can watch for this? I'm currently in dependency hell on a null safety migration because of that package and I'd love to know when it's updated.

@artificerchris certainly, check this PR: https://github.com/flutter/plugins/pull/3726 (still in progress, but already usable)

@ditman
That didn't work out. I modified my pubspec like so:
google_maps_flutter:
    git:
      url: https://github.com/ditman/plugins.git
      path: packages/google_maps_flutter/google_maps_flutter
  google_maps_flutter_web:
    git:
      url: https://github.com/ditman/plugins.git
      path: packages/google_maps_flutter/google_maps_flutter_web

and now I get
Error: Cannot run with sound null safety, because the following dependencies
don't support null safety:

 - package:google_maps_flutter_web
 - package:google_maps
 - package:js_wrapping

@artificerchris don't forget the ref: some-branch git option. The branch in this case is: google-maps-nnbd; so:
  google_maps_flutter_web:
    git:
      url: https://github.com/ditman/plugins.git
      ref: google-maps-nnbd
      path: packages/google_maps_flutter/google_maps_flutter_web

Also, I don't think I made any changes to google_maps_flutter; you don't need to override that one!

@ditman that did the trick! thank you! so now I just wait on the update on pub and swap back, right? I'm not super familiar with using a git version of a plugin.

@ditman that did the trick! thank you! so now I just wait on the update on pub and swap back, right? I'm not super familiar with using a git version of a plugin.

@artificerchris correct! I'd recommend that you "Subscribe" to the PR above so you get notified of when it gets merged. We normally publish plugins a couple of hours after they've been merged into flutter/plugins master. Then you can just switch to the new version in pub.dev (which IIRC is going to be: ^0.3.0)

@artificerchris you should be able to grab the null-safe google_maps_flutter_web plugin from pub now: ^0.3.0.
More info: https://pub.dev/packages/google_maps_flutter_web/versions/0.3.0

@ditman Thanks for your work!
On Wed, Mar 31, 2021 at 18:07 David Iglesias @.***>
wrote:

@artificerchris https://github.com/artificerchris you should be able to
grab the null-safe google_maps_flutter_web plugin from pub now: ^0.3.0.
More info: https://pub.dev/packages/google_maps_flutter_web/versions/0.3.0
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/75778#issuecomment-811497839,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQV5VLLJXACYGLWB5N4KDJLTGOMLNANCNFSM4XM2KJ5Q
.

I am using version:
google_maps_flutter: ^2.0.3
google_maps_flutter_web: ^0.3.0
in channel master
// This work for me:
setState(() {
      marcadores.clear();
      marcadores.add(Marker(markerId: MarkerId(latLng.toString()), position: latLng));
    });

// This not work for me:
setState(() {
      marcadores.clear();
      marcadores.add(Marker(markerId: MarkerId("positionNow"), position: latLng));
    });

animateCamera not work any case:

mapCtrl?.animateCamera(CameraUpdate.newLatLngZoom(latLng, zoom));

@d3roch4 from what I've seen in the example, you don't need to clear and add a new marker all the time, you should just update the with MarkerId that you want to move around.

animateCamera not work any case

It should at least move to the new latLng and set the desired zoom level. In web, it seems the plugin decides if it's going to animate while moving the camera or not, depending on how far the new center is from the current one, but I haven't found documentation about this.

@d3roch4 from what I've seen in the example, you don't need to clear and add a new marker all the time, you should just update the Marker with MarkerId that you want to move around.

animateCamera not work any case

It should at least move to the new latLng and set the desired zoom level. In web, it seems the plugin decides if it's going to animate while moving the camera or not, depending on how far the new center is from the current one, but I haven't found documentation about this.

Do you know any way to change marker position without clear all marker on flutter web ?

Digging deeper into this, I found this bit of the code that says:

"Preserves the position from the [currentMarker], if set."
(Source)

That is used to merge the properties of a Marker with whatever is already painted, HOWEVER, I don't really get why the position of the old marker matters (I blamed that line, and it's been there since the first iteration of the plugin, so maybe it was preventing an issue that doesn't happen anymore!).
Anyway, that seems like a bug that can be fixed. Knowing that, I now understand why Markers need to be deleted and re-created all the time. What people are achieving with that is to change the MarkerId to something that hasn't seen before by the Map widget (and that causes a repaint).
I'll try to hack around the issue above and post a quick example app in a few minutes.

Here's an example that seems to work:
It updates the position of the existing markers near the point where the map was clicked, and lets you add new markers when clicking on the Floating Action Button.
main.dart
import 'dart:math';

import 'package:flutter/material.dart';

import 'package:google_maps_flutter/google_maps_flutter.dart';
import 'package:pointer_interceptor/pointer_interceptor.dart';

final rnd = Random();

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      home: MyHomePage(title: 'Moving a Marker Google Maps Flutter Web Demo'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  MyHomePage({Key? key, required this.title}) : super(key: key);

  final String title;

  @override
  _MyHomePageState createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  // We use this value to paint new Markers close to the center of the last movement of the map.
  // Updates to this don't need to call setState, this is just a value that we care about some times.
  LatLng _center = LatLng(40.416775, -3.703790);

  // Will be updated when we tap on the map, or on the fAB.
  // Updates to this must call setState, so the GoogleMap gets re-painted.
  Map<MarkerId, Marker> _markers = {
    MarkerId('0'): Marker(markerId: MarkerId('madrid_initial'), position: LatLng(40.416775, -3.703790)),
  };

  // Will be initialized later by the [_onMapCreated] function.
  late GoogleMapController _controller;

  // This jitters a double a little bit, according to `scale`.
  // `scale` limits at which decimal point will the random function apply:
  // 0.00000001 -> tiny changes, 1.0 -> potentially large changes!
  double _jitterDouble(double val, double scale) {
    final min = val - (val * scale);
    final max = val + (val * scale);
    return rnd.nextDouble() * (max - min) + min;
  }

  // Jitters the lat/lng of a position, according to `scale`.
  LatLng _jitterPosition(LatLng position, double scale) {
    return LatLng(_jitterDouble(position.latitude, scale), _jitterDouble(position.longitude, scale));
  }

  // Creates a marker with a unique variation on a `MarkerId`, around a given `position`.
  Marker _timestampedMarker(MarkerId id, LatLng position) {
    return Marker(
      markerId: MarkerId('${id.value}_${DateTime.now().millisecondsSinceEpoch}'),
      position: _jitterPosition(position, 0.002), // Jitter so not all markers fall in the same center...
    );
  }

  void _onMapCreated(GoogleMapController controller) {
    _controller = controller;
  }

  void _onCameraMove(CameraPosition position) {
    _center = position.target;
  }

  void _onMapTap(LatLng newPosition) {
    // For each marker, move it close to the latLng of the click...
    setState(() {
      _markers.forEach((markerId, marker) {
        _markers[markerId] = _timestampedMarker(markerId, newPosition);
        // When the Marker position bug is fixed, this can be replaced by:
        // _markers[markerId] = marker.copyWith(positionParam: _jitterPosition(newPosition));
      });
    });
    // Center the camera where the user clicked after a few milliseconds...
    Future.delayed(Duration(milliseconds: 150), () {
      _controller.animateCamera(CameraUpdate.newLatLng(newPosition));
    });
  }

  // Adds a marker near the `_center` of the map.
  void _addMarker() {
    setState(() {
      // Add a new marker to the set of markers available...
      final MarkerId id = MarkerId('${_markers.length}');
      _markers[id] = _timestampedMarker(id, _center);
    });
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text(widget.title),
      ),
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            Expanded(
              child: GoogleMap(
                initialCameraPosition: CameraPosition(
                  target: _center,
                  zoom: 10,
                ),
                zoomControlsEnabled: false,
                minMaxZoomPreference: MinMaxZoomPreference(10, 10),
                markers: _markers.values.toSet(),
                onMapCreated: _onMapCreated,
                onTap: _onMapTap,
                onCameraMove: _onCameraMove,
              ),
            ),
          ],
        ),
      ),
      floatingActionButton:
        // PointerInterceptor from package:pointer_interceptor, so clicks on the fAB
        // don't hit the underlying GoogleMap widget.
        PointerInterceptor(
          child: FloatingActionButton(
            onPressed: _addMarker,
            tooltip: 'Add Marker (near center)',
            child: Icon(Icons.add_location_alt_outlined),
          ),
        ),
    );
  }
}

pubspec.yaml
name: gmaps_markers
description: A demo to demonstrate how to move a Marker with google maps web.
publish_to: none # Remove this line if you wish to publish to pub.dev

environment:
  sdk: ">=2.12.0 <3.0.0"

dependencies:
  cupertino_icons: ^1.0.2
  flutter:
    sdk: flutter
  google_maps_flutter: ^2.0.3
  google_maps_flutter_web: ^0.3.0
  pointer_interceptor: ^0.9.0 # So the fAB doesn't cause a click on the Map.

dev_dependencies:
  flutter_test:
    sdk: flutter

flutter:
  uses-material-design: true

You're the guy, thank you so much  @ditman .. It worked