training scripts

Thanks for sharing the code.
In the base2new_test.sh, shall we change
DATASET.SUBSAMPLE_CLASSES ${SUB}
to
DATASET.SUBSAMPLE_CLASSES new ?
Or an error will incur

I appreciate the authors' response. Could you please kindly direct me to where the soft prompt for the vision branch is implemented? I was able to locate the soft prompt for the text branch but couldn't find the one for the vision branch. Thank you again!


Apply patch for CVE-2022-29458

Addresses https://nvd.nist.gov/vuln/detail/CVE-2022-29458. Was cherry-picked from https://github.com/mirror/ncurses/commit/4c9f63c460cb7134f142aa65f6866c175ed77605 because the commit itself contains many changes, and we only need the patch for the CVE fix.

@katietz @tobijk @chenghlee @remkade

@katietz @tobijk @chenghlee @remkade friendly ping :)

Someone needs to check the ppc builder, then I'll merge this.

@tobijk thank you so much!

The packages should appear in a little while.

@tobijk thanks a bunch :)


Bump up Yorkie to v0.5.0

What this PR does / why we need it?
Bump up Yorkie to v0.5.0
Any background context you want to provide?
What are the relevant tickets?

Fixes #
Checklist

[x] Added relevant tests or not required
[x] Didn't break anything

Summary by CodeRabbit

New Features

Upgraded the SDK version to 0.5.0, potentially introducing new features and improvements.

Bug Fixes

Updated dependencies, including yorkie-js-sdk, to enhance functionality and resolve issues.

Chores

Incremented project version in package.json to reflect significant updates.

Thanks for your contribution.


Add University name

@codeToReality mun.txt I am sorry, I have to close the request without merging, because you made a mistake in a request and did not specify any filepath. Please ensure that you are familiar with this repository rules located at the bottom of this page and make a new correct request. Thank you for your understanding!


[formatter] formatter issue

NamedTuple(
  started: Array(Instance::Config),
  stopped: Array(Instance::Config)
).from_json(reply)

will always be format into:
NamedTuple(
  started: Array(Instance::Config),
  stopped: Array(Instance::Config)).from_json(reply)

The same issue happen on following code too.
Following code too longer for my screen
getter readers : Hash(IO::FileDescriptor, Instance) = {} of IO::FileDescriptor => Instance

I want to split it like this:
getter readers : Hash(IO::FileDescriptor, Instance) =
      {} of IO::FileDescriptor => Instance

But, it always revert to one-line version.


Add something to indicate column where the error is

I've played with your code and this is absolutely possible to do.
You have loclist variable that is updated at each linter result with locations of errors. I've copied its contents into global variable and used it like this.
fun! AddMatches()
    let g:my_positions = []
    for location in g:my_loclist
        if location.col
            call add(g:my_positions, [location.lnum, location.col])
        endif
    endfor
    call matchaddpos('ColorColumn', g:my_positions)
endf

So the idea is that you can subscribe to WinEnter event and get errors for the current buffer and then add highlight columns via matchaddpos. I've used colorcolumn here, but that's probably a bad idea. You can use some sane default and give user ability to overwrite it.

This is the same issue as #187. matchaddpos seems like the way to go. I should also probably expand the column match to whatever word the cursor lands on, with a start and end column, and make the default highlight a squiggly line.

@w0rp Sorry, I've search for word column and haven't found anything. Although I should say that I don't want entire lines to be highlighted. And not all errors, warnings should be highlighted also, so this should be customizable.


[Communication] add user-agent header for Rooms and Email service clients

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
The precondition is to put your code inside this repository and upgrade the version in the pull request but do not modify src/index.json.

Communication


Username and password are not valid for Twitter auth

twurl continues to maintain -u and -p options for username and password - this authentication method has not been available for many years, so this should be removed.

Note: we can deprecate -p option for sure but not -u option as it can be used to specify which user's secret/token from ~/.twurlrc to be used.

Great point, I completely forgot we needed it for that!


Add taproot data structures

I am still working on adding tests and testing these changes against bitcoin core. Feedback on code and API design is welcome.
Supercedes #666

Builder API to construct trees
Huffman encoding API that outputs optimal taproot tree given odds.

TODO:

[x] Add control block APIs. Verify merkle proofs, create a control block from spend data
[x] Add tests and verify them against bitcoin consensus

Sorry for the force push, addressed the feedback from @GeneFerneau and @tcharding, did not address comments from @Kixunil. I will add fixup commits from now on for easier review and later squash them when it is ready.

tACK 38a601d
Will start writing some code against this PR's API, and respond with feedback.

Rebased and squashed. No diff between 38a601d and cb00856

Addressed all your comments @dr-orlovsky

Will complete full review today

@dr-orlovsky No issues, your comments are helpful. It did help in catching an interesting caching bug that I and a few other reviewers missed! I have addressed all of your comments. Awaiting your review

tACK 89d96c0

@dr-orlovsky addressed all of your comments. I think if we get another review for this. We should just merge this and proceed with other taproot stuff. I can work on fixing up and making sure changes in #691 are reflected here.
Finally, I think about the API guidelines, I think we should have a broader discussion. My rule is to always follow the current convention in the codebase. Using  new_* and from_* over with_*. If we both(with and new) of these it would be even worse. If we want to switch to with_ (assuming we have consensus), we should do it for all APIs in a non-breaking way in a future release.

My understanding of naming:

new - obvious constructor, may be empty (String::new(), Box::new(T))
from_ - takes same information as new just in different representation (e.g. String::from_utf8(Vec<u8>))
with_ - takes additional information along with what new takes String::with_capacity(usize)

My understanding of naming:
* `new` - obvious constructor, may be empty (`String::new()`, `Box::new(T)`)
* `from_` - takes _same_ information as `new` just in different representation (e.g. `String::from_utf8(Vec<u8>)`)
* `with_` - takes _additional_ information along with what `new` takes `String::with_capacity(usize)`

I thought String was a bit of a special case but a quick look at the std lib shows its not. Perhaps conventions have changed for more recent code? I was under the impression that

Constructors with zero args should use Default
Constructors with one arg should use From<Foo> (unless the foo needs further restriction like the String;:from_utf8 case)
Constructors with multiple args should use new.
Constructors using the builder pattern should use with(self, foo: Foo)

I've never managed to work out the pattern for times when we need multiple constructors with multiple args?
Amusingly I was looking at all the instances of single arg constructors for Script yesterday wondering why they used the pattern new_.
I don't mean to bike shed here, I'm genuinely interested in these sorts of conventions.

This PR has exceeded Github's ability to reasonably display comments. I would prefer future reviews to be in the form of followup PRs.
Suggestions for non-github platforms are also welcome but that's a long term thing.

So far, I think the only things I see remaining are:

A doc-comment regarding explaining the usage of u64 for odds over probability.
The general API guidelines about the new_, with_. We basically decided to do this later and is being discussed on #692.

Anything else that I am missing? If there is nothing critical I would request to proceed on this and I can address all of the nits in a follow up PR.

@GeneFerneau @RCasatta, @dr-orlovsky, sorry for dismissing your Acks. if you are interested in taking another look.


Persistent volume claim

Can the chart be updated to use PVC to store the certs. right now every time the pod restarts it has to get certs from lets encrypt

Doing this would limit your replicas to 1.
Not sure that is the correct thing to do.

Or you use a PVC that works with ReadWriteMany.
Like EFS.

Okay. Am just concerned that while updating the arguments restarts the pod and might hit lets encrypt rate limit? How to avoid that?

If you have an PVC you maybe should convert it to a statefulset so it's not depending on having a readwritemany storage?
But is the certificates really fetched from lets encrypt? Aren't they stored in the secret created by cert-manager?

Fixed by #86


update version to 5.1

 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 contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Target fails with chr(0) in issue body

I've run into an annoying bug with target-postgres (datamill variant) where it crashes because a unicode char \x000 is sent to postgresql, causing it to reject the data.
The reason I'm reporting this here is that the data comes from this tap, and I'm not entirely sure what to do about it.
To reproduce:

run tap-github to fetch this issue: https://github.com/cockroachdb/cockroach/issues/68703 (you can get to the bug faster by hardcoding the issue number in the IssuesStream url, so as to only get this one issue)
The body of this issue contains a weird character (see screenshot from github below) which curl returns as \u0000 and python requests as \x00 (this might be the first time I write an issue report which might cause the bug to happen again :exploding_head: )

Through the various encoding/decoding, this char ends up being sent to postgresql which chokes on it, and thows psycopg2.errors.CharacterNotInRepertoire: invalid byte sequence for encoding "UTF8": 0x00

On the one hand, I feel like the target should clean the data before sending it to postgres, but the same reasoning can apply to the tap. I'm not sure what the best practice is here. The interface is JSON, and I found no evidence that \x00 is illegal in JSON, as long as it's escaped.
Any thoughts?

@laurentS - We had another encoding-based issue come up today in slack.
If we expect data to be loaded into a string field, I think it's probably healthy to coerce values to utf-8 and define some type of escaping to utf-8 string if a field may not otherwise be translated.
Alternatively, there's a JSON Schema spec for 'binary' like BASE64 encoding, but I don't think that's as generically useful vs applying utf-8 upfront. https://json-schema.org/understanding-json-schema/reference/non_json_data.html#id2
The downside I can see of coercing to utf-8 is that the validation+escaping process may be expensive computationally. It might make sense to have this as an optional config option, similar to some prior conversations around optionally validating each record against the json schema as a opt-in behavior at runtime..

In this case, I have a pretty high confidence that thee errors will be super localized and "only"happen in issue_body, issue_comment or repo_readme.
As a fix at the tap-github level, what do you think of doing something simple like this (eg. for IssuesStream):
    def post_process(self, row: dict, context: Optional[dict] = None) -> dict:
        row["type"] = "pull_request" if "pull_request" in row else "issue"
		# interesting part below:
        row["body"] = row["body"].decode('utf-8', 'ignore')
        return row

@ericboucher - Looks good from my side. If you can test on the problem row(s) and it works correctly, that looks like it would do the job. 👍

I was just doing that, but no luck: AttributeError: 'str' object has no attribute 'decode'
On the other hand row['body'] = row['body'].encode('utf-8') seems to work on the case at hand. The resulting data in postgres has the faulty character removed, but I think this is acceptable. I will let the tap run on  longer list of issues and report back if I see any other problems.

@laurentS @aaronsteers In this case, I have a pretty high confidence that these errors will be super localized and "only "happen in issue_body, issue_comment or repo_readme.

Actually, repo_readme is base64 encoded on all of the nearly 1k repos I fetched while testing, so I think that one is safe.
My impression of the cause of the error is users copy/pasting raw error logs into issues, maybe with from some source with a different encoding. So I'll guess we won't be seeing this beyond the issue bodies.


Fix two DDL bugs on hotfix branch

What problem does this PR solve?
Issue Number: close https://github.com/pingcap/tiflash/issues/5154, close https://github.com/pingcap/tiflash/issues/5859
Problem Summary:
cherry-pick two bug fixes for DDL:

For #5154

https://github.com/pingcap/tiflash/pull/5191

For #5859

https://github.com/pingcap/tiflash/pull/5932
https://github.com/pingcap/tiflash/pull/5924

What is changed and how it works?
Check List
Tests

[ ] Unit test
[x] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/cc @hongyunyan @lidezhu @flowbehappy

close as the user plan to upgrade to v5.4.3 which include these fixes

/reopen


scripts: fix push overview metrics

This PR fixes the overview metrics by providing both pull and push ways.

@rleungx  The push way of page of Overview the "TiKV" -> "leader" and "region" metrics are none data. PTAL


Fix parseURL in Internet Explorer

I added various workarounds to make the tests pass in IE11.
closes #151

Thanks!


in plugins.js > Ckeditor > config I need to have support for div container

How do I add support to add div container in source mode? its frustrating to get it deleted everytime I go away from source mode.

@tdserviceco You can cofigure "General HTML Support" plugin for that, look at https://ckeditor.com/docs/ckeditor5/latest/features/general-html-support.html
I think about include something like this in the next update https://github.com/centaur54dev/ckeditor5-custom-element

I found what i need: htmlSupport: {
allow: [
{
name: /.*/,
attributes: true,
classes: true,
styles: true
}
]
} but I cant for dear life of me understand where to put the plugin? is it plugin: {GeneralHtmlSupport} or how? and how do I import GeneralHtmlSupport from '@ckeditor/ckeditor5-html-support/src/generalhtmlsupport';? I keep getting Cannot use import statement outside a module

The plugin is already built in, all you have to do something like:
ckeditor:{
  enabled: true,
  config:{
     editor:{ // editor default config
      // ....
      htmlSupport: {
          allow: [
              // Enables plain
 elements.
              {
                  name: 'div'
              },

              // Enables plain
,
 and
 elements.
              {
                  name: /^(div|section|article)$/
              },

              // Enables
s with all inline styles (but no other attributes).
              {
                  name: 'div',
                  styles: true
              },

              // Enables
s with foo and bar classes.
              {
                  name: 'div',
                  classes: [ 'foo', 'bar' ]
              },

              // Adds support for `foo` and `bar` classes to the already supported
              //
 elements (those are enabled by the dedicated paragraph feature).
              {
                  name: 'p',
                  classes: [ 'foo', 'bar' ]
              },

              // Enables
s with foo="true" attribute and bar attribute that
              // can accept any value (boolean `true` value works as an asterisk).
              {
                  name: 'div',
                  attributes: {
                      foo: 'true',
                      bar: true
                  }
              },

              // Adds support for style="color: *" to the already supported
              //
 and
 elements.
              {
                  name: `/^(p|h[2-4])$/'`,
                  styles: { 'color': true }
              },
          ]
      }
    }
  }
}

and be careful with that:
htmlSupport: {
    allow: [
        {
            name: /.*/,
            attributes: true,
            classes: true,
            styles: true
        }
    ]
}

because it may not work

Ah thanks will play around with this :) thanks

hmmm doesnt seem to work with only htmlSupport: {
allow: [
// Enables plain ,  and  elements.
{
name: 'div',
}
]
} can you try to see if you get a div back?

I have tested it and it works, try to copy all from my comment above, also you can add:
heading: {
      options: [
              {
              model: 'div3',
              view: {name: 'div', classes: 'ck-heading_h3_b'}, title: 'div (border)', class: 'ck-heading_heading3', converterPriority: 'high'
              }
       ]
}

Im so sorry, I got it to work now.. you're right.. I needed to copy the entire thing you send me.. now I can do my DIV with class and give it a name :)
Thanks for your patient.. I sometime cant understand these setup.


Typo in AdaptationSet@initializationPrincipal in switching set MPD

Seen in http://dash.akamaized.net/WAVE/vectors/cfhd_sets/15_30_60/ss1/2022-10-17/avc_15_30_60_ss1_stream_v4.mpd
AdaptationSet@initializationPrincipale instead of AdaptationSet@initializationPrincipal without the last 'e'.

Cf https://github.com/cta-wave/Test-Content-Generation/search?q=initializationPrinciple for places to modify.


Fully support gravity changes

Right now there is a very basic gravity change support.
Not supported

slopes
right/left gravity
jumping

It just now what is above/below and raycast propely. My usage is to patrol ceilings, I don't plan to expand it more...

This must be done using a matrix4x4, and translate Vector2.Up to a method that return Up * matrix.


Image is not displayed on View but stored in firebase storage

solution: https://github.com/yoha/Ventori/commit/9d4e0d65ad24721d3ba93168ca848e6420e5329d


remove react-query passed as component properties

In the credential components, the queries are passed as component properties. This must be removed.
https://github.com/eclipse-xpanse/xpanse-ui/blob/main/src/components/content/credential/AddCredential.tsx#L31

[ ] Move all shared queries as custom query hooks and then directly used it in components.
[ ] To be checked and fixed in all credential related components.

let me do it


Add support for Sentry

Add raven and its dependencies as requirements, add a placeholder for
SENTRY_DSN, and initialize the plugin on the Flask application. If
no DSN is provided, the plugin remains registered but does not attempt
to contact a remote Sentry server.
Fixes #110.

@jonafato Since the scrape/index tasks aren't run through Flask, this won't catch errors in those right?

@captbaritone Good point. My change will only enable Sentry for the Flask app. I'll work on adding it to the outside-of-Flask functions next.

👍


Command methods: picking from interfaces in addition to superclasses.

Very specific use case, perhaps:

lots of top level sub-commands
implemented as command methods.
not wanting to put all of them in one java file.

Right now, the only way is chain of inheritance, and give root
of chain to CommandLine.
Another way is to create default methods in interfaces, and make
top Command implement all these interfaces.
I tried simple change, will this work ?
--- a/src/main/java/picocli/CommandLine.java
+++ b/src/main/java/picocli/CommandLine.java
@@ -11828,6 +11828,9 @@ public class CommandLine {
                     Stack<Class<?>> hierarchy = new Stack<Class<?>>();
                     while (cls != null) {
                         hierarchy.add(cls);
+                        for ( Class<?> c : cls.getInterfaces()) {
+                            hierarchy.add(c);
+                        }
                         cls = cls.getSuperclass();
                     }
                     Set<Class<?>> fullHierarchySet = new HashSet<Class<?>>(hierarchy);

Hi @vrdhn, my time to work on picocli is extremely limited these days. Mostly just bugfixes.
However, I can discuss ideas for enhancements and review pull requests.
I suggest that you clone the picocli repository, and experiment until it becomes clear which changes are necessary to fulfil your use case. When you are ready, you can raise a pull request to include those changes into the picocli library. A good pull request passes all existing tests (we cannot break any existing applications), and also should add a test for your use case - a test that fails with the current version of picocli and passes with your changes. Of course, make sure that you are happy with your solution, so that it solves your issue completely.
Note that this may be quite a lot of work. If you already have a workaround, I am not sure if it is worth your time working on a pull request for also supporting interfaces.

One more thing: we cannot use default methods on interfaces, since picocli requires only Java 5 (see reasons why), and default methods were introduced in java 8.


Amend image sizing issue in final export

See other conversation :)
Image resizing was done with InkScape and saved as 'optimised svg', file size is a little smaller.
I've tidied up some CSS too so leaderline colors match their label.

Thank you!


 The
following options are not yet implemented:

Explanation support (although, detailed info is logged using debug)
Detailed deep merge options

Also, the following options were left out because they make no sense
unless lookup is tightly integrated with Puppet:

Ability to select a 'node'
Ability to choose 'environment'
Option to fully compile a catalog

Closes #10

@thallgren It's a linter thing:
6.53s$ GO111MODULE=on golangci-lint run
lookup/lookup.go:49:5: `options` is unused (deadcode)
var options = map[string]px.Value{`path`: types.WrapString(`./testdata/sample_data.yaml`)}
    ^
The command "GO111MODULE=on golangci-lint run" exited with 1.


SW-5710 Added add boundary modal, and upload shapefile flow

#2923  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @tommylau523 and the rest of your teammates on  Graphite


Home page

-When a user is not logged in, when trying to access the website he/she will be redirected to the login page.

After the user is logged in he/she will be redirected to the schedule page.

#19


Option to allow the player to move during emotes.

Hello, I would like to ask for a feature to let the player move during an emote animation.
Im working on letting the player jump over ledges or to a button command.
I set the player emote to ! and i change the graphic to that player, then I change the player sprite to a shadow.
It looks great as you can see in the .gif
The problem is you cant move the character at anytime during the emote.
I would like to have this feature as an option, so that you can choose to stop the player or to not stop the player during an emote.

From Rulz on Discord he solved my problem, just put the emote to happen on the  "On Update" Trigger.


Map-style UDFs for Python API

This PR adds a first attempt at map-style User-Defined Functions (UDFs) to the Python API. These functions take a table as input and return a table of possibly different shape. UDFs are passed as functions that take a single Pandas DataFrame as argument and return a DataFrame as a result again.
It's important to note that these functions are executed on subsets of the data in a streaming fashion. For now these UDFs are implemented as part of our relational API, meaning they cannot be used within SQL queries (yet).
We determine the result schema of UDFs by calling them once with a zero-length data frame as input. The functions are expected to adhere to this schema in subsequent calls with actual data.
In the simplest case, the function does not do anything:
def nop(df):
    return df

duckdb.values([42]).map(nop)

of course you can also specify a lambda:
duckdb.values([42]).map(lambda df: df)

Some more meaningful use, for example extracting the domain name from an email address:
import duckdb
import pandas

df =<EMAIL_ADDRESS><EMAIL_ADDRESS>columns=['email'])

def get_domain(df):
	df['domain'] = df['email'].apply(lambda x : x.split('@')[1]).to_frame()
	return df

rel = duckdb.from_df(df).map(get_domain)
print(rel.to_df())

Of course this also works directly on tables, Parquet files, CSV files, you name it.
In the future, we will also allow parallelisation of those functions, but for now they share a GIL.

CC @dmitrykoval


Footer UI updation ,new feature Newsletter

Describe the feature
The previous one footer's rightmost part not looks good ,the icons are very much smaller .
Newsletter feature has been added in this newone.
Attaching the before after image .
Plz assign me this and label this gssoc level1
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

hlo @huamanraj plz check this updation and assign it to me

Assigned! @siddhanttomar2003
Make sure to attach before & after screenshots in your PR and include the issue number.
Also, please star the repo before working on it. Happy open-source contributing!


chore: Fix mypy check in #2070

:books: Documentation preview :books:: https://meltano-sdk--1.org.readthedocs.build/en/1/

cc @BuzzCutNorman


Better CI/CD

3 days in a raw merges breaks the code base
can we have something just to check that zenbot can be just started Ok ?

plz check the issue with latest pull
https://github.com/DeviaVir/zenbot/commit/607a72cdf7347f0f45c8924b88e410114378c203#r27555936
@DeviaVir @krystophv


Development: Backend Refactor

Description
Please test:

Requests
Admin (All of it)
Signup
Login
Should see following list and friends list
Should see public posts + following posts
Settings
Profile
FriendsFeed
Public

Type of change

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

How Has This Been Tested?
Will be.
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

Bugs:

When going to a user page with no post the backend crashes (@post.js line 431,  TypeError: Cannot read properties of undefined (reading 'posts_array')
When accepting a request, the backend crashes from deleting the request (@request.js line156, TypeError: res.json is not a function) Note: Unless someone was also running the app at the same time I was testing, It seems that it also deleted the wrong request, before there was a request from kc to someone else, now it is gone.  Upon further testing, it deletes the first request in the collection rather than the right one.
When signing up for a new account, using a "." in the username causes a 400 bad request
Editing a post removes the description with no way to add it back
When in friends post a copy of a username flashes on and off the screen in the left nav bar
There are a few minor cosmetic flaws, such as the following list on the right the same username appears 3 times,  alignment issues

Bugs:

When going to a user page with no post the backend crashes (@post.js line 431,  TypeError: Cannot read properties of undefined (reading 'posts_array') DONE
When accepting a request, the backend crashes from deleting the request (@request.js line156, TypeError: res.json is not a function) Note: Unless someone was also running the app at the same time I was testing, It seems that it also deleted the wrong request, before there was a request from kc to someone else, now it is gone.  Upon further testing, it deletes the first request in the collection rather than the right one. DONE
When signing up for a new account, using a "." in the username causes a 400 bad request NOT A BIG ISSUE RIGHT NOW
Editing a post removes the description with no way to add it back THIS IS BECAUSE DATABASE NEEDS TO BE UPDATED ... AGAIN
When in friends post,  a copy of a username flashes on and off the screen in the left nav bar DONE
There are a few minor cosmetic flaws, such as the following list on the right the same username appears 3 times,  alignment issues NOT MY PROBLEM


Codepush with encrypted private key fails with "The specified signing key file was not valid"

Hi!
I try to run codepush with an encrypted private key like this:
appcenter codepush release -c ./CodePush/ -t 1.0.4 -d Production -k private.pem
Expected behavior: Prompt for the private key keyphrase
However - running this command leads to:
Generated a release signature and wrote it to CodePush/.codepushrelease
Error: Command 'codepush release -c ./CodePush/ -t 1.0.4 -d Production -k eprivate.pem' failed with exception "The specified signing key file was not valid"
error Command failed with exit code 3.

Closing as stale.


Add new adopter

What this PR does / why we need it:
Canary Inc. as an adopter
Which issue(s) this PR fixes:
N/A
Does this PR introduce a user-facing change?:

How are users affected by this change: Not sure.
Is this breaking change: Not sure.
How to migrate (if breaking change): Not sure.

We are using PipeCD because of its ease of development.

Thank you so much for adopting!!!
Would you please signoff and pass the DCO check? (roughly saying, you need git commit -s)
cf. https://github.com/pipe-cd/pipecd/pull/4897/checks?check_run_id=24186548268

Thanks, I fixed  🙏
403c7eb


iroh-bytes: Show connection status in doctor accept / connect GUI

Description
Gives some info about the connection status in the accept and connect gui:
Accepted connection from cxzdmvkbdiktcg24ojqrl7gydm6jzg2l6jo4v77d25gkio6czraa
derp region: 2, latency: 0.000432s, connection type: direct, addrs: [<IP_ADDRESS>:51103 (unknown); <IP_ADDRESS>:51103 (0.000432s)]
send: 67.27 MiB/s
recv: 66.22 MiB/s
echo: 39.64 MiB/s
⠄ [█████████████████████████████▎                                                  ] send 5.84 MiB/16.00 MiB (81.29 MiB/s)

Notes & open questions
Change checklist

[x] Self-review.
[ ] Documentation updates if relevant.
[ ] Tests if relevant.

Just tried this out.  It's very cool to watch your connection start out in relay mode and then switch to a direct connection to faster speeds


App crash when we startPreview()

java.lang.RuntimeException: Fail to connect to camera service
at android.hardware.Camera.(Camera.java:519)
at android.hardware.Camera.open(Camera.java:365)
at com.gpfreetech.awesomescanner.ui.GpCodeScanner$InitializationThread.initialize(GpCodeScanner.java:822)
at com.gpfreetech.awesomescanner.ui.GpCodeScanner$InitializationThread.run(GpCodeScanner.java:799)

I'm having the same issue on android 8.1

ya i also facing same


[Bug] workflow syntax error

Describe the bug, including details regarding any error messages, version, and platform.

Component(s)
Continuous Integration

this bug is a syntex error caused by indentation， can be fix by https://github.com/apache/incubator-graphar/pull/645

this bug is a syntax error caused by indentation， can be fixed by #645

fixed


Test for header instead of length

Will close #6
brotli and deflate which have no deterministic header is a bit weird w/ this but maybe less weird than testing for exact compressed lengths? Opinions @musicinmybrain?

Indeed, it seems there is still some potential for the brotli and deflate tests to be brittle, since as I understand it those are both producing a raw compressed stream without any framing format (e.g. .br/.gz).
This could be an improvement, but it’s perhaps worth reflecting on what kind of issues the test is intended to catch. This version would catch a failure to apply any compression at all when it was requested, or would catch a typo that caused the wrong compressor to be used – but so, I expect, would the attempt to decompress the compressed stream with the expected decompressor. I wonder if examining the headers is providing any additional value or not.


Error: Exception during execution of external process

Hello MaxQuant Team,
I am trying to run a batch of experiment on cluster with 15 raw files and 6 fasta files as database. I am getting an error:
Exception during execution of external process
followed by Fatal error messages.
When I tried to execute the same 15 samples with 2 fasta files it finished without any error or issue. May I know what may be causing this issue?
Any clue will be of great help.
Thanks
Devender Arora

Hi Devender,
I'm not part of the MaxQuant team - just made this guide to help others. The official help forum is on Google Groups here: https://groups.google.com/g/maxquant-list


Maurice: asynchronous programming, chapter 1

Study Plan

Learning Objectives

[x] 🥚 You understand the JavaScript Event Loop, and can demonstrate this by using setTimeout and setInterval to schedule simple tasks.
[x] 🥚 You can explain why Asynchronous Programming is important for programs that have blocking and non-blocking tasks.
[ ] 🥚 You can explain the basics of the Client/Server model and HTTP requests and can fetch data from RESTful APIs.
[ ] 🥚 You can convert built-in Node modules from consuming callbacks being promises.
[ ] 🐣 You can write and run JavaScript for Node.js or for the Browser. Both environments run JavaScript but they have some important differences!

[ ] use cases: You can explain some use cases that are unique to each runtime.
[ ] built-in APIs: You can list some of the key APIs available in each environment, and why they are not available in the other.
[ ] module systems: You can explain the difference between CommonJS Modules in Node.js and ES Modules in the Browser. You can write and use programs written with either system.

[ ] 🐣 You can break down an asynchronous problem into smaller tasks and solve it using promises. This includes identify which tasks depend on each other and which are independent:

[ ] dependent tasks: The return value from one task is required to start the next task, these must be completed in a specific order - .then
[ ] independent tasks: These tasks do not use each other's return values, they can be completed at the same time - Promise.all

[ ] 🐣 You can trace, refactor and write code that accesses the file system between these 3 different syntaxes:

[ ] Callbacks

[ ] Promises

[ ] async/await

[ ] 🐣 You can step through a Node.js command line application using the VSCode debugger.
[ ] You can write small programs with a Data Access layer that asynchronously uses data stored in different locations:

[ ] 🐣 Browser: You can write a small web page that fetches data from a RESTful API and renders it into the DOM.
[ ] 🐥 Node: You can write a small CLI program that reads user input from process.argv and reads/writes the file system.

Week 21
Practice repo
Check-In
I Need Help With:

What went well?
Watching tutorials.
What went less well?
Lessons Learned
New concepts and the role that JS plays in programming.
Sunday Prep Work
Reading the material and practising.


Add neon.primary_is_running GUC.

We set it for neon replica, if primary is running
Corresponding cloud PR is https://github.com/neondatabase/cloud/pull/10183

For the sake of the archives, please explain the problem in the commit message too. And perhaps open a github issue to track it. IIUC the problem is that:

No primary is running on a branch
You start a new read-only replica on the branch
The read-only replica doesn't allow connections, because it doesn't have a valid standby snapshot yet. It doesn't know which transactions that have not committed yet might still be running in the primary and commit later. There is no primary, so the answer is "none", but Postgres doesn't know that.

A hot standby will wait for RUNNING_XACTS or shutdown checkpoint records until it can allow connections. If the primary is not running, they will never come.
This PR adds a GUC to tell the standby that there is no primary running. It doesn't actually do anything with it. Will that be a followup PR?
Even with this flag, this can still happen:

There is a primary running
You start a read-only replica
Primary crashes / is killed before it writes a RUNNING_XACTS record.

So just checking that a primary is running when the standby starts isn't necessarily enough.
A GUC doesn't feel like a very good mechanism to deliver this information. Whether a primary is running or not is very ephemeral. Perhaps the neon extension should ask the control plane for that directly with an API call?

For the sake of the archives, please explain the problem in the commit message too. And perhaps open a github issue to track it. IIUC the problem is that:

No primary is running on a branch
You start a new read-only replica on the branch
The read-only replica doesn't allow connections, because it doesn't have a valid standby snapshot yet. It doesn't know which transactions that have not committed yet might still be running in the primary and commit later. There is no primary, so the answer is "none", but Postgres doesn't know that.

A hot standby will wait for RUNNING_XACTS or shutdown checkpoint records until it can allow connections. If the primary is not running, they will never come.
This PR adds a GUC to tell the standby that there is no primary running. It doesn't actually do anything with it. Will that be a followup PR?

Hot-standby replica  is waiting for primary only if was not started after normal shutdown (wasShutdown true in xlogrecovery.c). This behaviour was changed only by my PR #6357. And I am also going to handle added GUC in this PR.

Even with this flag, this can still happen:

There is a primary running
You start a read-only replica
Primary crashes / is killed before it writes a RUNNING_XACTS record.

Primary has to be restarted in any case.
We do not support replacement of primary with replica.
So Neon should detect crash of primary node and restart it.
Replica will reconnect to new primary and receive  RUNNING_XACTS record.
Actually replica has no other choice rather than wait for primary once it starts recovery - receiving WAL from primary.
AS a result it can receive tuples which can contain XIDs of running transactions. This transactions can be committed before primary crash. So replica may not set XMIN_INVSLID hint but for such tuples.

So just checking that a primary is running when the standby starts isn't necessarily enough.

I do not know better solution.

A GUC doesn't feel like a very good mechanism to deliver this information. Whether a primary is running or not is very ephemeral. Perhaps the neon extension should ask the control plane for that directly with an API call?

The code making decision whether to set wasInterrupted to not was not in extension, but in Postgres core (xlogrecovery.c)
Certainly it is possible to add one more hook here. But we have to change Postgres sources in any case.
I do not understand why sending request to control plane is better than sending this information through compute spec and then GUC. Also extra round-trip doesn't speedup startup.

Even with this flag, this can still happen:
There is a primary running
You start a read-only replica
Primary crashes / is killed before it writes a RUNNING_XACTS record.
Primary has to be restarted in any case.

We do not support replacement of primary with replica.
So Neon should detect crash of primary node and restart it.
Replica will reconnect to new primary and receive RUNNING_XACTS record.

Hmm, looks like we can get into a deadlock here. Imagine this situation:

primary is running
replica is starting and waiting for running_xacts from primary
primary is crashing
StartCompute(replica) operation is still in progress, and control-plane cannot run concurrent operation of StartCompute(primary), so it will wait in a queue.
Eventually, this situation will resolve, when replica startCompute deadline exceeds.

Are we OK with this?
I'd say yes, because crashing primary is not normal and should be fixed asap anyway.
@hlinnaka, @knizhnik, WDYT?

Even with this flag, this can still happen:
There is a primary running
You start a read-only replica
Primary crashes / is killed before it writes a RUNNING_XACTS record.
Primary has to be restarted in any case.

We do not support replacement of primary with replica.
So Neon should detect crash of primary node and restart it.
Replica will reconnect to new primary and receive RUNNING_XACTS record.

Hmm, looks like we can get into a deadlock here. Imagine this situation:
* primary is running

* replica is starting and waiting for running_xacts from primary

* primary is crashing

* StartCompute(replica) operation is still in progress, and control-plane cannot run concurrent operation of StartCompute(primary), so it will wait in a queue.

* Eventually, this situation will resolve, when replica startCompute deadline exceeds.

Are we OK with this? I'd say yes, because crashing primary is not normal and should be fixed asap anyway. @hlinnaka, @knizhnik, WDYT?

Until https://github.com/neondatabase/neon/pull/6712 is merged, we don't actually write the shutdown checkpoint record even on a clean shutdown, so you'll get the above with a clean shutdown too.

This PR adds a GUC to tell the standby that there is no primary running. It doesn't actually do anything with it. Will that be a followup PR?

Hot-standby replica is waiting for primary only if was not started after normal shutdown (wasShutdown true in xlogrecovery.c). This behaviour was changed only by my PR #6357. And I am also going to handle added GUC in this PR.

I see. Can you include those changes here, please, so that this can be reviewed, tested and committed as one unit, please?
Needs tests.

So we currently have this bug:

Primary is running
Start a transaction in primary. Insert a row.
Start a replica. Because we always set 'wasShutdown==true' in xlogrecovery.c, the replica considers all in-progress transactions as aborted.
On replica. BEGIN REPEATABLE READ; and run a query on replica. The new row inserted in primary is not visible.
Commit the transaction on primary
On replica: run another query in the same transaction. Incorrectly, the new row is now visible.

Please create a python test case for that. This PR should then fix it.

There is such test  test_runner/regress/test_replication_start.py in PR #6357:
https://github.com/neondatabase/neon/pull/6357/files#diff-7edc60d2be535ca5bbd3cce1b149594fd1994e755bd3b1f362a7e010a5cd3b16

This PR adds a GUC to tell the standby that there is no primary running. It doesn't actually do anything with it. Will that be a followup PR?

Hot-standby replica is waiting for primary only if was not started after normal shutdown (wasShutdown true in xlogrecovery.c). This behaviour was changed only by my PR #6357. And I am also going to handle added GUC in this PR.

I see. Can you include those changes here, please, so that this can be reviewed, tested and committed as one unit, please?
Needs tests.

I can shuffle changes between PR as you prefer.
But actually this problem and its fix has no relation to this PR.
So, what we have no: replica is started with wasShutdown=true doesn't receive information about running xacts, construct incorrect snapshot and as a result see incorrect data.
The problem was fixed in #6357 - now hot-standby replica waits for WAL from primary.
It cause problem with e2e tests (which spawns read-only replica on branch without spawning master). But certainly it is not only related to e2e. So Star has proposed this mechanism with informing replica by control place whether primary is running (wasShutdown=false) or not (wasShutdown=true).
So #6357 solves the problem with spawning replica with alive master. And this PR (in conjunction with correspondent PR for control plane) solves the problem with spawning replica without alive master.
Please notice that

To make this POR work we need first merge it's control plane part
Regression tests are not using control plane. So to test it we do not need this PR. It is possible to propagate this flag through neon_local. But I am not sure that it makes sense.

I can shuffle changes between PR as you prefer.

Thank you. The general rule should be: one bug, one PR. PR includes all code changes required to fix the bug, and a test to reproduce it, but nothing else.

But actually this problem and its fix has no relation to this PR. So, what we have no: replica is started with wasShutdown=true doesn't receive information about running xacts, construct incorrect snapshot and as a result see incorrect data.

The point of this PR is to fix that bug, right?

The problem was fixed in #6357 - now hot-standby replica waits for WAL from primary.

According to the description of #6357, it is about propagating apply_lsn from safekeepers to pageservers, to postpone GC. That seems completely unrelated to this.

It cause problem with e2e tests (which spawns read-only replica on branch without spawning master). But certainly it is not only related to e2e. So Star has proposed this mechanism with informing replica by control place whether primary is running (wasShutdown=false) or not (wasShutdown=true).
So #6357 solves the problem with spawning replica with alive master. And this PR (in conjunction with correspondent PR for control plane) solves the problem with spawning replica without alive master. Please notice that
1. To make this POR work we need first merge it's control plane part

Gotcha.

2. Regression tests are not using control plane. So to test it we do not need this PR. It is possible to propagate this flag through `neon_local`. But I am not sure that it makes sense.

Yes, it does. We need regression tests for these things. If we go with a GUC, it's easy to set the GUC in a test to simulate how the control plane would set it.
To summarize, for this PR:

Let's agree that the point of this PR is to fix the bug that a replica constructs incorrect snapshots, which leads to incorrect query results, if the primary is running.
Please include all the code changes needed to fix that bug, but nothing else.
Please include a regression test case that demonstrates the bug. Without the code changes from PR, the test fails, and with the changes, it passes.

I can shuffle changes between PR as you prefer.

Thank you. The general rule should be: one bug, one PR. PR includes all code changes required to fix the bug, and a test to reproduce it, but nothing else.

But actually this problem and its fix has no relation to this PR. So, what we have no: replica is started with wasShutdown=true doesn't receive information about running xacts, construct incorrect snapshot and as a result see incorrect data.

The point of this PR is to fix that bug, right?

The problem was fixed in #6357 - now hot-standby replica waits for WAL from primary.

According to the description of #6357, it is about propagating apply_lsn from safekeepers to pageservers, to postpone GC. That seems completely unrelated to this.

It cause problem with e2e tests (which spawns read-only replica on branch without spawning master). But certainly it is not only related to e2e. So Star has proposed this mechanism with informing replica by control place whether primary is running (wasShutdown=false) or not (wasShutdown=true).
So #6357 solves the problem with spawning replica with alive master. And this PR (in conjunction with correspondent PR for control plane) solves the problem with spawning replica without alive master. Please notice that

To make this POR work we need first merge it's control plane part

Gotcha.

Regression tests are not using control plane. So to test it we do not need this PR. It is possible to propagate this flag through neon_local. But I am not sure that it makes sense.

Yes, it does. We need regression tests for these things. If we go with a GUC, it's easy to set the GUC in a test to simulate how the control plane would set it.
To summarize, for this PR:

Let's agree that the point of this PR is to fix the bug that a replica constructs incorrect snapshots, which leads to incorrect query results, if the primary is running.
Please include all the code changes needed to fix that bug, but nothing else.
Please include a regression test case that demonstrates the bug. Without the code changes from PR, the test fails, and with the changes, it passes.

Done

ref https://github.com/neondatabase/neon/issues/7204


Pipchecker compatibility

Resolves #1521
On pip 20.1, parse_requirements() returns ParsedRequirement object. So I updated a code to make InstallRequirement object from it.

Coverage decreased (-70.2%) to 0.0% when pulling 72380feb465dd25d486a8706d84b9223c219a326 on yeojin-dev:pipchecker-compatibility into 2975bf591822def88e916db3c47820c5dbacae59 on django-extensions:master.

Thanks !


feat: implement MacosDisclosureButton

Pre-launch Checklist

[x] I have run dartfmt on all changed files
[x] I have incremented the package version as appropriate and updated CHANGELOG.md with my changes
[ ] I have added/updated relevant documentation
[x] I have run "optimize/organize imports" on all changed files
[x] I have addressed all analyzer warnings as best I could

Hi @Umar1312, thanks for opening this PR!
Please address the failing check, and then I can review.

Hi @Umar1312, thanks for opening this PR!
Please address the failing check, and then I can review.

Addressed. Please check.
Thanks!

@Umar1312 The Flutter analysis check is still failing, looks like your test file.

Also, if you could please upload a gif of the widget in action, I'd really appreciate it. I don't generally have the time to pull PR branches and manually run the example to test the new code, so gifs are essential to my reviews.

Addressed. Also PFA the gif of widget in action.
Thanks!

@GroovinChip Thanks for reviewing. I'm not quite sure on what changes I should make for this.

Going through the Apple's Docs, what we are trying to to implement is NSBezelStyleRoundedDisclosure. The actual  implementation of the hide/show part should be the responsibility of the user as is the case for Apple's own implementation.

If you still want to incorporate the show/hide functionality then we should probably not view it as a button widget, as it's scope has now changed considerably.

Let me know what you think about this.

@Umar1312 I'll think about this and get back to you, thanks.

OK @Umar1312 we can keep things as they are. I'll review now.

@GroovinChip Thanks, updated.

@Umar1312 I actually just overhauled MacosScrollBar which allows the return of the ScrollController to ContentArea. If you want I can land that first, or you can open a new PR afterwards. What would you like to do?

@GroovinChip Updated.


PHOENIX-6721 CSV bulkload tool fails with FileNotFoundException if --…

…output points to the S3 location
This is @ss77892 's patch, rebased, and using getWorkPath() instead of getOutputPath()

FYI @steveloughran
Is this version correct ?
I have tested this with both HDFS and S3 outputdir.

It looks good to me. I don't quite remember why I didn't use getWorkPath in the first place, but if it works as expected, then I have no objections. Thank you so much, Istvan!

Merged manually.

I don't quite remember why I didn't use getWorkPath in the first place,

@ss77892 we only pulled it up from a FileOutputFormat into an interface with the s3a committer work


ref_model for training PEFT model with DPO

In the current version of the DPO trainer, it appears that the ref_model needs to be set as None when utilizing a PEFT model (a peft_config is passed during trainer initialization), and the PEFT model with adapters disabled will be used as the ref_model by default. In our experiments, the ref_model is a different model from the base model, so we cannot directly use the current implementation. I am wondering whether it would be possible to allow the option of passing in a ref_model for training PEFT model with DPO, or could you please suggest any workarounds for our experiments using the current DPO?
Your guidance and help would be greatly appreciated. Thank you very much!

hi @rachellxy
This makes sense, I just made https://github.com/huggingface/trl/pull/1367 which should fix this issue, you would have to pass force_use_ref_model in the DPOTrainer's init method


The question about the Jacobian derivation in IESKF::update()?

Hi, thanks for sharing the work! I was checking the code and  found some difference compared to ig-lio, especially in convariance update and constructing IMU prior constraint. For example, when constructing IMU prior constraint,  the jacobian about current state in ig-lio is

while in your code is

and I checked the details in the paper  and other paper:

and the problem also appear in convariance update, in ig-lio:

while in  in your code :

if the LIO is ok, I think the jacobian maybe is approximately identity matrix.

yes, most of time, right_jacobian is approximately identity matrix

Hi, the convariance update is aslo different. I checked the formulation in ig-lio and I found that  is similar to -Jl_inv:

about this question, do you have any ideas?

i think the author missed a transpose(),  P_ = L.transpose() * temp * L

yes, in the ig-lio code, the author missed a transpose for L, and the computation of matrix L confused me, which is a derivation of state?

用中文吧，整个过程是我是清楚，就是在计算L矩阵时，我看需要计算雅克比矩阵，如下图所示

而在你的代码中，这部分也在计算雅克比矩阵

ig-lio中L的计算，这个雅克比应该是-Jl_inv，这个雅克比矩阵应该是更新之前的位姿

最后一步是误差卡尔曼的修正过程，在《Quaternion kinematics for the error-state KF》 第64页的6.3节ESKF reset有直接的结论, IG LIO 的作者应该是用了这里的结论，但是这个雅可比其实误差状态对更新前误差的导数(文字描述还是有歧义，你直接看论文中的公式，或许会更好理解)

好的，谢谢！


Feature: Allow multiple frontends to be defined using docker labels in swarm mode

Do you want to request a feature or report a bug?
Request a feature

What did you do?

I was planning to have multiple frontends for a single swarm service with different settings (hostname, IP whitelist, etc)
What did you expect to see?
I expected to be able to define multiple frontends as it is possible to do so manually when using a config file
What did you see instead?
According to the docs, only 1 frontend can be defined per docker service (unless it listens on multiple ports)
Output of traefik version: (What version of Traefik are you using?)

Version:      v1.6.0-rc6
Codename:     tetedemoine
Go version:   go1.10.1
Built:        2018-04-17_11:59:31AM
OS/Arch:      linux/amd64 ```

Hello @ajardan .
Many thanks for your interest in the project.
The feature you described seems to already exists : it's the segment labels.
You can find more information about it in the documentation.
I close the issue, but feel free to reopenit if necessary or join our Slack workspace for more community #support.


Support  --no fix when linting with typescript plugin

Thank you for this :)

Close #1112

Somehow a PWA test failed on AppVeyor even though I didn't make any changes in that plugin? The tests also appear to be passing locally


Globalize circular dependency errors

I have decided to use globalize with ReactNative and faced the same errors as in https://github.com/joshswan/react-native-globalize/issues/3. In cldrjs it was fixed in https://github.com/rxaviers/cldrjs/issues/53. As far as I have understood a problem in cyclic dependences. The author of react-native-globalize has solved it in his fork globalize.

Thanks for filing this issue. It's worth mentioning it's not a problem for node or npm, but it seems to be a problem for some bundlers. The change is quick, let's make it in here as well. Feel free to submit a PR. Thanks.

Remains a riddle why Facebook developers have written own bundler without any configurability. Perhaps to make us stronger). And i'm not the first time faced with this and assume that it happens in those who do not use babel.


Added Mailjet Messaging adapter

What does this PR do?
Adds the Mailjet Messaging Adapter
Test Plan
In your env, add MAILJET_API_KEY, MAILJET_API_SECRET, TEST_EMAIL, TEST_FROM_EMAIL
Related PRs and Issues
https://github.com/appwrite/appwrite/issues/6389?notification_referrer_id=NT_kwDOBOKhvrM3OTAzNTI4MDExOjgxOTYxNDA2
Have you read the Contributing Guidelines on issues?
yes

Hey,
Due to time constraints, I'm going to mark this PR hacktoberfest-accepted for now so you get DO's Hacktoberfest rewards. We'll continue to work with you on this issue for review and merge.
When it is merged, we'll contact you for Appwrite-specific Hacktoberfest swag.
Thanks for helping us improve Appwrite!

Hey there! There were a lot of big PRs during this Hacktoberfest, and we wanted to give everyone ample time to collaborate with our engineering team. If you were able to merge your PRs during October, amazing. If it’s still not merged, don’t worry about it either. Either way, we’ve got your Hacktoberfest swag minted and ready to ship.
Please comment with your Discord username here so we can contact you about your shipping information to deliver your Hacktoberfest swag.

Please comment with your Discord username here so we can contact you about your shipping information to deliver your Hacktoberfest swag.

@gewenyu99 its @Chandram

Gonna try to reach out soon after we get forms ready for everyone. Appreciate your patience.


Use electron.clipboard for all clipboard uses

Signed-off-by: Sebastian Malton<EMAIL_ADDRESS>fixes #4529

tested on linux

Issue described a solution using browser API but this PR is using Electron api, any reason for this?

Issue described a solution using browser API but this PR is using Electron api, any reason for this?

I did this for two reasons:

The browser API requires being in a secure context (HTTPS) according to MDN
The electron api was easy to use.

Issue described a solution using browser API but this PR is using Electron api, any reason for this?

I did this for two reasons:

The browser API requires being in a secure context (HTTPS) according to MDN
The electron api was easy to use.

We use the electron clipboard API already in a few places so I think good to use it here too.


Tiny typo in document

Describe what scenario you think is uncovered by the existing examples/articles
Describe why existing examples/articles do not cover this case
Additional context
Add any other context or screenshots about the documentation request here.
 data: (value) => Text('Hello ${user.name}'), // incorrect
 data: (value) => Text('Hello ${value.name}'), // correct

https://pub.dev/documentation/riverpod/latest/riverpod/AsyncValue-class.html

This is fixed on master. I guess the doc fix wasn't deployed


BioT5X for NLI

Hi! Very interesting work!
Could you also provide a script for finetuning an NLI task with BIOT5X and describe the data format of MedNLI required for BiOT5X and how it should be exactly preprocessed?
Thanks!

@mstrise , thanks for interesting in our work.
You can processed the NLI data as:
input: sent1:{sent1} sent2:{sent2}

There are examples here from another project


Enhancement: Make the value argument of the functional QueryField objects to System.Object.

Describe the enhancement
To avoid the limitations on the value of the functional QueryField objects (i.e.: LeftQueryField, RightQueryField, TrimQueryField, etc), it is best to have it as object instead of targeted types.
In the current version, as a sample, the LeftQueryField is accepting a string.
var where = new LeftQueryField("FieldName", "VAL");
var result = connection.Query<Entity>(where);

The problem is, if you wish to use the advance operations like (IN, BETWEEN, etc), this is not possible. The proposal is to simply set it to object so it will inherit the entire behavior of RepoDB base QueryField object.
var where = new LeftQueryField("FieldName", Operation.In, new[] { "Val", "Ma", "St" });
var result = connection.Query<Entity>(where);

Will be a part of release > v1.12.8.


Add checksum test to library deploy

Libraries will now only copy if necessary.
Closes #27

Does the fileset - checksum creation process always result in a consistent ordering (e.g. is it sorted by filename)?  If not, since the entire checksum file is being compared, two development machines alternating deployment may result in different checksum files simply due to ordering, and result in unnecessary copies.  If it's not currently sorted, maybe Ant provides a sorting mechanism for filesets, or maybe checksum has a sorting option?
Even with a consistent total ordering, two different development machines may still have spurious redeployments if one machine has more plugins installed than the other.  The ideal of course would be to split the line and match files individually, and only upload the files with different checksums, but I know that is likely quite challenging in Ant.

Closing to supersede with a PR that fixes both #27 and #34


Containers lost data  when host doesn't shutdown gracefully

Description
If I reboot the host gracefully, containers keep all the data as it before restart.
If I just power off the host , containers will lost the data like routing table setting and env.
Should orchestration handle that case or docker will do that in the future?

Steps to reproduce the issue:

Run a simple container, set env or routing table
Power off the host

Describe the results you received:
Env and routing table will be gone and ip of the containers will be different
Describe the results you expected:
Keep the data container has after restart
Additional information you deem important (e.g. issue happens only occasionally):
Output of docker version:
Docker version 1.10.3, build 20f81dd
Output of docker info:
(paste your output here)

Additional environment details (AWS, VirtualBox, physical, etc.):

Can you provide the exact steps for reproducing? What commands do you run to start the container? Is the container run interactively, and changes made inside the container?

Hi,
Here is the details.
I am trying to use docker container to build a simple demo case that
container A can send all the traffic through container B to container C. In
this case I need to create 3 containers and two networks.
docker run -itd --privileged --net mynet1 --name A image command
docker run -itd --privileged --net mynet1 --name B image command
docker run -itd --privileged --net mynet2 --name C image command
docker network connect mynet2 $(containerB id)
In containers, I will need to set routing rules or some other settings. Now
I am able to ping container C from container A.
 When I restart it, all the
containers are stop. After I restart them, I am not able to ping container
C since all the settings are gone.
My case is much more complex than it, so I need to manually set up again
and again if host powers off for some reason.
I am just wondering that why the settings in containers will be good if I
shutdown the host gracefully. What is the difference? Will docker do
something if it receive any shutdown signal?
In this case, should orchestrator handle it or docker will fix it?
Thanks,
Jiamin
On Wed, Sep 21, 2016 at 9:51 AM, Sebastiaan van Stijn <
<EMAIL_ADDRESS>wrote:

Can you provide the exact steps for reproducing? What commands do you run
to start the container? Is the container run interactively, and changes
made inside the container?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/docker/docker/issues/26762#issuecomment-248672762,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQ3DibIyvE8Yfjc8yEQAIfIF-aqiKbbMks5qsWCCgaJpZM4KCPsb
.

Route settings in the container would not persist.
Likewise if you set routes on the host and reboot, the routes will be gone.
Closing as this looks like expected behavior.
Please feel free to discuss here, but these settings are not expected to persist in a container or outside.


Enable mailer previews in development

Enables mail previews to be displayed when visiting /rails/mailers in development mode.
N.B. Mailer previews did appear to have worked at some point in the past for this project.

LGTM. @matharden don't suppose you've any context on why this might have broken?

No. Dan was talking to me about this yesterday, but I don't know why it stopped working.


Lesson will not allow to progress after it is completed

Challenge http://www.freecodecamp.com/challenges/waypoint-use-css-selectors-to-style-elements has an issue. Please describe how to reproduce it, and include links to screenshots if possible.

Load the page (it should have the previous lesson's code still in it)
Delete the style from the h2 element
Add the style block
Add h2 { color: red; }
Click either run or Ctrl + Enter

It will show you have completed it correctly, but the pop-up does not show to allow you to progress to the next lesson.

@w00dStok thanks for posting this issue!
In order to proceed to next challenge you either need to click on Run code button twice or press Ctrl + Enter twice.
Related to: https://github.com/FreeCodeCamp/FreeCodeCamp/issues/2772 and https://github.com/FreeCodeCamp/FreeCodeCamp/issues/2659.

Please review the Guidelines for Contributing, thank you!.

I did. It didn't matter. It was completely stuck. It happened on a few other lessons as well.

@w00dStok Which browser are you using?

Chrome

I have the same problem also using Chrome.  If I click on the "run" button, it will tell me I succeeded but won't submit.  If I click on the coding area and then ctrl+enter it seems to work.  The key is having your cursor in the coding area I guess.

I have tested your work around and it seems to not work for me. This issue is also happening in "Change the Font Size of an Element".

Just on a hunch I tested this in other browsers getting the same issue. I have tried in Edge, Firefox, and Chrome with the same result.

This looks like an error in the way point itself.
The instructions say to use red but the test is checking for blue.
https://github.com/FreeCodeCamp/FreeCodeCamp/blob/717c56edb7bd07194328b97fa513690fc6807091/seed/challenges/html5-and-css.json#L385
Just to double check, @w00dStok what happens if you use this code:

CatPhotoApp

Kitty ipsum dolor sit amet, shed everywhere shed everywhere stretching attack your ankles chase the red dot, hairball run catnip eat the grass sniff.

@jameskopacz  the only instruction in this challenge's description section which asks to change any color is:

Delete your h2 element's style attribute and instead create a CSS style element. Add the necessary CSS to turn all h2 elements blue.

And this text is from tests' section:

Your h2 element should be blue.

Everything that relates to red color here is just an example i.e.:

When you entered
CatPhotoApp
, you were giving that individual h2 element an inline style.

and

Inside that style element, you can create a CSS selector for all h2 elements. For example, if you wanted all h2 elements to be red, your style element would look like this: .

I changed it to blue and it now allowed me to pass the waypoint.
@bugron My apologies. I obviously missed that instruction.

@w00dStok That's OK. You can now close this issue if you solved your problem, thanks.

Please review the Guidelines for Contributing, thank you!.

I've tried it with red and blue and cannot get past this point. I've also tried running it twice using both methods.

I have same issue here. Tried everything.
although the h2 color is as requested, blue, cannot pass this challenge.
Please, Help.
Thanks

Use this
h2 {
font-family: Lobster;
}

Finally i found that the colon after font-family should not have space.
font-family: Lobster; is working.
font-family : Lobster; is not working.

Finally i did by disabling my dark mode
i guess you all should disable dark mode extension in your brouser during css test


Error: Parameter token or opts.auth is required

I'm getting this error and I can't figure out why, since there's no mention of token or opts.auth in the source code. Here's a sample workflow:
name: test
on: workflow_dispatch

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - name: Install helmfile
        uses<EMAIL_ADDRESS>
And the output:
Run<EMAIL_ADDRESS>  with:
    helmfile-version: latest
    helm-version: latest
    helm-plugins: https://github.com/databus/helm-diff
Error: Parameter token or opts.auth is required

Any ideas? Thanks!

This works if I specify versions for both helm and helmfile, so the issue is probably with resolveLatest.

@joshfrench thanks for your feedback.

@joshfrench we will update the docs.

@bonddim WDYT?

Correct, v1.0.0 requires GITHUB_TOKEN to be in env and it was in README.
You may try helmfile/helmfile-action@main which doesn't require it after #34


Nullable Types in query string always show as required

We are using nullable query string parameters on our controller methods. When using the command line generator, these parameters always show as required in the generated swagger doc.
Steps to reproduce:

Create a new dotnet core project
Create a controller method with a nullable query string parameter.
Use the command line generator to create a swagger doc. Notice the parameter is shown as required.

See below for an example of our controller method and the generated swagger.
public async Task GetById(int id, [FromQuery] bool? someNullableParam)
 { 	"type": "boolean", 	"name": "manage", 	"in": "query", 	"required": true, 	"x-nullable": true }
Thanks

With
 public async Task GetById(int id, [FromQuery] bool? someNullableParam = null)

it works.
Are you sure that it is not required if there is no default value? Or has this changed in ASP.NET Core?

That works, but it seems to be inconsistent with how it works for reference types. For reference types, the required attribute determines if the parameter will be required in the swagger doc, which is what I would expect.
-Shows as required
-public async Task SomeMethod([Required][FromBody]SomeClass someClass)
-Shows as not required
-public async Task SomeMethod([FromBody]SomeClass someClass)
-Shows as required (This is the case that feels inconsistent to me)
public async Task SomeMethod(bool someParam)
-Shows as required
public async Task SomeMethod([Required]bool someParam = false)
-Shows as not required
public async Task SomeMethod(bool someParam = false)
This is not a huge deal for us as we can assign default values for value types so that they show as not required in swagger. I more just wanted to confirm if this was the intended behavior.
Thanks again.

It should behave exactly like Web API does (maybe it is also different for ASP.NET and ASP.NET Core)... The question for each scenario: Is the action called when the parameter is passed or not?

In the below case, the query string parameter 'someParam' is not provided in the request and the action is still executed. However, the parameter shows as required in the generated swagger.
public async Task SomeMethod([FromQuery]bool someParam)
Thanks,
Otis


Bug in Instance.runGenerators()

Running addN with
RunAllGenerators
FlattenAllPass
Creates inconsistent behavior.

I think it would be for the best to not have any Module Declaration in a generator Instance. That should only exist once I run runGenerator().  This means that I might have multiple modules that represent the same thing.

This will be solved with PR #134


Dynamic Chart Example

Is there any demo for dynamic chart using axios or something similar? Thanks.

#43

Thank you.


Add a simple report to samples/bluetooth/peripheral_hids

Hi, was playing with the peripheral_hids sample, having it register a device and no sample code to actually send report notifications feels like a bit of a cliffhanger. Added a simple loop to report a single button if the board supports it, and a comment of how the report looks like. Should be cool for demos to have a working clicker.
Also bumped into an odd issue with the descriptor that was confusing Android hosts for some reason, fixed that too.

@carlescufi @gmarull this may be cool for a demo or more advanced exeercise at the Zephyr workshop, thinking flashing this on a dongle with sysbuild and mcuboot, and then adding the exra buttons for x/y movement (easy enough, bit of copy paste) and flashing OTA. What do you think?


UnixTools: Redirect bot's stderr and stdout to a file

Implement stderr redirection similar to WindowsTools.
Also few minor fixes.

Now we support stdout redirection on Unix if the Debug flag was specified.


Added two more links to the Darknet section and added a new section c…

…alled Malware analysis.
Added two more links to the Darknet section, Whonix and Tails and created a Malware analysis section.

Thanks for adding this and sorry for the delay! Notifications aren't working, for some reason. I will try to get that fixed :)


Update Travis to xenial

would you like to see updates?

I think that in general I'm not opposed to keeping things with older versions of Ubuntu.  It's sometimes nice for CI systems to lag a bit, because that way they reflect what is more commonly deployed.  Backwards compatibility also seems to be more common than forwards compatibility.
If there isn't a driving need for this then I recommend that we wait for a while on it.


DRAFT: First pass at geoip support in benthos

I have not looked into the code yet, but support for geoenrichment is something I need. I, however, need to use ip2location as my provider.
When working on this, will it be possible to make it generic in code so Maxmind, ip2location and others can be added with more common code?

Merged from https://github.com/Jeffail/benthos/pull/1068


Fix sudo when running on docker

What's the problem in Docker with the current code? Thanks!

The sudo command doesn't exists in docker image. It throws errors
Start function webprobe_full 2021-12-21 03:19:34
reconftw.sh: line 821: sudo: command not found
cat: .tmp/probed_uncommon_ports_tmp.txt: No such file or directory
End function webprobe_full 2021-12-21 03:19:34


Use region identifiers when setting Tax Class artifacts and dependencies

Fixes #11 by using region identifiers instead of country identifiers when obtaining artifacts.

Hi @mattbrailsford not sure if you can use this one, just realised github has brought over a lot of extra commits 🤔.

Hmm, yea, it looks like you might have made your changes in a forked branch of main which is the v14 codebase. If you clone the support/13.x branch and make your change there, I think that should be what we need.


Elevated var not showing correctly

Believe me it is not a system or privileged account, but:

Even so, tried an implant which needed and:

elevating via implant+post execution worked all right.
Something is broken with the elevated var showing incorrectly for win2012r2 build 9600.
Pd. just realized it says status: dead. it was not.

We're checking whether a Zombie is elevated or not by running:
net pause lanmanserver
If you get a System Error 5, then you are not elevated. Anything else, and I believe that you should be. If you have permissions to run the action, running pause doesn't do anything, which is why we chose it. It's possible that there are multiple privilege levels that allow a user, who is not an administrator, to perform this action.
What output do you get if you run net pause lanmanserver? Could you also post whoami /groups?

I might as well change up the elevation detection to run whoami /all and check for the presence of SeDebugPrivilege. We had a small discussion about it in the office, it'll definitely be more reliable. I don't know if it will be called the same thing across different languages of Windows, but we can cross that bridge when we come to it.

There are two different Zombies in those screenshots. I only see that Zombie 0 was elevated, was Zombie 1 also elevated? Was Zombie 0 manually killed? We don't dispatch jobs to manually killed Zombies since there are no cases where that Zombie will be able to run that job.

Sorry, I was busy with other stuff and couldn't get to this until now.

What output do you get if you run net pause lanmanserver? Could you also post whoami /all?
Did you made any changes? the output of zombies  now shows correctly the elevated value.
lanmanserver now returns System error 5 has ocurred. Access is denied.
whoami /all is hard, too many entries of the domain I am working with and don't wanna mess with it.
There are two different Zombies in those screenshots. I only see that Zombie 0 was elevated, was Zombie 1 also elevated?
It took me a while to remember what I did, I will try to explain:
I dropped the mshta command on a cmd, then zombie 0 hooked. It was an unprivileged cmd with an unprivileged user.
The output of zombies 0 was elevated=YES
It could not be disconnected as it was freshly hooked.
Later on (after I closed that instance) I wanted to post this and recreated and environment. This time I had done a few more tests before I took a screenshot of mimikatz failing, so it was with zombie 1 instead of 0. But represents same situation. Sorry about the inconsistency.

This time around, doing same chain process, took me to show correct values for status and elevated.
If you did not change anything regarding these two, then I did something wrong or did not reproduced correctly.


Fix errors with avanzu:admin:fetch-vendor and avanzu:admin:build-assets commands

Fix theses errors :
[Error] bower bootflat#*          invalid-meta bootflat is missing "main" entry in bower.json
unable to process "/bundles/avanzuadmintheme/vendor/adminlte/plugins/daterangepicker/daterangepicker-bs3.css" with Error: ENOENT, no such file or directory '\bundles\avanzuadmintheme\vendor\adminlte\plugins\daterangepicker\daterangepicker-bs3.css'

@chteuchteu Could you quick review this PR please? Thanks

Thank you for your contribution, sorry about the delay!


Clean up Prometheus firewall rule after test

Cherry-picks from master: https://github.com/kubernetes/perf-tests/pull/909, https://github.com/kubernetes/perf-tests/pull/911
/cc wojtek-t

/cc mm4tt

/lgtm
/approve


xcm tool for NFTs

XCM tool for cross chain NFT
The Crosschain NFT Pallet is a unique initiative designed to facilitate the smooth movement of NFTs across various blockchain networks, utilizing the XCM protocol. Through the implementation of this pallet, individuals can effortlessly exchange NFTs between relay chains and parachains.
Grant level

[x] Level 1:  Up to $10,000, 2 approvals
[ ] Level 2:  Up to $30,000, 3 approvals
[ ] Level 3:  Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

[x] The application template has been copied and aptly renamed (project_name.md).
[x] I have read the application guidelines.
[x] Payment details have been provided (bank details via email or BTC, Ethereum (USDC/DAI) or Polkadot/Kusama (USDT) address in the application).
[x] The software delivered for this grant will be released under an open-source license specified in the application.
[x] The initial PR contains only one commit (squash and force-push if needed).
[x] The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
[ ] I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @_______:matrix.org (change the homeserver if you use a different one)

Thanks @anshulWeb3 for the application.

Can you integrate more technical details into the delivery table itself, such as the pallet functions?
We only offer USDT payment on Statemint/Statemine. Please look at our payment options for Ethereum.
Are you able to provide the GitHub accounts of your team members, or otherwise provide proof of previous work?

Thanks!

Thankyou @keeganquigly for the review.

I have added details to the delivery table.
I have changed the payment address.
The names of team members are clickable and they have the github repos for the team members. Also, I have added the stack exchange profiles of my team members.
Kindly check.

Thanks for the changes @anshulWeb3 it's looking better now. I will mark the application as ready for review and ping the committee members internally. In the meantime, a few additional questions:

Did this come out of a need to transfer your own NFTs, or otherwise what temperature checks have been done to let you know that this is needed in the community?
Have you checked other NFT bridging solutions to see if some of these pallets have already been built? I seem to remember RMRK working on a substrate-to-substrate bridge but am not finding any updates with a quick search.

Thankyou @keeganquigley  for the questions.

To answer your first question, our team was researching on XCM and it's applications as we were looking into interoperability solutions. Cross chain NFT transfers interested us as NFT are a big part of functionality on blockchain and there are already many NFT projects that are live. Cross-chain support for NFT across the Substrate ecosystem could open a lot of possibilities in the future.
Yes, we looked into other bridging solutions. Work has been done for Fungible assets but we couldn't find anything relevant to our needs. Hence, we felt a need for this to exist. xTokens pallet exists why not xNFT. This project is also a part of our research on XCM and there is a lot more to come.

Thanks @Noc2  for reviewing the application.

Yes, we are aware of XCM v3 and we are building this xNFT pallet on top of the XCM v3 functionality for NFT transfers i.e the pallet consists of methods that combines the XCM functionality relevant for transferring NFT across chains. This pallet may be integrated with the substrate SDK as a module.
As of now our pallet supports the transfer of (only) NFT that are made using the NFT pallet provided by substrate. We plan to extend this functionality for custom NFTs in future. We have researched the xToken pallet (used for cross chain Fungible Asset transfers) currently used by parachains like Moonbeam and also have studied about Sovereign Account, TeleportAsset and ReserveTransferAsset. The architecture of the xNFT pallet will be somewhat similar to the xToken pallet.

Hi @anshulWeb3,
I think this discussion is also relevant for your tool.

Thankyou for the review @takahser .
No, I just looked into this issue and the PR. Thankyou for bringing this into our notice. I believe that we will have to start our work once this PR is merged.

Hi @vstam1 ,
Thankyou for the reference.

@anshulWeb3 thanks for your feedback.

I believe that we will have to start our work once the PR you mentioned in your comment is merged.

I agree that it's a good idea to wait for the relevant changes on the NFT pallet to be implemented, but I'd generally be happy to support this effort once that's done. I think it's advisable to have a look at the RFC that @vstam1 has shared in the comment above. Ideally, you'd get familiar with the changes that are currently being implemented and adapt your proposal accordingly.
In the meanwhile I'm going to put this application on hold, but feel free to further update it.

I have to mention that the RFC is a proposal for a new instruction for XCMv4. It can still take some time before we release v4. The planning now is Q4 2023.

@vstam1 do you think it'd be possible to parallelise the development of XCMv4 and this proposal? Maybe, once the relevant part of the XCMv4 API is fixed the grantee team could start implementing this?

Unfortunately we cannot. XCM is versioned, and we cannot add another instruction to version 3.

Hi @anshulWeb3 did you want us to re-open the pull request? Are you still working on the milestone?

Hi @keeganquigley we are currently looking for solutions which align with "not changing the Frame NFT pallet" approach. Apart from that we are waiting for the required changes to get uptream.

Thanks @anshulWeb3 do you think these required changes will happen soon?

Hi @anshulWeb3 do you plan on submitting a delivery soon? If not, please consider submitting an amendment to extend the timeline. Thanks!

Hi @anshulWeb3 are you still working on this grant? I noticed there hasn't been much activity on the repos. Please let us know, otherwise after 2 weeks we will close the grant due to inactivity.

Hi @keeganquigley . Sorry for the delayed response. I was on a  Medical leave and the access to the account was with me only so any other team member was unable to respond in time. We've been engaged in research related to this matter and have explored various methods to access private fields such as ItemMetadataOf and CollectionMetadataOf within the FRAME NFT pallet, without altering the actual code. During this process, we've identified a solution and are currently in the implementation phase. We plan to provide you with a comprehensive update by next week. Thanks for your patience.

Hi @keeganquigley . We have successfully reverted all modifications made to the FRAME NFT pallet, including changes to structs such as CollectionDetails, ItemDetails, CollectionMetadata, and ItemMetadata. These structs now align with the standard FRAME NFT pallet.
However, we are currently addressing the final outstanding change, which involves making a Type of RuntimeCall in the Config of the FRAME NFT pallet to enable the calling of functions of the FRAME NFT pallet from the xnft pallet. We are actively working to resolve this issue and will provide updates as soon as it is resolved.
If you have any suggestions or insights regarding this matter, we are open to receiving them. Additionally, we will keep you informed about the resolution of the previous RuntimeCall issue as soon as it is resolved. Thank you for your understanding and cooperation.

Thanks for the update, @anshulWeb3. Sounds good to me. But could you submit an amendment to the grant application with an updated timeline? That makes it a lot easier for us to track project progress.

Hi @keeganquigley , @semuelle  We have successfully addressed the Runtime call challenge and are pleased to inform you that we will be delivering the xnft-pallet by the upcoming week.

Hi @keeganquigley . The development is done and we are  setting up the testing environment using Trappist. We expect to deliver by Wednesday. Thanks!

Great @anshulWeb3 sounds good thanks for the update!

Hello @keeganquigley . We are happy to announce that we have submitted the delivery of xNFT pallet. Looking forward to your response.  Link to the PR.
Thanks.


Returning JSON of modules broken

It seems that 0.3.1, or more specifically https://github.com/QubitProducts/exporter_exporter/pull/38 broke the ability to return JSON of all modules and their configuration on request.
Executing curl -XGET -H "Accept: application/json" localhost:9999 now logs ERRO[0013] json: unsupported type: func(*http.Request)

Right, we're at the point now where I really should ad a test suite.


Could not find encoder for codec id 27: Encoder not found

OpenCV: FFMPEG: tag 0x34363258/'X264' is not supported with codec id 27 and format 'mp4 / MP4 (MPEG-4 Part 14)'
OpenCV: FFMPEG: fallback to use tag 0x31637661/'avc1'
Could not find encoder for codec id 27: Encoder not found

H264 encoding is not supported because it falls under GPL license. See: https://github.com/skvark/opencv-python/issues/100
You must build OpenCV yourself and link it with system FFmpeg.
About licensing:
If I ship GPL'ed components with opencv-python I would have to re-license the whole package under GPL license and any package using opencv-python, respectively, would have to be licensed under GPL. This would also mean that this package or any package which uses opencv-python could not be used for commercial purposes / proprietary applications unless you are willing to publish your software source code.

This helps. Thank you.

H264 encoding is not supported because it falls under GPL license. See: #100
You must build OpenCV yourself and link it with system FFmpeg.
About licensing:
If I ship GPL'ed components with opencv-python I would have to re-license the whole package under GPL license and any package using opencv-python, respectively, would have to be licensed under GPL. This would also mean that this package or any package which uses opencv-python could not be used for commercial purposes / proprietary applications unless you are willing to publish your software source code.

But  how can I do?

H264 encoding is not supported because it falls under GPL license. See: #100
You must build OpenCV yourself and link it with system FFmpeg.
About licensing:
If I ship GPL'ed components with opencv-python I would have to re-license the whole package under GPL license and any package using opencv-python, respectively, would have to be licensed under GPL. This would also mean that this package or any package which uses opencv-python could not be used for commercial purposes / proprietary applications unless you are willing to publish your software source code.

But how can I do?

Follow the manual build instructions in the readme: https://github.com/opencv/opencv-python#manual-builds

Thank  you! I will try.
---Original---
From: "Olli-Pekka @.>
Date: Wed, Mar 31, 2021 15:56 PM
To: @.>;
Cc: "Lin<EMAIL_ADDRESS>Subject: Re: [opencv/opencv-python] Could not find encoder for codec id 27: Encoder not found (#207)
H264 encoding is not supported because it falls under GPL license. See: #100
You must build OpenCV yourself and link it with system FFmpeg.
About licensing:
If I ship GPL'ed components with opencv-python I would have to re-license the whole package under GPL license and any package using opencv-python, respectively, would have to be licensed under GPL. This would also mean that this package or any package which uses opencv-python could not be used for commercial purposes / proprietary applications unless you are willing to publish your software source code.
But how can I do?
Follow the manual build instructions in the readme: https://github.com/opencv/opencv-python#manual-builds
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

If you are using conda, uninstalling OpenCV through pip and instead using conda install -c conda-forge opencv worked for me! I can run cv2.VideoWriter('out.mp4', cv2.VideoWriter_fourcc(*'avc1'), FPS, (WIDTH, HEIGHT)) without issues.


ee_platform_distro is not "debian"

I try to install full stack on Debian 7 and i've got this error :type object 'EEVariables' has no attribute 'ee_nginx'.
I searched and i found that command platform.linux_distribution() is not equal to "debian" but "Debian". So variables are not set correctly in variables.py
ee --version EasyEngine v3.1.2 Copyright (c) 2015 rtCamp Solutions Pvt. Ltd.

@cicoub13 ,
We are not able to reproduce this issue on Debian 7.8.
Can you please update all your packages, and check again?
I am closing this issue now, feel free to reopen if face this again.

My server is a Kimsufi 2G hosted by OVH France.
EasyeEngine use python linux_distribution (base on etc/lsb-release).
ee_platform_distro = platform.linux_distribution()[0]

cat /etc/lsb-release
DISTRIB_ID=Debian
DISTRIB_RELEASE=7
DISTRIB_CODENAME=
DISTRIB_DESCRIPTION=

I can suggest a pull request with ".lower()" to correct if necessary.


Stop & remove app containers in parallel to local push, with better feedback

Right now, local push is fairly synchronous: https://github.com/resin-io-modules/resin-sync/blob/master/lib/capitano/resin-toolbox.coffee#L164-L198. We do some querying up front, and wait until the existing app has been killed and remove, and then we do the build etc.
This means for the normal cached development flow, the majority of time is spent on the initial 'Stopping and removing' step, with no feedback, followed by high speed build output.
We should do more of this in parallel, and with better feedback:

Stop & remove existing containers in parallel to the build
Query for the previous image id in parallel to the build
Show a spinner when the uploading for the build itself starts
Remove the old image in parallel to creating & starting the new container.

@lekkas I noticed this in my talk on Friday - it makes it a bit awkward to demo, because it just sits on 'stopping & removing' for ages (well, 10s or so), and it's not easy to explain to an audience what's going on. I think there's some nice UX tweaks and overall performance improvements here in some code people will be running pretty often. Are there any reasons not to do the above? Is there a specific reason we always stop & remove the existing container before we let any building start?

@pimterry If we can safely parallelise the tasks

build // stop&remove old containers, query image id
start container // remove old image

with the new build let's go for it. There is no specific reason to keep the initial waterfall approach, it was the simplest to start with. I also agree on giving the user some feedback like the spinners you suggest because long, silent pauses can be awkward :)

Related to #528

The local push command was replaced with the "live push" feature which is enabled by default with the balena push <ip-address> command in CLI v11. The logic for stopping and restarting containers is now much cleverer. :-)


Dark Theme for the website

Is your feature request related to a problem? Please describe.
Implementation of the Dark Theme for the React Website for Github Readme Quotes, to get a view of how the card looks in the Dark theme of the Github API

Hi Shravan, I'd like to help with this issue.
Since this app is using Material-UI, I could try to implement custom global themes.
More Precisely:

Add a ThemeProvider at Dashboard
Import custom Global theme objects
Add toggle theme state to Dashboard
Append Toggle Button to Dashboard / AppBar to change theme state

Is this similar to what you've had in mind?

Hi @koskrit ,
Thank you for your time!
Yes, we were looking for something similar to what you proposed. Feel free to implement your ideology and raise a PR.
Looking forward to see your PR.

Update1:

[x] Added ThemeProvider at Dashboard
[x] Added toggle theme state
[x] Added Toggle Button to Dashboard / AppBar to change theme state
[x] Tested Theme functionality with sample themes
[ ] Create Github Dark Theme with JSS

@koskrit Will Peer review the code and let you know the status.

Before I do some cleanup and submit the PR, maybe you could give me some thoughts on the first draft.
Update2:

[ ] Create Github Dark Theme with JSS

Theme Draft1

All colors are taken from the Github color palette
Any reflections or preferences for the color choices?

Hi @koskrit
I believe the colour choices for the dark mode looks good for now. Inverted duo is fine for now!


Upgrade the version of Jetty that we use to 9.4.18.v20190425

Task Description
We need to upgrade to Jetty >= 9.4.18.v20190425.
Acceptance Test

[ ] Building the code with mvn clean install -Dintegration.tests still works.
[ ] Running mvn spring-boot:run in the strongbox-web-core still starts up the application correctly.
[ ] Building the code and running the strongbox-distribution from a zip or tar.gz still works.
[ ] The tests in the strongbox-web-integration-tests still run properly.

Task Relationships
This task relates to: #1254 , #1130 (and should later on be re-applied there).
Help

Our chat
Points of contact:

@carlspring
@sbespalov
@fuss86

Hi ,
Can I take this up?


replace lodash

would it be possible to replace the lodash isequal with something a little more robust/secure?
there are a number of options including fast deep equal
here's the details of the security issue - https://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-23337
we're blocked from using the player right now because of this. i'm happy to open a pr if you're happy with the change.

Sure, pr is welcome!


BVAL-596 Move ValidateUnwrappedValue to javax.validation.metadata

https://hibernate.atlassian.net/browse/BVAL-596

Isn't there any include of that file that needs adapting?

@gunnarmorling nope, it's not described in the spec AFAICS. Maybe it should be?

Yes, absolutely. Each API type should be contained in the spec.

@gunnarmorling I added one more commit to mention validateUnwrappedValue().

Thanks, @gsmet!


Docker image tag 2.9 is set, but 2.9 is still RC

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you do?
We are using Renovate Bot to keep our dependencies up2date and we are using the traefik docker image from docker hub.
What did you see instead?
When the 2.9 rc versions of traefik get released, a 2.9 tag gets created for docker hub.
So dependency checkers like dependabot or renovate propose to update to 2.9 tag, but v2.9 is still in rc.
Because of that I would propose to create a base 2.9 tag only if the released version is not alpha, beta or release candidate version.
What version of Traefik are you using?
v2.8 from docker hub
What is your environment & configuration?

If applicable, please paste the log output in DEBUG level
No response

duplicate of #9353


{ [Error: timedout while connecting to smtp server] code: 4, smtp: undefined }

After installing emailjs, I run the following code for mailing in nodejs
emailjs = require('emailjs');
var server = emailjs.server.connect({
user:"mygmail.com",
password:"gmail password",
host:"smtp.gmail.com",
ssl:true,
port: 465
});
server.send({
text: "message",
from:"LLVC ",
to:"",
subject:"Subject"
},
function (err, message) {
console.log(err || message);
});
when running the script, I got a error
{ [Error: timedout while connecting to smtp server] code: 4, smtp: undefined }
I want to fix them.
Thanks

You timed out while connecting to the SMTP server.