Use several selectors?

Hello, is it possible to use several selectors one after the other. For example from here:
http://voxeu.org/article/economics-secession
I can get separately h1, .article-teaser, article-content
with
curl hIttp://voxeu.org/article/economics-secession | ./pup 'h1 text{}'
and so on, but I would like the text to appear one after the other. That is, the text from h1, then the text from .article-teaser, and then the text from .article-content.

I was wondering if I could run pup with several selectors but have the results appear in combined order. i.e. group each selector result together: selector1-result1,selector2-result1,selector3-result1, selector1-result2,selector2-result2,selector3-result2, and so on.


Draft:  test automation

Proposed changes
Describe the use case and detail of the change. If this PR addresses an issue on GitHub, make sure to include a link to that issue using one of the supported keywords here in this description (not in the title of the PR).
Checklist
Before creating a PR, run through this checklist and mark each as complete.

[ ] I have read the CONTRIBUTING document
[ ] I have run make install-tools and have attached any dependency changes to this pull request
[ ] If applicable, I have added tests that prove my fix is effective or that my feature works
[ ] If applicable, I have checked that any relevant tests pass after adding my changes
[ ] If applicable, I have updated any relevant documentation (README.md)
[ ] If applicable, I have tested my cross-platform changes on Ubuntu 22, Redhat 8, SUSE 15 and FreeBSD 13

Codecov Report
Patch and project coverage have no change.

Comparison is base (3d9d248) 67.43% compared to head (c57efb7) 67.43%.
Report is 4 commits behind head on main.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #428   +/-   ##
=======================================
  Coverage   67.43%   67.43%
=======================================
  Files         113      113
  Lines       12764    12776   +12
=======================================
+ Hits         8607     8616    +9
- Misses       3588     3591    +3
  Partials      569      569

see 2 files with indirect coverage changes

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


Config

Great would be to give us config to define globals like colors, credit position, width, height and so on - would be great.

You can do all of that. If you look at the source, I have exposed a lot of those properties via the 'options' attribute on the directive. You can create an object on your scope, like:
$scope.amChartOptions = {
    data: $scope.myDataObject,
    lineColor: '#000000',
    marginLeft: '40'
}

then pass it to your directive
<am-chart id="myFirstChart" options="amChartOptions" height="300px" width="500px"></am-chart>

Again, I'm still working on exposing a lot more and trying to come with conventions for properly handling things like live chart update.

Yes, but You have to define it every time You use Your directive.
Better would be global config.

That's the point. Directives are compartmentalized so they can be ultra reusable. I would not want to pollute some kind of global scope with a config for these charts. Instead, I could store that config object in a more persistent location, like a service, and retrieve it and modify it as I need it. In all but the rarest of use cases, you're going to have a different dataset and probably different key and value fields for the graph(s) in each chart.
The more you try to make a directive like this specific to your use case, the more you couple it to your application. I wrote this to be application agnostic so that anyone can just grab the directive, throw it in their project, and be up and running without having to worry about some of the finer details.


chore: import repository https://github.com/hazem-internship/thingsboard.git

this commit will trigger a pipeline to generate the CI/CD configuration which will create a second commit on this Pull Request before it auto merges

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign
You can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Include task name when raising TaskNotFound

TaskNotFound may appear in logs without indicating which task could not be found.
By comparison, consider that the code {}["foo"] raises KeyError("foo") -- i.e. including the failed key in the exception raised has precedent in Python's built-in dict type.
This PR adds the name to the exception in line with said precedent.

It looks like black has a missing dependency in the Python 3.8 Syntax check. I am assuming that is not caused by anything in my PR.


Use a file-based, persistent storage

TL;DR: if a user does not open Cosmic Everyday for three months, its data is wiped.
Currently, CE uses PouchDB, that uses IndexedDB as its underlying driver, that utilizes built-in chromium storage. This storage is considered being ephemeral: though it may be used as a storage for a database, it is not meant for long-term use. As a result, if a database is not used for a considerable amount of time, it is wiped out. It seems that for CE, it is a period of three months.
So, either PouchDB's backend storage should be changed to a local, file-based, more native adapter, or another DB should be picked.

@CosmoMyzrailGorynych Have this been fixed? I can try to change it to the one I use.

@Bandito11 no, it wasn't. Feel free to send a pull request or make a fork.


Integration tests for PrestaShop 1.7

@maf-embraceit please review the pull request

@saadidrees711 the changes have been reviewed.


ccu: add SMHC clock register and SMHC bus gating reset register

Add SMHC Clock register and SMHC Bus Gating Reset resgister, including the definition of regitster bitfiled and Read/Write functions in RCC peripheral refer to Section 3.2.6 CCU·Register Description.
There are also some minor amends that the accord of register document, the offset_ccu test case and  the additions of is_xxx_reset_cleared functions testcase in the case of xxx reset signal cleared by hardware.

LGTM


Easier ECR integration

At the minute it's a little bit tricky to get ECR integration working, this makes it more seamless by adding a parameter called ElasticContainerRegistryAccess that is either none, readonly, poweruser or full. If this is set, everything else will be setup for ECR to work out of the box.
Remaining todo:

[x] Document the new parameter

Any objections to me merging this @toolmantim / @sj26?


[feature request] Add "charge on solar" toggle

I'd like the "charge on solar" toggle that is available in the app to be also available in the integration.
This would be usefull to create better automations. ie, in my case, I want to only charge on solar once the powerwall is full.
Charge on solar is a feature where the car and the gateway will talk together to have the car request just the right amount of current to match the solar production, resulting in no grid or powerwall consumption. See Tesla website. The issue is that when enabled, the powerwall will not charge.
This is the button I'd like to be able to toggle via the integration:

Thanks a lot

I would like to add the two charge limit %s to this for the charge on solar feature - ie any source and solar limits

Adjusting the Charge on Solar settings is not currently supported by the Tesla API, so it cannot be implemented in this integration.
I would be a nice feature to have.

Thanks for looking at it


SetIamPolicy should use etag to determine idempotency.

The InstanceAdmin::SetIamPolicy should examine the etag field to determine if the operation is idempotent, we currently assume that it never is.  We need to verify the server actually uses the etag parameter though.

Well, it seems that Cloud Bigtable is not returning etags for AppProfiles, so this may be moot. I asked the Cloud Bigtable devs, depending on their answer this will either be closed or removed from the milestone.

This is currently not implemented, marking as blocked for now.

Still blocked. b/132681137

I think we can generalize this problem.  For all services, the SetIamPolicy() function is idempotent if the request has a ETag value set.  I am going to change this to be the generator and to call it unblocked.


[Suggestion] Add option to change color

It would be great to have a funtion to change the color of background on fullscreen and fullscreen notifications:

These fullscreen notifs no longer exist, you're using  an  old  version of the extension. In the new version you can set the font size to big.


.gitignore should list examples/calc/calc + other binaries produced

Fixed in https://github.com/DmitryOlshansky/pry/commit/0cbd801870d96422735726f8c2d69022373876bf


Fixing warnings in the GitHub Service API/Impl modules

Changes on warnings and suggestions reported by Eclipse and Sonar.
Signed-off-by: Xavier Coulon<EMAIL_ADDRESS>

@ALRubinger a first PR to remove various warnings in the GitHub Service API and Impl modules (because I like to have as little warning decorators as possible in my IDE). More to come if you like the changes ;-)

Welcome, @xcoulon!  I'd put line notes into the commit.
And I totally get the motivation here, but some of the changes are IMO removing clarity (like explicit throws clauses on RuntimeExceptions).  Lots of other good stuff like unifying camelcase of arguments and docs, making all variables final unless they need to be mutable, etc.
But ultimately I bet your talents are best spent on feature dev and bug fixes as opposed to code style checks. :)
Really glad to have you aboard.  Will be looking to get you a feature area or task to own.
With some of the required line notes addressed I can put this upstream.

Thanks for your feedback, @ALRubinger ! I intended to work on features, but I thought I could give a first contribution by fixing a few warnings that I got in my IDE, which, btw, gave an opportunity to start getting more familiar with the code ;-)

@ALRubinger I just pushed an update of the PR with all your comments taken into account.

Introduced #66 to reflect these changes

Rebased atop master and committed 3f38cbfde69f8e4fed7078942669dc590ee00b45


Split celery fixtured/unfixtured jobs

Add tox environment and GitlabCI job for tests requiring celery running in background during tests
Todo

[ ] Add pytest.skip guard instead of --ignore in tox.ini
[ ] Move as many tests as possible to "fixture" tox environment

@pbugni tagged you for a followup review; LMK if you think any of the Todos I have in the PR description should be part of the PR


make branching kata

examines the following commands in regards to a branch

git branch and -a
git checkout and -b
git diff

Along with the shorthand notations HEAD ^ ~
Examples:
There should be two branches, both pointing to the same commit.

Ok just realized there was one already.... will look that one over.


Mistake when open the select

Hi Guys
Project with Yeoman,  and the structure has a  views, and controller and i use routeProvider, no use demo.js because each view has a controller.
i follow this steps
/**************************************************************/
bower install angular-ui-select
Inside your HTML add
select.js:
select.css:
Add the ui.select module as a dependency: angular.module("myApp", ["ui.select"]);
/**************************************************************/
but when try to open the view give me a error like this
undefined it's no a function, if the steps are this what more need to put on the app.js file.
Log Error
TypeError: undefined is not a function
at link (http://localhost:9000/bower_components/angular-ui-select/dist/select.js:633:11)
at nodeLinkFn (http://localhost:9000/bower_components/angular/angular.js:6579:13)
at compositeLinkFn (http://localhost:9000/bower_components/angular/angular.js:5986:15)
at nodeLinkFn (http://localhost:9000/bower_components/angular/angular.js:6573:24)
at compositeLinkFn (http://localhost:9000/bower_components/angular/angular.js:5986:15)
at publicLinkFn (http://localhost:9000/bower_components/angular/angular.js:5891:30)
at boundTranscludeFn (http://localhost:9000/bower_components/angular/angular.js:6005:21)
at controllersBoundTransclude (http://localhost:9000/bower_components/angular/angular.js:6600:18)
at ngRepeatAction (http://localhost:9000/bower_components/angular/angular.js:20084:15)
at Object.$watchCollectionAction [as fn] (http://localhost:9000/bower_components/angular/angular.js:12126:13)
i try this issue https://github.com/angular-ui/ui-select/issues/96 but the error it's the same, change the files select.min.js and select.min.css => select.js and select.css but the error it's the same

Closing this issue as over a year old and doesn't have a repro sample.
If you believe its still relevant please reopen with a plunkr (or similar) against the latest version of ui-select (currently v0.15.0)


Verify a workset only exists along with a reboot context

Adds the following:

Serializes a workset to disk during setup.
Upon deserializing a RebootContext, delete the file from disk (We support rebooting once and only once)
Check if a workset exists with a RebootContext

If True, continuing processing
if False, mark the tasks & node as "Done" with appropriate errors via:

send WorkerEvent::Done events for each of the tasks in the work set
send StateUpdateEvent::Done for the node

This passed basic integration tests, but none of those do a reboot.
This PR should update the integration tests to one of the tests to enable reboot_after_setup.


Without the Splash page other pages do not appear

To reproduce the issue comment SplashFactory = (e) => new Views.Splash(e); at
    public App()
    {
        InitializeComponent();

        // DOCS: https://github.com/Windows-XAML/Template10/wiki/Docs-%7C-Cache
        CacheMaxDuration = TimeSpan.FromDays(2);

        // DOCS: https://github.com/Windows-XAML/Template10/wiki/Docs-%7C-BackButton
        ShowShellBackButton = SettingsService.Instance.UseShellBackButton;

        // DOCS: https://github.com/Windows-XAML/Template10/wiki/Docs-%7C-SplashScreen
        //SplashFactory = (e) => new Views.Splash(e);
    }

Good one. Line 218 of HamburgerMenu.xaml.cs was the cause. Resolved.


Missing template diagram/erd_template.gommd in v0.2.0

Thanks so much for the quick fix in #8, when trying it out on the schema that produced that issue for me I ran into another issue though. Turning on the debug flag (thanks for that too) I got this output:
.  ..___.__ .  ..___.__ .__
|\/|[__ [__)|\/|[__ [__)|  \
|  |[___|  \|  |[___|  \|__/ (0.2.0)

Create MermaidJs diagrams from your database

INFO[0000] Got tables                                    count=1
INFO[0000] Got columns and constraints constraints       columns=5 constraints=0
ERRO[0000] Could not load template file | open diagram/erd_template.gommd: no such file or directory

If I manually download that file and place it in the path it works, but I'm guessing that it was meant to be bundled into the binary.

Thanks for pointing out - totally missed that one due to local testing.
Created a patch version 0.2.1 that fixes the issue - feel free to reopen the ticket if it not works as expected.


troubleshooting: Large transactions do not complete

Finalize guidance: https://cockroachlabs.atlassian.net/wiki/spaces/TS/pages/1139081478/Large+transactions+do+not+complete
Relates to: https://github.com/cockroachlabs/support/issues/684

This guidance is complete.


[Installer] [Bug] .Net Framework error

The Installer needlessly suggests .Net Framework 3.5 needs installing even though RepoM doesn't target .Net 3.5 (which has long been deprecated anyway).
Also the error message is shown using a weird/broken font:

Strange, Never seen this before. Is this the first time this your machine/repoM suggest to install 2.0 and 3.0?

Yes, first time.


Connection management improvement

We need to improve connections management.
Partially this task is covered in #297 (folders hierarchy).
Another ideas:

Connections filter (similar to drivers filter)
Folders coloring
Tagging (it overlaps with folders)

Maybe some presentation switcher is needed in database navigator (flat, folders, tags)

One really annoying issue I have related to connections, is running on a laptop which is suspended / resumed regularly....
Naturally when I resume from a different IP address, my connections all fail, and dbeaver fails them immediately in this situation, but even after this, when I click on "Disconnect", so I can "Reconnect", the disconnection takes so long that I end up quitting DBeaver and restarting it instead.

Nested folders management will be added in the next version.


[Question] What is the formly way to remove a form field and its FormControl(s)?

I'm submitting a ...  (check one with "x")
[ ] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[X] support request

Current behavior

I am dynamically adding fields based on User selections on previous form fields.  All of this works as expected, but we allow the User to remove these fields (e.g. similar to repeater examples).  What I cannot figure out is how to properly do a full clean up.
I currently manually handle it by removing each part individually: field from FormlyFieldConfig[], formControl from the form, null or deleting the property off of the model.  This process seems a little too manual and I wanted to know if there's a more formly way to do this.  See https://stackblitz.com/edit/ngx-formly-ui-material-i9sndp
Note: I'm not looking to using hide or hideExpression for these fields, since I would rather completely remove them.

let's give it a try!

I propose adding a new option strict which force immutability and cleanup the removed field (formControl and model value).
strict = immutable( #1427) + cleanup the formcontrol and its model value.
WDYT ?

I generally like immutability pattern, so I think adding strict is reasonable!

added to V6 roadmap


CodeAnalysis pipeline fixes, eslint bump, test fixes

Fixes #2741
Fixes #2740
Description
Pins dependencies for the code-analysis CI job. With the release of TypeScript 4.x, the pipeline was pulling down the typescript@latest which was resulting in eslint errors:
error  Parsing error: Cannot read property 'map' of undefined

Specific Changes

Pins dependencies for the code-analysis CI job.

Addresses #2741

Fixes "build" and "test" scripts in botbuilder-dialogs-adaptive and adds tsconfig.json for botbuilder-dialogs-adaptive/tests

Addresses #2740

Aligns and bumps eslint-related dependencies in libraries
Removes default "test" scripts that resulted in lerna run test failures.
Places contents of .eslintignore in .eslintrc.json's ignorePatterns

Testing
Verified locally that all of botbuilder-dialogs-adaptive tests run and are built.
Manually ran CI for this branch where the CA step passed:

Pull Request Test Coverage Report for Build 160231

0 of 0   changed or added relevant lines in 0 files are covered.
2 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.1%) to 82.908%

Files with Coverage Reduction
New Missed Lines
%

libraries/adaptive-expressions/src/builtinFunctions/getNextViableTime.ts
1
88.89%

libraries/adaptive-expressions/src/builtinFunctions/getPreviousViableTime.ts
1
87.3%

Totals

Change from base Build 159202:
0.1%

Covered Lines:
15158

Relevant Lines:
17390

💛  - Coveralls


Feat/config variables

[x] add config variables

[x] remove deeppavlov_root in favor of a DEEPPAVLOV_PATH variable

[x] merge name and class into class_name

[ ] update docs

Should close #112


The default branch name isn't main

Setting the default branch name to main is more inclusive, moreover main is the default branch name that github uses

thank you for raising this issue, I initiated this repo via git and it gave me master , I changed the branch now to main.


Use transpiled imports from mapbox-gl-style-spec

This pull request replaces #92.
The downside is that all bundles created from ol-mapbox-style will be larger by 10 kB than with the source imports we previously used.
For create-react-app users, we should consider making that work with ES modules, which it maybe already does in the latest alpha version. See facebook/create-react-app#3889.
That said, I'm not sure if we want to merge this. @bartvde @frankrowe what do you think?

I've tried this with CRA 2.0 this morning and I don't think it solves the problem directly.  Or at least the way Webpack is configured is not doing transpiling the deeper modules.
I'm getting the same syntax errors from that I was getting with CRA 1.x.

Can you point me to an example project so I can reproduce the issue and investigate? Thanks!

hey @ahocevar basically the instructions here: https://www.npmjs.com/package/@boundlessgeo/sdk
just make sure to leave out the version numbers for ol-mapbox-style and sdk

I just came across this same issue trying to use ol-mapbox-style with Parcel.  It fails to parse the flow syntax in @mapbox/mapbox-gl-style-spec/util/color.js.

Installing<EMAIL_ADDRESS>fixed the issue for me.

see also: https://github.com/mapbox/mapbox-gl-js/issues/7105

@ahocevar any objections to merging this one?

At this point it's 10kb vs a lot of broken apps...

Let‘s do this.


A successful but cryptic .debug()

It seems like .debug() performed some awesome black magic on a troubled model, but then, like all good magicians, didn't tell me how to do the trick. Is there something to be gleaned from this:
In [2]: sol1 = hl1.solve()
   ...:
Using solver 'cvxopt'
Solving for 242 variables.
Solving took 10.4 seconds.
---------------------------------------------------------------------------
RuntimeWarning                            Traceback (most recent call last)
<ipython-input-1-0da4b2f64ebd> in <module>()
      4 hl1 = HyperloopSystem(propulsion="podside")
      5 hl1.substitutions.update({'cruisevelocity': 210, 'minpodcapacity': 5.2})
----> 6 sol1 = hl1.solve()

/Users/philippe.kirschen/Documents/Optimization/gpkit/gpkit/constraints/prog_factories.pyc in solvefn(self, solver, verbosity, skipsweepfailures, *args, **kwargs)
     82         else:
     83             self.program, solvefn = genfunction(self, verbosity)
---> 84             result = solvefn(solver, verbosity, *args, **kwargs)
     85             solution.append(result)
     86         solution.program = self.program

/Users/philippe.kirschen/Documents/Optimization/gpkit/gpkit/constraints/gp.pyc in solve(self, solver, verbosity, warn_on_check, *args, **kwargs)
    201                 "A result dict can be generated via "
    202                 "program._compile_result(program.solver_out)." %
--> 203                 (solvername, solver_status))
    204
    205         if solver_status.lower() == "near_dual_feas":

RuntimeWarning: final status of solver 'cvxopt' was 'unknown', not 'optimal'.

The solver's result is stored in model.program.solver_out. A result dict can be generated via program._compile_result(program.solver_out).

In [3]: hl1.debug()
> Trying to solve with bounded variables and relaxed constants
Using solver 'cvxopt'
Solving for 537 variables.
Solving took 20.1 seconds.
> ...success!

> Trying to solve with relaxed constraints
Using solver 'cvxopt'
Solving for 571 variables.
Solving took 7.78 seconds.
> ...success!

I should add that debugoutput['boundedness'] is an empty dict.

@mayork Does this use your relax heuristic?

it solved with both a relaxed constants method and a relaxed variables method (what was in Boyd's paper I sent you). Since boundedness is empty you should check to see if there are any relaxed constants or constraints (not sure how to do this, if you look at post process on the SP aircraft repo it will check automatically for relaxed constants).

debug should print any relaxed variables...is this an SP?

GP. I noticed one slack variable was slightly greater than 1 just by looking at the dict  but I figured there might be a specific command for finding all of them.

There is if you use RelaxConstants manually, but debug really should be
printing that out if it's greater than 1.01

Ah gotcha. It's 1.002 so doesn't meet the threshold. Should I interpret this as meaning that the problem is primal infeasible?

I should probably change that threshold to be much smaller. Yeah, you're 2%
infeasible.
On Fri, Aug 4, 2017 at 11:45 AM, pgkirsch<EMAIL_ADDRESS>wrote:

Ah gotcha. It's 1.002 so doesn't meet the threshold. Should I interpret
this as meaning that the problem is primal infeasible?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/hoburg/gpkit/issues/1143#issuecomment-320282776, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABagGHiXsimRXbqzWnQby6fK_Zu9HIYfks5sUzyMgaJpZM4OtFHt
.

meant .2%
On Fri, Aug 4, 2017 at 11:56 AM, Edward Burnell<EMAIL_ADDRESS>wrote:

I should probably change that threshold to be much smaller. Yeah, you're
2% infeasible.
On Fri, Aug 4, 2017 at 11:45 AM, pgkirsch<EMAIL_ADDRESS>wrote:

Ah gotcha. It's 1.002 so doesn't meet the threshold. Should I interpret
this as meaning that the problem is primal infeasible?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/hoburg/gpkit/issues/1143#issuecomment-320282776, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABagGHiXsimRXbqzWnQby6fK_Zu9HIYfks5sUzyMgaJpZM4OtFHt
.

You could just expose it like the Tight tolerance?

Maybe!


Introduce maxRange property

@burakcan could you please review this PR?

@keremciu can you please check this, if you have time?

@burakcan oh okay I will check it at today


Added Kendriya Vidyalaya Namrup to the list

Kindly Add my school name to the list of schools.

@zoid-anurag Please provide us with:

the school official website URL
the school street address, including city and country
an URL of a page on the official website where the school offers an IT-related long-term (>1 year) course
a proof, which shows that the school recognizes the domain you are submitting as an official email domain for the students.

@zoid-anurag You might miss my previous comment. Please react.

lipto thanks for your response.
The url to the institute with information regarding student enrollment and courses offered are below.
namrupbvfcl.kvs.ac.in

The address for the school
KENDRIYA VIDYALAYA NAMRUP, PO PARBATPUR DISTRICT DIBRUGARH, NAMRUP , ASSAM, PIN CODE- 786623

Due to the ongoing covid situation, there might be some delay arranging for the proof for official student email domain.


Add support for column sort

Hi ! Would be fine add some option to sort column

Sorry, sorting is out of scope for this tool. You can instead use one of the programs listed in https://github.com/dbohdan/structured-text-tools#csv.


Enable publish-configure to publish to streaming

Enable publish-configure and retract-configure workflow operations to be able to publish and retract streaming elements as well. The documentation and the workflows were amended accordingly, but the default behavior is unchanged. Streaming elements will only be published if the operation is configured for it and streaming is enabled in the streaming service. Streaming elements are only retracted if the operation is configured for it. Publish configure will now return "skipped" if no elements (neither download nor streaming) were published.

If I'm understanding this correctly, this is a breaking change, right? The attributes source-flavors and source-tags don't work anymore and were replaced by download-source-flavors and download-source-tags, correct? I ran into this today when updating to Opencast 9.1. While this PR is mentioned in the release notes and changelog, it just includes the title of this PR. Further, it is listed under "features". So it was not apparent to me at all that this is a breaking change and that I have to potentially update my workflows.
Was this breakage intended or an accident? If it was intended, shouldn't it be mentioned more prominently in the release notes or the upgrade guide?

@LukasKalbertodt Yeah, you're right, this should've been in the release notes or the upgrade guide, mea culpa! Though I'm still unsure which of these would be a good spot. I guess this would've been major enough to get a section in the upgrade guide, but in general I'm still a bit fuzzy in regards to the correct workflow here. Maybe I'll bring it up in the Technical Meeting.
As for now, do you want to create a short PR to mention this change or should I?

I'm still a bit fuzzy in regards to the correct workflow here. Maybe I'll bring it up in the Technical Meeting.

I have no idea (either) when it comes to that. But yeah, communicating these breaking changes is probably pretty important for a project like Opencast. Bringing it up in the technical meeting seems like a good idea! Curious to see what comes out of it :)

As for now, do you want to create a short PR to mention this change or should I?

You know more about the context of this change, so I guess you can describe it better than I could.

@LukasKalbertodt I added a point to the upgrade docs, see #2328 :)

Thanks ^_^


Restoring 'WITHIN' when tile38 starts returns fatal error

Hi.
I have a weird problem with the latest tile38. I can create a location entry and tie it to a geofence and when i write a location the fence is triggered as expected. However if I stop and start tile38 (when using storing data persistently) I get an error regarding 'WITHIN': [FATA] invalid argument 'WITHIN'.
As the fence has been added correctly and it has been functioning, I would assume restoring it from disk would also work. However for some reason it doesn't. I've reproduced this on images tagged 1.14.0 and 1.14.3.
As a minor thing I also noticed that at least the latest tile38 docker images all have version 0.0.0 and git 0000000.

Hmm on second thought maybe this is some sort of issue with my build/provisioning scripts. Apologies.

As a side note there was an issue with loading AOF files in 1.14.0 that was fixed in 1.14.1 that sounds similar.
If you happen to run into this issue again please let me know.
Thanks


Help bring up new board based on imx8mp

Adding a SOM based on Engicam imx8mp
Current situation
We are using a SOM based on imx8mp. We have our own layer and can boot a custom yocto image on the board.
Initially, we adopted A/B update mechanism and everything went well, but the issue is with the space constraint of 8 gb emmc. Now with two partitions, each of 3.3gig, its difficult to run container-based applications.
We are looking to implement meta-updater

It is bit complicated to support a new board and requires some good level of understanding on type of kernel image, memory address for loading FIT image.
We did go ahead and tried the guide available to add our imx8mp based board.

Trial

As per the 1st point in the link, I made sota_imx8mp-icore.bbclass

KERNEL_IMAGETYPES = "fitImage"
KERNEL_CLASSES += "kernel-fitimage"
IMAGE_FSTYPES = " ostreepush garagesign garagecheck ota-ext4 ostree.tar.bz2 ota.tar.xz wic"
OSTREE_KERNEL = "fitImage-${INITRAMFS_IMAGE}-${MACHINE}-${MACHINE}"
OSTREE_KERNEL_ARGS = "console=ttymxc1,115200 ramdisk_size=2048 root=/dev/ram0 rw rootfstype=ext4 ostree_root=/dev/mmcblk1p2"

WKS_FILE = "sdimage-imx8-sota.wks.in"
IMAGE_BOOT_FILES = "imx8mp-icore_boot.scr"

As per the 2nd  point, I created a custom wks file

part u-boot --source rawcopy --sourceparams="file=imx-boot" --ondisk mmcblk --no-table --align ${IMX_BOOT_SEEK}
part /boot --source bootimg-partition --ondisk mmcblk --fstype=vfat --label boot --active --align 4096 --size 100
part / --source otaimage --ondisk mmcblk --fstype=ext4 --label root --align 4096

bootloader --ptable msdos

3)As per 3rd point, I created u-boot_2022.04.bbappend file with below content
FILESEXTRAPATHS:prepend := "${THISDIR}/${PN}:"
DEPENDS += "u-boot-mkimage-native"

do_deploy:append () {
  install -d ${DEPLOYDIR}
  install -m 0644 ${WORKDIR}/interface.bin ${DEPLOYDIR}
  install -m 0644 ${WORKDIR}/interface_release.info ${DEPLOYDIR}

    cat > ${DEPLOYDIR}/imx8mp-icore_boot.txt << EOF
load mmc 1:2 \${load_addr} /boot/loader/uEnv.txt
env import -t \${fileaddr} \${filesize}
load mmc 1:2 \${load_addr} \${kernel_image}
bootm \${load_addr}
EOF

  mkimage -A arm64 -O linux -T script -d ${DEPLOYDIR}/imx8mp-icore_boot.txt ${DEPLOYDIR}/imx8mp-icore_boot.scr
}

Generating SD card image
The SD card image is created and when I boot it, I get the below output
## Loading kernel from FIT Image at 40400000 ...
   Using 'conf-engicam_imx8mp-icore-starterkit.dtb' configuration
   Trying 'kernel-1' kernel subimage
     Description:  Linux kernel
     Created:      2024-03-11   9:31:42 UTC
     Type:         Kernel Image
     Compression:  gzip compressed
     Data Start:   0x40400108
     Data Size:    15368358 Bytes = 14.7 MiB
     Architecture: AArch64
     OS:           Linux
     Load Address: 0x40480000
     Entry Point:  0x40480000
     Hash algo:    sha256
     Hash value:   54cd2a529a9c337406ece22465b686c345b2672717b06847de5349bd97ff4193
   Verifying Hash Integrity ... sha256+ OK
## Loading ramdisk from FIT Image at 40400000 ...
   Using 'conf-engicam_imx8mp-icore-starterkit.dtb' configuration
   Trying 'ramdisk-1' ramdisk subimage
     Description:  initramfs-ostree-image
     Created:      2024-03-11   9:31:42 UTC
     Type:         RAMDisk Image
     Compression:  uncompressed
     Data Start:   0x412c56c4
     Data Size:    2293772 Bytes = 2.2 MiB
     Architecture: AArch64
     OS:           Linux
     Load Address: unavailable
     Entry Point:  unavailable
     Hash algo:    sha256
     Hash value:   3092a8aee7fd07bdd8d24a79169e530d339ce58959fcb35863bf45e8ca8c5c3a
   Verifying Hash Integrity ... sha256+ OK
## Loading fdt from FIT Image at 40400000 ...
   Using 'conf-engicam_imx8mp-icore-starterkit.dtb' configuration
   Trying 'fdt-engicam_imx8mp-icore-starterkit.dtb' fdt subimage
     Description:  Flattened Device Tree blob
     Created:      2024-03-11   9:31:42 UTC
     Type:         Flat Device Tree
     Compression:  uncompressed
     Data Start:   0x412a82d4
     Data Size:    59413 Bytes = 58 KiB
     Architecture: AArch64
     Hash algo:    sha256
     Hash value:   b90b8979e5fb095ce469b6911ef3feef1dbf13977528a6305a288f0dcdbf3830
   Verifying Hash Integrity ... sha256+ OK
   Booting using the fdt blob at 0x412a82d4
   Uncompressing Kernel Image
**Error: inflate() returned -3**
gzip compressed: uncompress error -1
Must RESET board to recover
resetting ...

I tried setting the load_addr address manually thinking that there may be an overlap of addresses somewhere. But I again get the error
u-boot=> setenv load_addr 0x60000000
u-boot=> setenv fdtaddr 0x70000000
u-boot=> load mmc 1:2 ${loadaddr} /boot/ostree/poky-43941fa7486627fa6351143a7be3783b31f6633e91943213a81c3669eddf00ec/vmlinuz-5.15.71+g67aba053e67d6

## Loading kernel from FIT Image at 60000000 ...
   Using 'conf-engicam_imx8mp-icore-starterkit.dtb' configuration
   Trying 'kernel-1' kernel subimage
     Description:  Linux kernel
     Created:      2024-03-11   9:31:42 UTC
     Type:         Kernel Image
     Compression:  gzip compressed
     Data Start:   0x60000108
     Data Size:    15368358 Bytes = 14.7 MiB
     Architecture: AArch64
     OS:           Linux
     Load Address: 0x40480000
     Entry Point:  0x40480000
     Hash algo:    sha256
     Hash value:   54cd2a529a9c337406ece22465b686c345b2672717b06847de5349bd97ff4193
   Verifying Hash Integrity ... sha256+ OK
## Loading ramdisk from FIT Image at 60000000 ...
   Using 'conf-engicam_imx8mp-icore-starterkit.dtb' configuration
   Trying 'ramdisk-1' ramdisk subimage
     Description:  initramfs-ostree-image
     Created:      2024-03-11   9:31:42 UTC
     Type:         RAMDisk Image
     Compression:  uncompressed
     Data Start:   0x60ec56c4
     Data Size:    2293772 Bytes = 2.2 MiB
     Architecture: AArch64
     OS:           Linux
     Load Address: unavailable
     Entry Point:  unavailable
     Hash algo:    sha256
     Hash value:   3092a8aee7fd07bdd8d24a79169e530d339ce58959fcb35863bf45e8ca8c5c3a
   Verifying Hash Integrity ... sha256+ OK
## Loading fdt from FIT Image at 60000000 ...
   Using 'conf-engicam_imx8mp-icore-starterkit.dtb' configuration
   Trying 'fdt-engicam_imx8mp-icore-starterkit.dtb' fdt subimage
     Description:  Flattened Device Tree blob
     Created:      2024-03-11   9:31:42 UTC
     Type:         Flat Device Tree
     Compression:  uncompressed
     Data Start:   0x60ea82d4
     Data Size:    59413 Bytes = 58 KiB
     Architecture: AArch64
     Hash algo:    sha256
     Hash value:   b90b8979e5fb095ce469b6911ef3feef1dbf13977528a6305a288f0dcdbf3830
   Verifying Hash Integrity ... sha256+ OK
   Booting using the fdt blob at 0x60ea82d4
   Uncompressing Kernel Image
**Error: inflate() returned -5**
gzip compressed: uncompress error -1
Must RESET board to recover
resetting ...

Looking forward to get some help from the community members who can understand this error and help bring this board up. Thankyou.

@pattivacek @ricardosalveti Can you guys help on this?

Sorry, I'm much too out of the loop to help here. Perhaps also @quaresmajose could help?


Add border-radius support

Changes

Added a loop to generate border-radius classes based on predefined values.
Defined variables for border-radius types and name
Updated documentation to include 'borderRadius' prop

Why

This allows developers to effortlessly apply border-radius.
Needed this feature myself, implemented it locally and than thought to myself that I'm probably not the only one and it could benefit other users.

Testing

Verified that all generated border-radius classes apply the correct styles.
Ensured that existing styles are not broken by these additions.

@Alexandre-Chapelle
Hi. Thank you for your interest and contribution to the library, it is crucial to me.
At the moment I am investigating to what extent it may be useful. During development, there were thoughts about this functionality, but I tried to stick to the idea that the library should not mutate the elements to which it is applied.
And also, will it not intersect with other use cases. It will take me some time, but I will try to solve it in the nearest time.

@Alexandre-Chapelle
@Alexandre-Chapelle
Hi, I've reviewed your contribution and merged it. I made small changes and fixed typos. Thanks again for your contribution!
I will consider expanding this feature in the future.
If you don't mind, feel free to add me on LinkedIn (it's specified in my GitHub account), I'd like to mention you in the post about your contribution.

@WOLFRIEND
Hey! Thanks for reviewing the PR. I've added you on LinkedIn.
I'd love to contribute more to this library in the future, but I have a question.
I think it would be great if the library had skeleton presets, such as:

Presets for a loading bullet list or numbered list
Presets for a loading user card
Presets for a loading image
...

Here's an example what it could look like

But as far as I understood the library aims for simplicity and lightweightness. So my question is: would adding this functionality be appropriate for this library?

@Alexandre-Chapelle
Sorry, can't find you there, could you, please, send me a direct message: https://www.linkedin.com/in/aleksandrtkachenko/
Regarding the presets, yeah, I was thinking about their possibilities, but there are a few key points why I didn't implement them:

As you mentioned, I wanted this library to be simple and lightweight as much as possible. Adding these presets probably involves adding JS, which opens up a whole new range of possibilities. I didn't want to reinvent yet another library, of which there are already quite a few.
I spent a lot of time investigating this question and studying other libraries that have similar preset functionality. And it is impossible to predict all cases. Even if a project has some "User card" that seems to look more or less similar everywhere, but in the end, they still differ from project to project. And even using a preset, it still has to be configured, and customized, so that it matches the project. But the main idea was to make as few changes as possible. And, it's way easier to adjust your component (if needed of course) and set some predefined dimensions during the loading process.


[RFC] Program Analysis Framework in Relay

Please also see #3895, which is @MarisaKirisame's RFC around a specific change to support analyses in Relay.
This RFC pertains to building a centralized, comprehensive program analysis framework in Relay. I see two primary uses of program analyses in Relay: for generating analysis data used by the compiler, to do things such as quantization, and for generating human-readable data used by developers, useful for exploring Relay programs. Whereas Marisa's request pertains more to the first use-case, this request is inspired by the second use-case, and motivated by a desire to build a framework that covers both use-cases. Such frameworks exist -- see LLVM's framework, which is designed to generate data useful to both the compiler and the developer.
I built a small analysis framework for Relay this past summer at Microsoft, useful for building human-readable analyses of Relay programs. A demo of this framework can be found here, on my branch of TVM.
These are features I developed in my simple framework:

Utilities for exporting analysis results into some more useful format (e.g. pandas)

I achieve this in my simple framework by giving utilities which: (1) extract "columns" out of the resulting analysis data and (2) convert analysis data into a record-based format which can be imported into pandas.

A consistent format for the resulting analysis data, allowing for analyses to be composed and to depend on the outputs of previous analyses.

In my framework, analysis data is simply structured into a dictionary-of-dictionaries in Python, where keys are strings representing column/column-group names.

A helper class for doing simple static dataflow analysis, built on Relay's ExprVisitor.

These are features which could be considered for a full framework:

Useful for building compiler analysis passes and analysis passes which generate human-readable data
The ability to do dynamic analysis of programs

There is some exploration of this in the demo linked above

Integration with the Pass Manager, so that dependencies between analyses can be explicit

Also so that analyses can be registered and discovered

Utilities for doing control-flow analyses
One or more "right ways" of building analyses. These methods of building analyses should be flexible, so as not to limit the power of analyses, but they should enforce a general structure to analyses so that

Analyses can compose with each other easily
Analyses are readable and maintainable, once you understand the "right ways" to build them.

It should be quick to write new analyses
Utilities for pulling data out of analyses

These are open questions that I have:

What examples of "ad-hoc" program analyses exist in Relay? #3895 lists some.
What features are needed by compiler analyses?

I'm posting this in advance of the TVM conference this year, as I'm doing a lighting talk on program analysis in Relay and am hoping that the talk generates some discussion.

Hi @gussmith23:
I just start playing with TVM this year. I'd think this is very useful to me.

I'm posting this in advance of the TVM conference this year, as I'm doing a lighting talk on program analysis in Relay and am hoping that the talk generates some discussion.

Do you keep the link? I'd like to know more details.
I am wondering if you have plan to make this upstream to TVM?
Seems this RFC didn't updated for a long time.

I assume this is no longer active.


Ensure we configure any "managed" VM

UNtile now, we didn't generate any config drive for VM that weren't
started, even though we wanted them managed.
This patch corrects the issue, and also ensure we don't rely on SSH to
configure anything on the VMs.
We just keep plain SSH accesses for OCP/CRC, since they can't rely on
cloud-init.

/trigger github-experimental

we need this for the adoption infra

/approve


Metadata on the connection

At this moment a connection (ConnectionContext) consists of a UserId only. For scenarios I have in mind, it should be possible to add some metadata or additional context to the connection at the point of creation.
var clientUri = _client.GetClientAccessUri("John",  keyvaluepair);
on the server side we then should be able to get this information by getting it from the connection context again.

Thanks for the feedback. Do you have some scenarios for such metadata, for example, can clients edit such metadata or should it be readonly to the clients?
ConnectionContext contains the headers and query strings of the client URL when the client connects. So one way is to append some query string to the generated URI so that connection. But in this way, such metadata is editable by the clients.
Another way would be for the SDK to add such metadata into claims.

At this point, i add some metadata like subprotocol and some other claim-like value. When a client connects
Right now, i do the following and put the metadata inside the "clientid". This way i can get that data out again on the server side using the ConnectionContext. But this is not a neat way to do it. So maybe some additional parameter on the GetClientAccessUri to add a dictionary<string,string> to be able to add it.
var url = _webPubSubServiceClient.GetClientAccessUri($"{metadata1}:{metadata2}:{subProtocol}").AbsoluteUri;

Yes, the feature makes total sense to me.
The concern of adding the metadata to GetClientAccessUri is that it actually sets the info inside the jwt token which then is a query parameter of the URL, there are some limitations of this approach that:

URL has a length limit
People can extract what the metadata is with the token, it might also be a concern when the server does not want to expose the metadata to the client.

Proposal
How about adding such metadata in connect event so that such metadata is just between the WebPubSub service and the server (e.g. Azure Function)?
Detail:
So for now we can set userId, subprotocol, groups and roles in connect response for a connection https://azure.github.io/azure-webpubsub/references/protocol-cloudevents#success-response-format
How about adding a metadata field there like:
{
    "groups": [],
    "userId": "",
    "roles": [],
    "subprotocol": "",
    "metadata": {
        "foo": "bar",
        "more": { }
    }
}

Later on, such metadata can be fetched from ConnectionContext.
I can see that "claim-like" metadata can still be useful, maybe we can support both ways. Comments?

Yes i agree with you that adding the metadata to the GetClientAccessUri is not clean.
Upon the "connect" event would be the perfect place. A client connects once (or a few times, depending on how stable the internet is e.g.) and the "backend" retrieves the metadata from somewhere and stores it on the ConnectionContext.
This solution would perfectly fit our use-case.
Thanks!

set state  is now available in<EMAIL_ADDRESS>Sample usage:
const handler = new WebPubSubEventHandler("chat", ["https://xxx.webpubsub.azure.com"], {
  handleConnect(req, res) {
    // You can set the state for the connection, it lasts throughout the lifetime of the connection
    res.setState("calledTime", 1);
    res.success();
  },
  handleUserEvent(req, res) {
    var calledTime = req.context.states.calledTime++;
    console.log(calledTime);
    // You can also set the state here
    res.setState("calledTime", calledTime);
    res.success();
  }
});


Service instance cannot start with too long instance name

Noticed this with a long project name running kontena app deploy: service with longer than 48 character name fails to start, so the instance name must be 50 characters or less. Creation and deployment runs fine, but the instance cannot start. I tested this also locally with Docker for Mac (client and server versions 1.12.0-rc2 and api versions 1.24) and was able to run a container with arbitrary long container name.
$ kontena version
cli: 0.14.3
master: 0.14.3

This fails:
$ kontena service create --grid dev 0xxxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxx49 kontena/lb:latest
$ kontena service deploy 0xxxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxx49
$ kontena service show 0xxxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxx49
dev/0xxxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxx49:
  status: running
  image: kontena/lb:latest
  stateful: no
  scaling: 1
  strategy: ha
  deploy_opts:
    min_health: 0.8
  dns: 0xxxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxx49.dev.kontena.local
  net: bridge
  instances:
    0xxxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxx49-1:
...
      dns: 0xxxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxx49-1.dev.kontena.local
...
      status: stopped
      reason: [8] System error: invalid argument

This works:
$ kontena service create --grid dev 0xxxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxx48 kontena/lb:latest
$ kontena service deploy 0xxxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxx48
$ kontena service show 0xxxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxx48
dev/0xxxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxx48:
  status: running
  image: kontena/lb:latest
  stateful: no
  scaling: 1
  strategy: ha
  deploy_opts:
    min_health: 0.8
  dns: 0xxxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxx48.dev.kontena.local
  net: bridge
  instances:
    0xxxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxx48-1:
...
      dns: 0xxxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxx48-1.dev.kontena.local
...
      status: running

According to RFC 1035 the length of a FQDN is limited to 255 characters, and each label (node delimited by a dot in the hostname) is limited to 63 characters, so in effect the limit you're after is 63.

The limit could be increased but not much to keep in line with the standards.
CLI should complain or refuse to deploy.

This seems to be the issue downstairs in docker: https://github.com/docker/docker/issues/21445

Following stack won't deploy due to this:
stack: matti/kontena-mongodb-single
version: 0.0.1
description: Single MongoDB instance for Kontena Master

expose: mongodb

services:
  mongodb:

okay so it seems that it's due to my extremely long grid name that makes "Domainname" to become long:
            "Hostname": "mongodb-1",
            "Domainname": "konte.lolmaster-mega-gcp-us-east1-masters.kontena.local",

Confirmed, there seems to be a maximum limit of 64 bytes on the Docker container hostname + domain, so with a grid development.kontena.local domain, the maximum length service name that still works is xxxxxxxxx10xxxxxxxx20xxxxxxxx30xxx36: xxxxxxxxx10xxxxxxxx20xxxxxxxx30xxx36-1.development.kontena.local is exactly 64 bytes. A service called xxxxxxxxx10xxxxxxxx20xxxxxxxx30xxxx37 fails to deploy, because it is 64 bytes long.
$ kontena service create xxxxxxxxx10xxxxxxxx20xxxxxxxx30xxx36 redis
 [done] Creating xxxxxxxxx10xxxxxxxx20xxxxxxxx30xxx36 service
$ kontena service deploy xxxxxxxxx10xxxxxxxx20xxxxxxxx30xxx36
 [done] Deploying service xxxxxxxxx10xxxxxxxx20xxxxxxxx30xxx36
⊛ Deployed instance development/null/xxxxxxxxx10xxxxxxxx20xxxxxxxx30xxx36-1 to node core-01
$ kontena service create xxxxxxxxx10xxxxxxxx20xxxxxxxx30xxxx37 redis
 [done] Creating xxxxxxxxx10xxxxxxxx20xxxxxxxx30xxxx37 service
$ kontena service deploy xxxxxxxxx10xxxxxxxx20xxxxxxxx30xxxx37
 [fail] Deploying service xxxxxxxxx10xxxxxxxx20xxxxxxxx30xxxx37
 [error] 500 : halting deploy of development/null/xxxxxxxxx10xxxxxxxx20xxxxxxxx30xxxx37, one or more instances failed:
	⊗ Failed to deploy instance development/null/xxxxxxxxx10xxxxxxxx20xxxxxxxx30xxxx37-1 to node core-01: GridServiceInstanceDeployer::ServiceError: Docker::Error::ServerError: invalid header field value "oci runtime error: container_linux.go:247: starting container process caused \"process_linux.go:359: container init caused \\\"invalid argument\\\"\"\n"

The resulting error from Docker is not very pretty.

The stack name is also included in the limitation on the total DNS name length:
stack: test/test-asdfasdfasdfasdf
services:
  xxxxxxxx10xx12:
    image: redis

  xxxxxxxx10xxx13:
    image: redis
    depends_on:
      - xxxxxxxx10xx12

 [done] Creating stack test-asdfasdfasdfasdf
 [done] Triggering deployment of stack test-asdfasdfasdfasdf
 [done] Waiting for deployment to start
 [done] Deploying service xxxxxxxx10xx12
 [fail] Deploying service xxxxxxxx10xxx13
Deployment of service development/test-asdfasdfasdfasdf/xxxxxxxx10xxx13 failed:
  - halting deploy of development/test-asdfasdfasdfasdf/xxxxxxxx10xxx13, one or more instances failed
  - GridServiceInstanceDeployer::ServiceError: Docker::Error::ServerError: invalid header field value "oci runtime error: container_linux.go:247: starting container process caused \"process_linux.go:359: container init caused \\\"invalid argument\\\"\"\n" (on node core-01)

This seems to be the issue downstairs in docker: docker/docker#21445

That issue is about {"Config": {"Hostname": "..."}} longer than 63 chars... this seems to be about $hostname.$domain being limited to 64 chars, even though the plain hostname itself is well below the 63-char limit.

Fundamentally this is happening because docker-runc is calling sethostname with the complete container FQDN, even when specifying a plain Hostname with a separate Domainname. This fails with EINVALID if the FQDN hostname is longer than HOST_NAME_MAX, which is 64 on Linux.
Very little we can do about this without breaking the DNS search domains... possibly docker/runc would need to be fixed to only use the plain Hostname for sethostname.
container.json
{
        "Image": "redis:latest",
        "Hostname": "xxxxxxxxx10xxxxxxxx20xxxxxxxx30xxx36-1",
        "Domainname": "development2.kontena.local"
}

Created using curl --unix-socket /var/run/docker.sock -H "Content-Type: application/json" -X POST http:/v1.22/containers/create -d @container.json => a447c7661138a
docker inspect -f '{{.Config.Hostname}}' a447c7661138a
xxxxxxxxx10xxxxxxxx20xxxxxxxx30xxx36-1

docker inspect -f '{{.Config.Domainname}}' a447c7661138a
development2.kontena.local

curl --unix-socket /var/run/docker.sock -H "Content-Type: application/json" -X POST http:/v1.22/containers/a447c7661138a764da71a0ce7389e72afba1ef8f02f1bb373bf149595ce31e38/start
oci runtime error: container_linux.go:247: starting container process caused "process_linux.go:359: container init caused \"invalid argument\""

strace -s 512 -f -p $(pidof containerd)
14666 sethostname("xxxxxxxxx10xxxxxxxx20xxxxxxxx30xxx36-1.development2.kontena.local", 65) = -1 EINVAL (Invalid argument)

How about warning user when grid name exceeds X? Maybe same logic for stack install etc.
Atleast kontena could detect that container name is too long and tell about it / refuse to start deploy?

On 29 May 2017, at 15.24, Tero Marttila<EMAIL_ADDRESS>wrote:
Fundamentally this is happening because docker-runc is calling sethostname with the complete container FQDN, even when specifying a plain Hostname with a separate Domainname. This fails with EINVALID if the FQDN hostname is longer than HOST_NAME_MAX, which is 64 on Linux.
Very little we can do about this without breaking the DNS search domains... possibly docker/runc would need to be fixed to only use the plain Hostname for sethostname.
container.json
{
"Image": "redis:latest",
"Hostname": "xxxxxxxxx10xxxxxxxx20xxxxxxxx30xxx36-1",
"Domainname": "development2.kontena.local"
}
Created using curl --unix-socket /var/run/docker.sock -H "Content-Type: application/json" -X POST http:/v1.22/containers/create -d @container.json => a447c7661138a
docker inspect -f '{{.Config.Hostname}}' a447c7661138a
xxxxxxxxx10xxxxxxxx20xxxxxxxx30xxx36-1
docker inspect -f '{{.Config.Domainname}}' a447c7661138a
development2.kontena.local
curl --unix-socket /var/run/docker.sock -H "Content-Type: application/json" -X POST http:/v1.22/containers/a447c7661138a764da71a0ce7389e72afba1ef8f02f1bb373bf149595ce31e38/start
oci runtime error: container_linux.go:247: starting container process caused "process_linux.go:359: container init caused "invalid argument""
strace -s 512 -f -p $(pidof containerd)
14666 sethostname("xxxxxxxxx10xxxxxxxx20xxxxxxxx30xxx36-1.development2.kontena.local", 65) = -1 EINVAL (Invalid argument)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Atleast kontena could detect that container name is too long and tell about it / refuse to start deploy?

Yes, that's what #2376 does, it raises a validation error on the service create/update before deploying.

How about warning user when grid name exceeds X? Maybe same logic for stack install etc.

Perhaps... #2376 adds a note in the documentation that grid/stack names should be kept reasonably short. Dunno what the warning threshold would be.
@jnummelin  perhaps consider #2376 for 1.3.0?

Atleast kontena could detect that container name is too long and tell about it / refuse to start deploy?

Yes, that's what #2376 does, it raises a validation error on the service create/update before deploying.

How about warning user when grid name exceeds X? Maybe same logic for stack install etc.

Perhaps... #2376 adds a note in the documentation that grid/stack names should be kept reasonably short. Dunno what the warning threshold would be.
@jnummelin  perhaps consider #2376 for 1.3.0?

hit this again. named services with "func-run-UUID-UUID-UUID-UUID" and the resulting name was too long..

@SpComb what if we just pass hostname (without domainname) to docker engine?

@SpComb what if we just pass hostname (without domainname) to docker engine?

The concept of the Linux system domainname is very vauge, it's difficult to say offhand exactly what kind of effects that change would have... initial guess is that it could work to retain the current beavhior, assuming the DNS search domain is such that the plain hostname + DNS search domain resolves to an IP address that has a reverse-dns mapping with the correct domain - which should be the case with Weave DNS :)


Initial version of the /asns API

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/346/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/304/


Using APSI in other C++ project

Hi, dear authors, I have read the README.md, but I didn't find that how to use APSI in other c++ projects. Would you please provide some demo?

Hello, have you find the way to use APSI for other C++ projects?  Looking forward to your reply.


[UOD-1171] Adding abi block number as part of schema versioning

Hi Danilo,
I think this file can be remove from this PR: testdata/eosio.nft.ft:1.abi

@romain-gilles-ultra true, done!


fix: Table columns on account show

Fixes the account show table to correctly show all columns (previously, nonce was missing):
Ater:

Before:

We should also look into making these tables "safer" (eg, throw if number of columns and values do not match)

I know this is a pretty small thing - but it should probably have gone into the next branch.


Proposal|Question: Use JumpList instead of Tray/Notification Area Icon?

We are currently using the Tray/Notification Area Icon as a place to interact with the apps settings or to terminate it.
The Tray/Notification Area has been there since the initial stages of Windows OS and were a great way for background apps to interact with users without any additional windows opening.
But they are now considered as obsolete or old tech and UWP apps are already using different APIs to compete with the tray icon (such as JumpList, live tiles and toast notifications & etc.)
Since by plan we are eventually moving to MSIX, it will be an opportunity for us to do the same "Modern methods" that UWP apps do.
For context :

Current method using tray icon for hosting the menu

MS Edge Dev's context menu containing jump list tasks for opening new windows
This issue is not only a proposal but a question for users about what they think. And to travel the path which they favour.
Also the Tray/Notification Area won't be visible in Tablet mode. So the proposed method will be a modern and viable alternative.
There are still some issues surrounding this topic :
Proposal: Have WinUI Desktop support the UWP Jumplist API
Proposal: System tray icon for WinUI 3 Desktop (Win32 and .NET Core)

Hey @ADeltaX, @Samuel12321, @Cyberdroid1 and others (if there are) any opinions?

If the notification tray icon would be removed, jump lists would be cool. Just that we must inform the user that to access settings, one must right-click on the app icon and select settings to open it.
If the notification tray icon stays, better to keep the context menu for it.

Should we keep both methods?

I personally have mixed thoughts about this, on one hand it is a familiar and expected app interaction method, but i am also all for using the most modern methods.
The migration to MSIX is the best time to do it , however it is probably is the lowest priority

keeping both methods might be best, but enhance the context menu and allow the tray icon method to be disabled (default enabled)

Initially, I think we can, for a couple of releases. Let people get accustomed to it, and then maybe remove the tray icon (after proper information). But, is it possible that the app would run in background even after removing the tray icon?

If the notification tray icon stays, better to keep the context menu for it.

agreed

The tray icon doesn't affect the app running, it's just a way to tell the users whether the app is running or not and let them interact without opening additional windows.

I read those proposals given above. I don't think the system tray would be removed in the near future. Still, I think we should remove the tray icon. And probably fix the start on boot for store version of app. That would be great.

I read those proposals given above. I don't think the system tray would be removed in the near future. Still, I think we should remove the tray icon.

i still think both methods might be best, but enhance the context menu and allow the tray icon method to be disabled (default enabled)

And probably fix the start on boot for store version of app. That would be great.

already working on it for 0.4

@Cyberdroid1

If the notification tray icon stays, better to keep the context menu for it.

There will be no reason to keep the tray icon without the menu, it's the only reason to have it.
@Samuel12321

enhance the context menu

Can you elaborate?

Thank you all for feedback. Both JumpList and TrayIcon now work.

Can the Tray Icon be hided with a setting in v0.4 ?

The tray icon is a must that shouldn't be taken away. While it is easy to implement an option to hide it, it shouldn't be. I wanted to provide an alternative approach incase the tray goes away.

Hm, ok. Thanks for telling.

Thanks for feedback! Try v0.4.0 once it's out


Are there CSV versions of the feature vectors?

E.g. similar to https://github.com/anthony-wang/CrabNet/blob/master/data/element_properties/mat2vec.csv
https://github.com/anthony-wang/CrabNet/issues/29

@sgbaird FYI, I've updated the CSV file, located at https://github.com/lantunes/skipatom/blob/main/data/skipatom_20201009_induced.csv, to fix a problem introduced when I created the file initially. You may want to update your version of this file.

@lantunes thanks! Got that added


Cannot load larger CodeLlama models

System Info
Using image ghcr.io/huggingface/text-generation-inference:latest with Id: sha256:e8c9985b0bbe3a4e745e3492cd5f4d71a2672f8afa41d1fb0ebab5233c6bc29b
Information

[x] Docker
[ ] The CLI directly

Tasks

[x] An officially supported command
[ ] My own modifications

Reproduction
I am able to use text-generation-inference to load the CodeLlama-7b-hf model. However, when using the CodeLlama-13b-hf or CodeLlama-34b-hf I see the following error:
2023-08-24T21:08:24.228883Z ERROR download: text_generation_launcher: Download encountered an error: Traceback (most recent call last):

  File "/opt/conda/bin/text-generation-server", line 8, in <module>
    sys.exit(app())
  File "/opt/conda/lib/python3.9/site-packages/text_generation_server/cli.py", line 192, in download_weights
    utils.convert_files(local_pt_files, local_st_files, discard_names)
  File "/opt/conda/lib/python3.9/site-packages/text_generation_server/utils/convert.py", line 106, in convert_files
    convert_file(pt_file, sf_file, discard_names)
  File "/opt/conda/lib/python3.9/site-packages/text_generation_server/utils/convert.py", line 68, in convert_file
    to_removes = _remove_duplicate_names(loaded, discard_names=discard_names)
  File "/opt/conda/lib/python3.9/site-packages/text_generation_server/utils/convert.py", line 32, in _remove_duplicate_names
    raise RuntimeError(

RuntimeError: Error while trying to find names to remove to save state dict, but found no suitable name to keep for saving amongst: {'model.norm.weight'}. None is covering the entire storage.Refusing to save/load the model since you could be storing much more memory than needed. Please refer to https://huggingface.co/docs/safetensors/torch_shared_tensors for more information. Or open an issue.

Expected behavior
Expect the server to load the model properly.

@Narsil since you recently changed something related to CodeLlama.

Issue seems to be the validation phase on model.norm.weight tensor has some weird properties when calling _is_complete under _remove_duplicate_names
>>> from safetensors.torch import save_file, load_file, _find_shared_tensors, _is_complete, storage_ptr, storage_size
>>> tensor = state_dict['model.norm.weight']
>>> tensor.data_ptr()
139976225415232
>>> storage_ptr(tensor)
139976094343232
>>> tensor.nelement() * _SIZE[tensor.dtype] == storage_size(tensor)
False
>>> tensor.nelement() * _SIZE[tensor.dtype]
16384
>>> storage_size(tensor)
262160384
>>> tensor.dtype
torch.bfloat16
>>> tensor.nelement()
8192
>>> tensor.untyped_storage().nbytes()
262160384

For one the storage size is bit weird on this tensor (way larger than ) listed

A current workaround is simply convert the last shard yourself.
I have to download the entire repo, and run the last safetensor conversion myself
from safetensors.torch import save_file
save_file(state_dict, "path to checkpoint")

Thanks for the report, we're looking into it, might be an issue with the original checkpoint here.

For what it's worth it works for me now

Yes the checkpoints were fixed. Thanks for the report and the ping. Closing now.

Hey all, I am hitting the same problem with PygmalionAI/pygmalion-6b and PygmalionAI/pygmalion-2.7b, when running the following command:
docker run \
  --gpus all \
  --shm-size 1g \
  -e HF_HUB_ENABLE_HF_TRANSFER=False \
  -e HUGGING_FACE_HUB_TOKEN=$token \
  -p 8080:80 \
  -v $volume:/data ghcr.io/huggingface/text-generation-inference:1.0.1 \
  --model-id $model \
  --dtype=float16 \
  --disable-custom-kernels

see trace here:
....  WARN text_generation_launcher: No safetensors weights found for model PygmalionAI/pygmalion-6b at revision None. Converting PyTorch weights to safetensors.

Error: DownloadError
Downloading (…)l-00002-of-00002.bin: 100%|██████████| 5.94G/5.94G [01:17<00:00, 76.3MB/s]d an error:
Downloading (…)lve/main/config.json: 100%|██████████| 975/975 [00:00<00:00, 387kB/s]
Traceback (most recent call last):

  File "/opt/conda/bin/text-generation-server", line 8, in <module>
    sys.exit(app())

  File "/opt/conda/lib/python3.9/site-packages/text_generation_server/cli.py", line 192, in download_weights
    utils.convert_files(local_pt_files, local_st_files, discard_names)

  File "/opt/conda/lib/python3.9/site-packages/text_generation_server/utils/convert.py", line 106, in convert_files
    convert_file(pt_file, sf_file, discard_names)

  File "/opt/conda/lib/python3.9/site-packages/text_generation_server/utils/convert.py", line 68, in convert_file
    to_removes = _remove_duplicate_names(loaded, discard_names=discard_names)

  File "/opt/conda/lib/python3.9/site-packages/text_generation_server/utils/convert.py", line 32, in _remove_duplicate_names
    raise RuntimeError(

RuntimeError: Error while trying to find names to remove to save state dict, but found no suitable name to keep for saving amongst: {'transformer.wte.weight'}. None is covering the entire storage.Refusing to save/load the model since you could be storing much more memory than needed. Please refer to https://huggingface.co/docs/safetensors/torch_shared_tensors for more information. Or open an issue.

However, it does work properly with PygmalionAI/pygmalion-1.3b which supports SafeTensors. Any recommendation @Narsil ?

Try using 1.0.3 . Those odd checkpoints are usually generated by deepspeed which messes around with storage (which indeed regularly leads to unnecessary storage usage on disk).
1.0.3 upgrade to safetensors==0.3.3 which takes care of it (by looking more deeply into storage + tensor mess to ignore the unnecessary storage).

@Narsil getting the same error with 1.0.3. Any guidance on how to fix the checkpoints?

Simplest I recommend would be using transformers:
from transformers import pipeline
pipe = pipeline(model="PygmalionAI/pygmalion-6b')
pipe.save_pretrained(safe_serialization=True)

If that doesn't work you can always nuke everything
weights = torch.load("xx")
weights = weights = {k: v.clone().contiguous() for k, v in weights.items()}
save_file(weights, "new.safetensors")

This might lead to extra storage with unwanted tensors possibly (some tensors could end up being duplicates).

I'll look into that thanks 🤓

Hey @Narsil as you predicted it lead to tensor duplicates (the checkpoints size increased by almost a factor 2) 😥


vim9script: Can't get "items" key of quickfix list from ":def" function

Describe the bug
Trying to get the items key of a quickfix list from inside a :def function raises E715.
To Reproduce
Run this shell command:
vim -Nu NONE -S <(cat <<'EOF'
    def Func()
        helpg grail
        let qfl = getqflist({'items': 0})
        let items = qfl.items
    enddef
    call Func()
EOF
)

It raises E715:
Error detected while processing function Func:
line    3:
E715: Dictionary required

Expected behavior
No error is raised, and items contains the items of the quickfix list populated by :helpg grail.
Environment

Vim version: 8.2 Included patches: 1-1079
OS: Ubuntu 16.04.6 LTS
Terminal: XTerm(356)

Additional context
I think this is a bug because the error comes from this line:
let items = qfl.items

Which suggests that qfl is not a dictionary.  But it is a dictionary:
vim -Nu NONE -S <(cat <<'EOF'
    def Func()
        helpg grail
        let qfl = getqflist({'items': 0})
        echom type(qfl) == v:t_dict
    "   ^-------------------------^
    enddef
    call Func()
EOF
)

(1 of 1): You found it, Arthur!^I^I^I^I*holy-grail* *:smile*
v:true
^----^

Besides, the same function works as expected when defined with :fu instead of :def.

Finally, the same code works as expected if I replace getqflist({'items': 0}) with its literal dictionary evaluation:
vim -Nu NONE -S <(cat <<'EOF'
    def Func()
        let qfl = {'id': 1, 'items': [{'lnum': 37557, 'bufnr': 2, 'col': 7, 'pattern': '', 'valid': 1, 'vcol': 0, 'nr': 0, 'type': '', 'module': '', 'text': '|holy-grail|'}, {'lnum': 1124, 'bufnr': 3, 'col': 32, 'pattern': '', 'valid': 1, 'vcol': 0, 'nr': 0, 'type': '', 'module': '', 'text': 'You found it, Arthur!				*holy-grail* *:smile*'}]}
        let items = qfl.items
    enddef
    call Func()
EOF
)

The return types of getqflist() (and getloclist()) probably need to be changed to any, since the return type of the function is list<dict<any>> when called without arguments, but when called with an argument, the return type should be dict<any>.'
https://github.com/vim/vim/blob/6378b21d6dd38cc0f80aa6d31d747db6c287483b/src/evalfunc.c#L597
You can get a clearer error message when you explicitly specify the type of the variable. For example:
    def Test_works()
        let qfl: list<dict<any>> = getqflist()
    enddef

    def Test_fail()
        let qfl: dict<any> = getqflist({'items': 0})
    enddef
    defcompile

The second function will print the following error:
E1013: type mismatch, expected dict<any> but got list<dict<any>>

@lacygoill Wait why did you close it?
@brammool Isn't this a bug?
The return type of getqflist({'items': 0}) is definitively not list<dict<any>>. It should be dict<list<any>>. But on the other hand getqflist({'title': 1}) returns dict<string>. So it depends on the arguments passed to getqflist().

Oh, I thought you meant there was a mistake in my code, sorry.

fixed by f151ad1c70825a91afb112e611db5c712e2656ef


fix: fail if superfluous packages are excluded

[ ] Have you followed the guidelines in our Contributing document?
[ ] Have you checked to ensure there aren't other open Pull Requests for the same change?
[ ] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[ ] Have you successfully run brew style with your changes locally?
[ ] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

So the thing I'm trying to fix is:

you add a package and depend on the six formula so you add it to the exclude list
upstream removes the dependency on six in a new release
everything keeps depending on six since currently we have no way to know if the excludes list has superfluous entries.


node-node-1  | waiting for geth to be ready

node-geth-1  | INFO [01-26|02:54:59.936] Starting geth on an OP network...        network=base-mainnet
node-geth-1  | INFO [01-26|02:54:59.936] Bumping default cache on mainnet         provided=1024 updated=4096
node-geth-1  | INFO [01-26|02:54:59.936] Enabling metrics collection
node-geth-1  | INFO [01-26|02:54:59.936] Enabling stand-alone metrics HTTP endpoint address=<IP_ADDRESS>:6060
node-geth-1  | INFO [01-26|02:54:59.936] Starting metrics server                  addr=http://<IP_ADDRESS>:6060/debug/metrics
node-geth-1  | INFO [01-26|02:54:59.937] Maximum peer count                       ETH=100 LES=0 total=100
node-geth-1  | INFO [01-26|02:54:59.938] Smartcard socket not found, disabling    err="stat /run/pcscd/pcscd.comm: no such file or directory"
node-geth-1  | INFO [01-26|02:54:59.946] Enabling recording of key preimages since archive mode is used
node-geth-1  | WARN [01-26|02:54:59.946] Disabled transaction unindexing for archive node
node-geth-1  | INFO [01-26|02:54:59.946] Set global gas cap                       cap=50,000,000
node-geth-1  | INFO [01-26|02:55:00.099] Initializing the KZG library             backend=gokzg
node-geth-1  | INFO [01-26|02:55:00.136] Allocated trie memory caches             clean=1.20GiB dirty=0.00B
node-geth-1  | INFO [01-26|02:55:00.136] Using pebble as the backing database
node-geth-1  | INFO [01-26|02:55:00.136] Allocated cache and file handles         database=/data/geth/chaindata cache=2.00GiB handles=524,288
node-geth-1  | INFO [01-26|02:55:00.160] Opened ancient database                  database=/data/geth/chaindata/ancient/chain readonly=false
node-geth-1  | INFO [01-26|02:55:00.163] State scheme set to already existing     scheme=hash
node-geth-1  | INFO [01-26|02:55:00.246]
node-geth-1  | INFO [01-26|02:55:00.246] ---------------------------------------------------------------------------------------------------------------------------------------------------------
node-geth-1  | INFO [01-26|02:55:00.246] Chain ID:  8453 (Base)
node-geth-1  | INFO [01-26|02:55:00.246] Consensus: Optimism
node-geth-1  | INFO [01-26|02:55:00.246]
node-geth-1  | INFO [01-26|02:55:00.246] Pre-Merge hard forks (block based):
node-geth-1  | INFO [01-26|02:55:00.246]  - Homestead:                   #0        (https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/homestead.md)
node-geth-1  | INFO [01-26|02:55:00.246]  - Tangerine Whistle (EIP 150): #0        (https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/tangerine-whistle.md)
node-geth-1  | INFO [01-26|02:55:00.246]  - Spurious Dragon/1 (EIP 155): #0        (https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/spurious-dragon.md)
node-geth-1  | INFO [01-26|02:55:00.246]  - Spurious Dragon/2 (EIP 158): #0        (https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/spurious-dragon.md)
node-geth-1  | INFO [01-26|02:55:00.246]  - Byzantium:                   #0        (https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/byzantium.md)
node-geth-1  | INFO [01-26|02:55:00.246]  - Constantinople:              #0        (https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/constantinople.md)
node-geth-1  | INFO [01-26|02:55:00.246]  - Petersburg:                  #0        (https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/petersburg.md)
node-geth-1  | INFO [01-26|02:55:00.246]  - Istanbul:                    #0        (https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/istanbul.md)
node-geth-1  | INFO [01-26|02:55:00.246]  - Muir Glacier:                #0        (https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/muir-glacier.md)
node-geth-1  | INFO [01-26|02:55:00.246]  - Berlin:                      #0        (https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/berlin.md)
node-geth-1  | INFO [01-26|02:55:00.246]  - London:                      #0        (https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/london.md)
node-geth-1  | INFO [01-26|02:55:00.246]  - Arrow Glacier:               #0        (https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/arrow-glacier.md)
node-geth-1  | INFO [01-26|02:55:00.246]  - Gray Glacier:                #0        (https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/gray-glacier.md)
node-geth-1  | INFO [01-26|02:55:00.246]
node-geth-1  | INFO [01-26|02:55:00.246] Merge configured:
node-geth-1  | INFO [01-26|02:55:00.246]  - Hard-fork specification:    https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/paris.md
node-geth-1  | INFO [01-26|02:55:00.246]  - Network known to be merged: true
node-geth-1  | INFO [01-26|02:55:00.246]  - Total terminal difficulty:  0
node-geth-1  | INFO [01-26|02:55:00.246]  - Merge netsplit block:       #0
node-geth-1  | INFO [01-26|02:55:00.246]
node-geth-1  | INFO [01-26|02:55:00.246] Post-Merge hard forks (timestamp based):
node-geth-1  | INFO [01-26|02:55:00.246]  - Regolith:                    @0
node-geth-1  | INFO [01-26|02:55:00.246]
node-geth-1  | INFO [01-26|02:55:00.246] ---------------------------------------------------------------------------------------------------------------------------------------------------------
node-geth-1  | INFO [01-26|02:55:00.246]
node-geth-1  | INFO [01-26|02:55:00.246] Loaded most recent local block           number=0 hash=f712aa..6c73dd td=0 age=7mo2w1d
node-geth-1  | INFO [01-26|02:55:00.247] Initialising Ethereum protocol           network=8453         dbversion=8
node-geth-1  | INFO [01-26|02:55:00.247] Initialized transaction indexer          limit=0
node-geth-1  | INFO [01-26|02:55:00.247] Loaded local transaction journal         transactions=0 dropped=0
node-geth-1  | INFO [01-26|02:55:00.247] Regenerated local transaction journal    transactions=0 accounts=0
node-geth-1  | INFO [01-26|02:55:00.277] Chain post-merge, sync via beacon client
node-geth-1  | INFO [01-26|02:55:00.277] Gasprice oracle is ignoring threshold set threshold=2
node-geth-1  | WARN [01-26|02:55:00.279] Engine API enabled                       protocol=eth
node-geth-1  | INFO [01-26|02:55:00.279] Starting peer-to-peer node               instance=Geth/v1.101304.1-stable-ed8e9f54/linux-amd64/go1.20.12
node-geth-1  | INFO [01-26|02:55:00.300] New local node record                    seq=1,706,237,098,675 id=13797d9ff0beb51d ip= udp=0 tcp=30303
node-geth-1  | INFO [01-26|02:55:00.301] Started P2P networking                   self=enode://416b7b8bb3ab5941f91d7af94c6ee60df3131d9411bc9bc251c9753e535d77f79685e5633707ea3faff0c2587c72477af866ab7b29e2ae27400c5cc3fd5187c7
node-geth-1  | INFO [01-26|02:55:00.301] IPC endpoint opened                      url=/data/geth.ipc
node-geth-1  | INFO [01-26|02:55:00.302] Loaded JWT secret file                   path=/tmp/engine-auth-jwt crc32=0x890e18e0
node-geth-1  | INFO [01-26|02:55:00.303] HTTP server started                      endpoint=[::]:8545 auth=false prefix= cors=* vhosts=*
node-geth-1  | INFO [01-26|02:55:00.303] WebSocket enabled                        url=ws://[::]:8546
node-geth-1  | INFO [01-26|02:55:00.303] WebSocket enabled                        url=ws://[::]:8551
node-geth-1  | INFO [01-26|02:55:00.303] HTTP server started                      endpoint=[::]:8551 auth=true  prefix= cors=localhost vhosts=*
node-node-1  | waiting for geth to be ready
node-node-1  | waiting for geth to be ready
node-node-1  | waiting for geth to be ready
node-node-1  | waiting for geth to be ready
node-node-1  | waiting for geth to be ready
node-node-1  | waiting for geth to be ready
node-node-1  | waiting for geth to be ready
node-node-1  | waiting for geth to be ready
node-node-1  | waiting for geth to be ready

how to deal with it. thx

@BoogalooLi
Hello, what are you using for the L1 RPC?

@BoogalooLi
Hello, what are you using for the L1 RPC?

my own L1 node, a full node of eth

waiting for geth to be ready

@BoogalooLi @Adewagold
Please come to the Base Discord and open a #developer-support ticket so we can take a closer look at your docker-compose.yml configurations and also take a closer look at the environments you both are running your nodes in. 👍


Machine learning

Gradient Descent from scratch issue #2957  (re submit)
issue #2957
Please review my ipynb files, and let me know the changes I have to make, I am feeling some issues of images, as its not showing after adding in the Assets folder. This is a fresh PR from Machine_Learning branch (forked) to Machine_Learning branch of main repo.

Domain of Contribution 📊
Machine Learning issue #2957  ML_2_20_Implement_Gradient_Descent_without_using_any_standard_ML_library_like scikit-learn_or_more_(D).ipynb

PR approved :tada: @Anindyadeep


Volto's form validation is severely limited

The form validation is hardcoded. The only way to add new validators in a form is either by declaring a new widget or type and patching widgetValidation.

For form validation we can use one of the popular 3rd party libraries and if that sounds good then I world like to work on this issue. Please assign it to me.

Hey @tiberiuichim can you explain the issue in some detail ?

The form validation is hardcoded. The only way to add new validators in a form is either by declaring a new widget or type and patching widgetValidation.

In an on-going non-Volto project, we are using react-jsonschema-form to render and validate forms, and it works pretty well. We took the idea of rendering JSONSchema based forms from Volto.
I know that Volto renders the forms using custom widgets, but perhaps using a library like this, can bring validators 'for free'.
I know that modifying Volto to use a library like this is a larger project than adding proper validator support, and may be even unachievable, but it may be interesting.

I just discussed with @sneridagh and one possible (even if limited) solution would be to move widgetValidation to the configuration registry and allow people to register new validations (if needed).


[Feature]: Automatic Resources Deletion

Describe the feature
VAB doesn’t have a way to track the resources installed, this way if a resource is removed from the VAB configurations it doesn’t get actually removed from the cluster in the next vab apply command. It would be useful whether VAB could keep track of resources managed, in order to keep them in sync with the modules.
Code of Conduct

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

Thanks of the suggestions, we will work on it


Mail for Contributor not received for GSSoC'24

Discussed in https://github.com/GSSoC24/Contributor/discussions/5

I already filled contributors form on 1st may. But did not received email for contributor.
<EMAIL_ADDRESS>Name:Anushka Mokashi

check your email for a response to see if you have been selected. If you have not received a response, it is possible that you were not selected.

Thank you for considering my issue. I am recieving other GSSOC emails of
newsletter. But not contributor's email.
Kindly refer screenshot below.
On Fri, 10 May 2024, 12:16 pm Dhyanesh Siddhartha, @.***>
wrote:

check your email for a response to see if you have been selected. If you
have not received a response, it is possible that you were not selected.
—
Reply to this email directly, view it on GitHub
https://github.com/GSSoC24/Contributor/issues/38#issuecomment-2103975490,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AYAZRTNBLYOISIA7SYTOXPTZBRUMXAVCNFSM6AAAAABHQASOZCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBTHE3TKNBZGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

You can do one thing in gmail search for "GSsOC" then see cause it may happen email sent in spam!

Yes I chechked, no mail regarding the contributor's selection is there.

You can check your mail box, after applying it will take some time to get a mail.

The emails are still being rolled out. Just so you know, you may receive it soon. @AnushkaJMokashi

@AnushkaJMokashi  You can contact the organizer though .

Recieved the contributor's mail about selection. Thank you so much for considering my issue and your support.

Mail for contributor received. Thank you all of you for your time and consideration.


Fixed Websocket problem with latest Firefox versions

The latest Firefox versions (>=37) are using permessage compression.
The current implementation of permessage compression in websocket-sharp
is incorrect because it creates a new DeflateStream object for every
message, but this is only allowed, if client_no_context_takeover or
server_no_context_takeover has been agreed during the handshake.
Otherwise the DeflateStream object would need to be persisted and reused
for each connection, in order to implement the LZ77 sliding window.
I tried to copy over some stuff from websocket-sharp, to include
client_no_context_takeover and server_no_context_takeover, but that does
not have any effect on the Firefox behaviour. According to the spec, the
server may just acknowledge the extensions requested by the client, but
may not add options (like client_no_context_takeover). As a consequence,
this didn't solve the problem.
The final solution would of course be to change the code to reuse the
DeflateStream objects, but it hasn't even been done in webbsocket-sharp.
Instead websocket-sharp has introduced an IgnoreExtensions property
which effectively disables lines 163-165 in WebSocket.cs. I have
commented these out in our code as a quick fix. As a result permessage
compression is simply disabled.
This change finally made Emby-Websockets on Firefox clients work again!

Excellent, thanks! Really glad to see this one fixed.

Some further reading:
https://bugzilla.mozilla.org/show_bug.cgi?id=1176176
https://www.igvita.com/2013/11/27/configuring-and-optimizing-websocket-compression/
https://github.com/sta/websocket-sharp/issues/132
https://github.com/sta/websocket-sharp/issues/140

Wow, that was a quick merge :-)
PS: Closes #1194

Actually this also closed MediaBrowser/Emby/#1193


Fixes a bug where a promise was unhandled.

Fixes #10.
Rather than intermixing callbacks and promises, this opts to just use promises all the way through.
Giant caveat: This means that the query passed in to the constructor must support promises.  I personally think this is the right/sane thing to do, but if you want to continue to support callbacks you will need to solve this bug in a different way (e.g., swallow the promise result of query[queryMethod](...)).
ethjs-contract
Thank you for contributing! Please take a moment to review our contributing guidelines
to make the process easy and effective for everyone involved.
Please open an issue before embarking on any significant pull request, especially those that
add a new library or change existing tests, otherwise you risk spending a lot of time working
on something that might not end up being merged into the project.
Before opening a pull request, please ensure:

[ ] You have followed our contributing guidelines
[ ] Pull request has tests (we are going for 100% coverage!)
[x] Code is well-commented, linted and follows project conventions
[x] Documentation is updated (if necessary)
[x] Internal code generators and templates are updated (if necessary)
[x] Description explains the issue/use-case resolved and auto-closes related issues

Be kind to code reviewers, please try to keep pull requests as small and focused as possible :)
IMPORTANT: By submitting a patch, you agree to allow the project
owners to license your work under the terms of the MIT License.

I just realized the code I wrote is a modification to the compiled output, not the original source.  Recommend closing this PR and having someone who actually has the project checked out locally applying the fix.

Okay, this should not happen, how exactly are errors getting swallowed though? I might want to implement a try/catch in the meantime if that is the case. @MicahZoltu

Not sure if it helps, but I am getting an UnhandledPromiseRejectionWarning everytime something fails with rpc @SilentCicero
node-server_1  | (node:28) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: [ethjs-rpc]  error with payload {"id":2575583708953,"jsonrpc":"2.0","params":[{"to":"0xA97fEfe489ca62ADD4949360DCE30e3351F6881B","data":"0x8eaa6ac01201cf23b4c1d237a7c146584a8e540995f700cf38525cf627cc3407eac17416"},"latest"],"method":"eth_call"} Error: [ethjs-provider-http] Invalid JSON RPC response from provider
node-server_1  |     host: https://rinkeby.infura.io/ywCD9mvUruQeYcZcyghk
node-server_1  |     response:  ""
node-server_1  |     responseURL: undefined
node-server_1  |     status: 0
node-server_1  |     statusText:
node-server_1  |
node-server_1  | (node:28) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

So I just updated the rpc with new code that exposes the rpc errors. Perhaps this is triggering the error here. Can you show more code as to what is triggering this?
Sent from my iPhone

On Dec 5, 2017, at 2:15 PM, William Chong<EMAIL_ADDRESS>wrote:
Not sure if it helps, but I am getting an UnhandledPromiseRejectionWarning everytime something fails with rpc @SilentCicero
node-server_1  | (node:28) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: [ethjs-rpc]  error with payload {"id":2575583708953,"jsonrpc":"2.0","params":[{"to":"0xA97fEfe489ca62ADD4949360DCE30e3351F6881B","data":"0x8eaa6ac01201cf23b4c1d237a7c146584a8e540995f700cf38525cf627cc3407eac17416"},"latest"],"method":"eth_call"} Error: [ethjs-provider-http] Invalid JSON RPC response from provider
node-server_1  |     host: https://rinkeby.infura.io/ywCD9mvUruQeYcZcyghk
node-server_1  |     response:  ""
node-server_1  |     responseURL: undefined
node-server_1  |     status: 0
node-server_1  |     statusText:
node-server_1  |
node-server_1  | (node:28) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Just a simple get() of a smart contract deployed in rinkeby
https://github.com/likecoin/likecoin-poc/blob/master/server.js#L155
It fails randomly but I was never able to debug it, due to the error message being empty like above

What version of ethjs are you using? Try the latest npm version. I believe 0.3.1
Sent from my iPhone

On Dec 5, 2017, at 5:19 PM, William Chong<EMAIL_ADDRESS>wrote:
Just a simple get() of a smart contract deployed in rinkeby
https://github.com/likecoin/likecoin-poc/blob/master/server.js#L155
It fails randomly but I was never able to debug it, due to the error message being empty like above
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@williamchong007 Upgrade to the latest version of ethjs-query/ethjs-rpc.  It resolves the null error message issue, allowing you to actually debug your code.  :)
@SilentCicero I don't use ethjs-contract anymore, but the problem still occurs with ethjs-query and I believe it has the same root cause.  To reproduce the problem, cause the JSON-RPC return a JSON-RPC error when calling await this.connector.ethjsQuery.estimateGas(transaction);.  This should result in the rejected promise turning into a node exception here due to the await call which can then be wrapped in a try/catch.  However, instead what happens is node screams about an unhandled promise rejection.  This is because (I believe) that a promise is being generated by one of the lower level libraries but a callback is being used to detect the error instead of the promise.
The fundamental issue here is that if you instantiate a Promise in node, you must hookup a .catch to it OR await it.  Throughout the ethjs codebase there is a weird mix of promises + callbacks.  If someone uses callbacks to monitor for failure, they will not hookup a .catch to the Promise which means they'll get an unhandled promise rejection error from node.  I strongly recommend removing support for callbacks and just using promises.  If someone really wants, they can create a wrapper that turns the promise into a callback, but in a way that appropriately sets up the .then and .catch.  I believe there are even libraries that do this automatically for you.

I dived into my docker-compose container and checked the ethjs version,
and above UnhandledPromiseRejectionWarning still happen @0.3.1
Interestingly it does not seems to happen at all when I deploy the same container onto production k8s

Interesting! I'll look into dropping callbacks. I think that makes a lot of sense now that async await is taking off.
Sent from my iPhone

On Dec 6, 2017, at 7:13 AM, William Chong<EMAIL_ADDRESS>wrote:
I dived into my docker-compose container and checked the ethjs version,
and above UnhandledPromiseRejectionWarning still happen @0.3.1
Interestingly it does not seems to happen at all when I deploy the same container onto production k8s
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

I don't know if this is a good workaround, but I commented out "reject(callbackError)" from line 8350 and then I could catch the exception without having any problem with unhandled exception.
if (callbackError) {
    //reject(callbackError);
    protoCallback(callbackError, null);

I'll look into this solution. I may just remove callback support altogether as Mike suggested.
Sent from my iPhone

On Dec 22, 2017, at 6:29 PM, Chi-Hao Poon<EMAIL_ADDRESS>wrote:
I don't know if this is a good workaround, but I commented out "reject(callbackError)" from line 8350 and then I could catch the exception without having any problem with unhandled exception.
if (callbackError) {
//reject(callbackError);
protoCallback(callbackError, null);
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

this was resolved! 😸


Common issues expansion

Including a singular override has a syntax landmine due to list ambiguity.  It's
also a very likely issue and including the recipe will undoubtedly help people
get unstuck faster.
The toml issue has a worse issue in #149 than the one the README mentions.
Bad rust toolchain was encounted recently, and this is a frequent mistake of
vendoring via niv add blah/repo
closes #167

Superseded by #171

Superseded by #171


License

Thanks for creating this library, it looks nice and simple to use 👍
I notice the mix.exs file says the license is MIT, but I don't see a LICENSE file in the repo.
Could you add one just to clarify.
Thanks again!

Thanks for the heads up @mbuhot. Missing LICENSE has been added. Will be available in the next hex release.


Good job. Very well documented

What is the next step once we have complete control over the Windows registries?

I would've loved to add more documentation, yet I've been quite busy as of late.
What you want to do with the Windows registry is all up-to you, as long as it is not in a malicious manor. There are a couple solutions, such as changing programs to have unquoted service paths, changing policies, subverting administrative restrictions, bypassing group policies, and much more.
Happy Pentesting!


chore: add more linters, address findings

:zap: Summary

Add some more useful linters, address their findings.
:ballot_box_with_check: Checklist

[x] Check locally
[ ] Add tests
[ ] Add documentation

Nice findings! Thank you!


Renamed some functions from utils

What does this PR do?
It renames some functions from utils.
Where should the reviewer start?
It just renames few functions from utils, and replaces their name with new ones throughout the project.
How should this be manually tested?
It shouldn't cause build errors when this package and https://github.com/segmentio/analytics-ios are using together.
Any background context you want to provide?
It's impossible to use PostHog library together with Segment library on iOS. It happens because PostHog iOS package is based on Segment package, and they have duplicating function names which is causing failing of app build.
What are the relevant tickets?
https://github.com/PostHog/posthog-react-native/issues/2
Screenshots or screencasts (if UI/UX change)
Questions:

Does the docs need an update?
Are there any security concerns?
Do we need to update engineering / success?

Thanks @serhey-dev for this! Apologies for the wait, yet 1.2.3 is now out with the change. I'll update the RN repo next.