Added new Go resources

Ordered the new resources into alphabetical order

Hey @Jetlum , blog posts and tutorials are not really books. Thanks anyway!

Yeah,but you added Go by example and I thought except books we're adding
and tutorials and blog posts
On Thu, Nov 3, 2016, 23:12 victor felder<EMAIL_ADDRESS>wrote:

Closed #2150 https://github.com/vhf/free-programming-books/pull/2150.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/vhf/free-programming-books/pull/2150#event-847159648,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMnPbxtx5rGWGVQPT_7x2NOH4HTnfY0Tks5q6lwygaJpZM4KnIjO
.

To me, Go by example is closer to a book. It consists of snippets thoroughly explained. It's neither a blog post nor a tutorial. I don't have extremely strict rules, but I'm not sure rather short blog posts tutorials helping to create a specific thing don't really qualify here.

Okay thank you for the answer and from now on will add only books.
On Thu, Nov 3, 2016 at 11:22 PM, victor felder<EMAIL_ADDRESS>wrote:

To me, Go by example is closer to a book. It consists of snippets
thoroughly explained. It's neither a blog post nor a tutorial. I don't have
extremely strict rules, but I'm not sure rather short blog posts tutorials
helping to create a specific thing don't really qualify here.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/vhf/free-programming-books/pull/2150#issuecomment-258291270,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMnPb-FAiw6OyMc2hDX_o6UbIjgXcIITks5q6l6PgaJpZM4KnIjO
.


Add a way to ignore or filter pageerrors being emitted by PuppeteerEnvironment

🚀 Feature Proposal
Add a way to filter what browser errors should be emit or not as 'uncaughtException', or at least a way to disable from jest-puppeteer from emitting those errors.
Motivation
Not all errors aren't cause by tests (in an ideal world, those errors should be fixed), but sadly a lot of websites use ads, 3rd party libraries etc, that can cause page errors and since PuppeteerEnvironment doesn't offer a way to disable or filter those errors, can cause a lot of "false" positives failed tests.
Example
Please provide an example for how this feature would be used.
Most obvious way, would be used by setting a flag to disable it in jest-puppeteer.config.js
Pitch
Why does this feature belong in the Jest Puppeteer ecosystem?
Since the feature of catching those errors and throwing is added by Jest Puppeteer library, a way to filter or disable I think should belong to Jest Puppeteer ecosystem. If not developers would be forced to fork it, to be able to use it.
https://github.com/smooth-code/jest-puppeteer/blob/master/packages/jest-environment-puppeteer/src/PuppeteerEnvironment.js#L7-L9

Ignore this issue, looks like there is exitOnPageError, I didn't found it in docs at all, that can be added to the jest-puppeteer.config.js, and it works as expected.


[TextServer / Font] Add support for customizable baseline offset.

Fixes https://github.com/godotengine/godot/issues/87655
https://github.com/godotengine/godot/assets/7645683/598ec12a-abca-41c2-8f79-e6b5dc45a637

very nice

Thanks!


WIP: Commercial support

Starting PR on documenting commercial support processes via Zendesk

Closing this as there is much detail on our website: https://about.mattermost.com/support/.


Issues in the grpc-secured-unary sample

Pack - Tools build on 18/04/2018
Oracle JDK - "1.8.0_161"
Windows 7
Description:
The following error is thrown when running the sample
ballerina: initiating service(s) in 'grpc-secured-unary.bal'
error: error, message: method name should be prefixed with service name and separated with '/'. Expected service name: 'HelloWorld'. Actual fully qualifed method name: 'HelloWorld\hello'.
        at ballerina.grpc:register(<native>)

Also, mention the steps to run the sample and expected output in the sample description

This is working now. Please reopen if it is failing yet.


Translate tutorials/stateless-application/guestbook/ into Japanese

This is a Feature Request
What would you like to be added
Translate tutorials/stateless-application/guestbook/ into Japanese.
Why is this needed
This page has not been translated.
Comments
/language ja
/assign

/close


Compatible with an other Garmin sensor

Hello,
I tested your app with an other version of Garmin sensor. It's the sensor cadence/speed together.
With this your app is functional.

I have an other sensor to test. I'll keep you informed.

Thanks for testing that!

From ANT official website I can only find this one made by Garmin, could be the same one you tested:
https://www.thisisant.com/directory/gsc-10-speed-cadence-bike-sensor

I tested the GSC-10 with my Samsung S9. Unfortunately it either registers the speed or the cadence... not both. I'll see if I can debug it and issue a pull request.
I also tested this with a Garmin Vivoactive 4 watch set to broadcast a heart rate. It works.

Thanks @ecammit !

Pull request #8

Pull request #8 has been merged. Closing.

Pull request #8 has been merged. Closing.


gomobile bind: Allow go-elements to be built for Android and iOS targets

This commit allows to build go-elements packages as a single standalone library to be imported in iOS and Android targets using gomobile bind
To do so some cosmetic change is needed to make it work, most importantly we have Only a subset of Go types wich are currently supported and return variables should be at maximum 2 where the second shoudl alwasy be the error
The only breaking change has been for the slip77 where DeriveKey now it returns a struct KeyPair instead of two variables.
I see this as an acceptable tradeoff overall, instead of creating dedicated slip77 gomobile binding.

Unfortunately is not that easy, gomobile seems to not bind the entire library (ie. Payment, Pset etc..)
I think the best way is to creata a more high level library that uses go-elements and expose only the supported go types for gomobile Moving to github.com/vulpemventures/ionio


Do not rely on x64 and arm64 artifacts being uploaded.

Signed-off-by: dblock<EMAIL_ADDRESS>Description
Set global environment variables for the location of the build output, then use in the docker stage.
Issues Resolved
Closes  https://github.com/opensearch-project/opensearch-build/issues/1183
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #1196 (030af1a) into main (e79709f) will decrease coverage by 0.19%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main    #1196      +/-   ##
============================================
- Coverage     93.77%   93.58%   -0.20%
  Complexity       10       10
============================================
  Files           105      105
  Lines          2618     2618
  Branches          9        9
============================================
- Hits           2455     2450       -5
- Misses          153      158       +5
  Partials         10       10

Impacted Files
Coverage Δ

tests/jenkins/jobs/IncrementalBuild_Jenkinsfile
100.00% <ø> (ø)

tests/jenkins/jobs/Vars_Jenkinsfile
100.00% <ø> (ø)

src/system/temporary_directory.py
82.75% <0.00%> (-13.80%)
:arrow_down:

src/system/os.py
92.30% <0.00%> (-7.70%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e79709f...030af1a. Read the comment docs.


Add Formality lexer

Fixes #1242
Ported from https://bitbucket.org/birkenfeld/pygments-main/pull-requests/836

In the next few days, I'll update my PR and fix these build errors. Thanks!

@birkenfeld - I'm doing some PR necromancy here. It looks like the "formality" language itself is dead. The original link in this PR redirects to the Kind language project. I found this repository which contains a copy of formality, which hasn't been updated in 5 years and is marked "experimental".
As per our own guidelines, "formality" doesn't meet the bar for a PR (there's no community around it), but I don't know the relationship to "Kind" and whether it's feasible to convert the lexer for that. A cursory glance indicates they have diverged. If you do think this should make it back, please feel free to reopen.


Mining-Overlay on walls after mining

It sometimes gets stuck in the non-wall version. Not gud

Seemingly only on the highest


Add New Metric Types and explanatory SQL snippets

🚀 Deployed on https://65e9580c53244baa154ff3b6--cozy-fox-0defec.netlify.app


⚠ Bofrost.at has degraded performance

In 03c9dc6, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1236 ms

Resolved: Bofrost.at performance has improved in 1a55cb4 after 14 minutes.


Add support keyword-only attributes on Plugins

Description
Added support for keyword-only attributes on plugins.
closes #5706
Self Check:

[x] Attached issue to pull request
[x] Changelog entry
[x] Type annotations are present
[x] Code is clear and sufficiently documented
[x] No (preventable) type errors (check using make mypy or make mypy-diff)
[x] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
[x] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )
[ ] If this PR fixes a race condition in the test suite, also push the fix to the relevant stable branche(s) (see test-fixes for more info)

Processing this pull request

Merged into branches master, iso6 in e9df85ff06d92eaf4c4c1f5c014ac6bfbdfaa1af


Scheduled Posts never publish

Issue Summary

Our content editor has scheduled posts for April 1st and April 5th, and neither one were published, and are still sitting in the scheduled queue.
The only modification i have done to ghost is to inject a script that will redirect frontend ghost url's to our external webapp for viewing the blog. all admin and api routes still accessible,nginx config is not changed.
To Reproduce

Setup ghost
Schedule post
wait for the scheduled date to pass
observe the scheduled post did not publish.

Any other info e.g. Why do you consider this to be a bug? What did you expect to happen instead?
It's obviously a bug when an advertised feature does not work as expected
Technical details:

Ghost Version: 2.14.0
Node Version: 10.15.3
Browser/OS: Ubuntu 18.04.2
Database: MariaDB 10.1.38

Hi @r3wt if this is an exact problem observed in https://github.com/TryGhost/Ghost/issues/8485, would recommend adding the details about your case there. Closing this issue as a duplicate :upside_down_face:
If you could please provide in the original issue answers to these questions: https://github.com/TryGhost/Ghost/issues/8485#issuecomment-303797404 and  https://github.com/TryGhost/Ghost/issues/8485#issuecomment-304062693
Thanks!

@gargol the original issue was never solved, that's why i opened a new issue. very frustrating that you would close my issue without even investigating the other thread first. please reopen my issue and give it the proper respect it deserves.

@r3wt no disrespect meant here. Just trying to keep things grouped up as they belong together. Would rather reopen original issue with updated information so that whole context is kept in one place. Cheers!


When writing default config files, first check if they exist before writing

Description:
Added a check for each default config file to see if they exist before potentially overwriting
Related issue (if applicable): fixes #23153
Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.

I would like to change when we generate default config to when both configuraion.yaml and .HA_VERSION are not exist.
Bottom line, if any of those files exist, we should raise error, not silent accept it.

I would like to change the condition we generate default config to when both configuraion.yaml and .HA_VERSION are not exist.
Bottom line, if any of those files exist, we should raise error, not silent accept it.
EDIT: .HA_VERSION will always exist

Overwriting version I agree with, that one should be taken out because it's irrelevant. I'm not sure why it should raise an error if the other files exist. Maybe just log the fact that they were not created.
Are you saying raise an error instead of accept because if the other files are present and configuration.yaml is not then something is fishy and needs to be reviewed by the user before continuing?

When we enter the code to create default config, we was assuming that is for new installation. If there are files exists, something wrong happened, we should abort the process. So I still think we should check file existing outside the create_default_config method.

I agree, we should abort. We won't know how our default config will work with the existing files that we reference.

Fair point. That is beyond my knowledge of how HA handles errors, so I'll close this PR


Model Reconstruction Service enhancements

In this release, planned enhancements to the metabolic modeling service revolve around extending the modeling and simulation framework to include transcription data. We will enable users to predict flux based on gene expression profiles derived from RNA-Seq data. We will also enable users to use RNA-Seq data to add additional reactions to the model, permitting reactions with highly expressed genes to function.

10/14: Ron check with Chris

Per Chris, going to be Dec 4.

12/2: Chris is confident I can get the backend for this done. My main concern is the front end. (probably won't make it)

02/24: Per Chris, probably will not make it for March.

I think we can drop this from the wish list for now. Closing the ticket.


Restrict Controls to the size of the page

Problem
If you want a Column to be scrollable, it is currently not sufficient to set scroll=ft.ScrollMode.ALWAYS. You must also set a fixed height to the Column, either as an explicit number (which is often a bad idea) or something more dynamic like the page's height.
However then one needs to listen to changes on the page size and manually propagate those. Also, if the Column is nested deep inside other controls, the height may need to be that of an arbitrary parent. How would that currently be done?
Example
import flet as ft

def main(page: ft.Page):
    page.add(
        ft.Column(
            scroll=ft.ScrollMode.ALWAYS,
            height=page.height,
            controls=[
                ft.ListTile(
                    title=ft.Text(value=str(i)),
                )
                for i in range(20)
            ],
        ),
    )

ft.app(target=main)

This snippet only shows a scrollbar, when this line is included: height=page.height.
Now imagine, the Column was somewhere deep inside the application or maybe there is an AppBar. How would I handle the Column height to make only the visible height scrollable?
Suggested solution
Restrict children of the page to the size of the page.
If I set an explicit height to a control, then it's children are already restricted to that height. Why is this behavior not applied to the size of a page?

I'm noticing that the page behavior of not restricting child heights is consistent with Column itself. I would think that the Column's tight property would help, but it doesn't.

The expand property seems to do what I am looking for.
Example:
import flet as ft

def main(page: ft.Page):
    page.appbar = ft.AppBar(title=ft.Text("Some text"))
    page.add(
        ft.Container(
            expand=True,
            content=ft.Column(
                scroll=ft.ScrollMode.ALWAYS,
                expand=True,
                controls=[
                    ft.ListTile(
                        title=ft.Text(value=str(i)),
                    )
                    for i in range(20)
                ],
            ),
        ),
    )

ft.app(target=main)

I need to set it on each control (see the Container between the page and the Column). Is there a better way?


Handle updates to cost data automatically

Whenever there is a new release of https://github.com/pypsa/technology-data we should update the ariadne-data/costs/{mean,optimist,pessimist} files. Ideally that would happen automatically in the snakemake workflow, but creating the files requires executing the technology-data workflow with different configurations for the data uncertainty.
I just wasted an hour trying to find out why a new key was not present in the cost data, just to realize that retrieve_costs is disabled in pypsa-ariadne.
We should have at least a helpful error message that checks if the version in ariadne-data is up to date with the version specified in default-config.
To automate updating the ariadne-data/costs we could add a CI.
For each new release of technology-data, a runner is started, executes the technology data workflow with the required configs, and places the output in ariadne-data.
Maybe this is something @lkstrp could tackle?

We are going to add the optimistic and pessimistic cost assumptions to the output folder of technology-data.
This way we can download the data just like the mean cost horizon and don't have to worry about submodules etc.
Once the data is online, I will create a rule to take care of this.

Technology-data is going to be a package. Once that's done I will write a rule to put together the cost data.
Until then, I manually upload the missing two cost horizons.


Use the controller runtime client

The general-purpose client is currently initialised using the OpenShift Cluster DNS operator, probably accidentally. This initialises it using the controller runtime directly, dropping the Cluster DNS dependency.
Signed-off-by: Stephen Kitt<EMAIL_ADDRESS>

We have this dependency going all the way back to at least 0.12; this should be backported to 0.14, 0.13 and 0.12 to reduce our dependency tree and resulting exposure to security alerts.

K8s 1.17 job is failing consistently: ERROR: failed to create cluster: failed to init node with kubeadm....  Perhaps we should make it non-required for now so we don't bock PRs....

K8s 1.17 job is failing consistently: ERROR: failed to create cluster: failed to init node with kubeadm.... Perhaps we should make it non-required for now so we don't bock PRs....

Yes, we lost the ability to work with 1.17 at some point :-/.

@vthapar @aswinsuryan one of the service-discovery tests are failing. Is this some known issue which is found to be flaky or do you want to take a look?
[Fail] [discovery] Test Headless Service Discovery Across Clusters when the number of active pods backing a service changes [It] should resolve the local pod IPs
github.com/submariner-io/shipyard@v0.14.0-m2.0.20221121173616-41b20b7d46e1/test/e2e/framework/framework.go:562


Is variable_types really optional?

@sebbacon observed the following in this Slack message.
From README.md:

The generate_report action outputs one HTML document with a graph for each variable specified. Where graphs have a category of 5 or less, small number suppression is applied and the whole graph is redacted.

Later on, however, variable_types is described as optional. How should one specify a variable without also specifying its type? Is variable_types really optional?

Based on briefly 👀 cohortreport/report.py, I think:

If variable_types isn't supplied, then tables and graphs are created for all columns in the input file
If variable_types is supplied, then its values are used to apply column types, irrespective of the input file type
If variable_types is supplied, then an AssertionError is raised when its keys don't match the columns in the input file

https://github.com/opensafely-actions/cohort-report/blob/715b7b8419fa964156e488078b1ffb97f57e9f1b/cohortreport/report.py#L64-L90

OK, so this sounds like reasonable behaviour as implemented, but there's a missing config step for just specifying a subset of columns without types. Perhaps a separate key variables, which is a list?

Either that, or a type code/value that represents the existing type. An example of the former would be "DEFAULT"; of the latter would be null.

Yes. If we did that we should consider renaming the config key itself to something like variables


Add consumer group to logging output

While troubleshooting problematic consumers (for example, that return malformed event data or are lagging behind), it would be helpful to know which particular consumer a record fails on. With the current log structure, we only receive the partition/offset of a record, but the same record can be dispatched to many different consumers.
Proposed Changes

:broom: Add consumer group as a key to logs in the RecordDispatcher

Release Note
Log output from the record dispatcher now contains the consumer group as a key for better tracing of a record.

Sorry about that, my STS is bugging out and thought I could get this visually 😅

Seems like there is a linting issue from the control plane? Is that something I should be concerned with?

@jhill072 thanks for the PR! :heart_eyes_cat:

/retest-required

/cc @matzew

@jhill072 do you have a CLA? https://github.com/knative-sandbox/eventing-kafka-broker/pull/1999#issuecomment-1223618988

/retest

Again... namespaced ... /cc @aliok
timed out waiting for the condition

/test reconciler-tests-namespaced-broker_eventing-kafka-broker_main

/test all

I think Tide (https://prow.knative.dev/tide) is messed up :(
This PR seems to be the first item in the merge pool for the past 2 days. And other PRs can't be merged before this one.
I am gonna put a hold on this to see what happens.

/hold

Ok, hold didn't work. Gonna close and reopen to see what happens.

/close

/reopen

/unhold

/retest

I've reworked the logging part to include the context (consumer group, resource name, resource namespace, etc) in every log statement, let us know if that addresses your issue.


viewmodel not destroy in recomposition state

Hello,
I hope this message finds you well.
I'm currently using Voyager version 1.1.0-beta02 along with Koin for dependency injection. Following the sample provided, I’m defining ViewModels within my composable screens as shown below:
val vm = koinScreenModel()
However, I've encountered an issue where, during each recomposition of the composable screen, everything gets destroyed except for the ViewModel. While this behavior might be useful for temporarily sharing a ViewModel content between two composable screens, it causes significant challenges in other scenarios. Unfortunately, this issue persists across previous versions as well.
I would greatly appreciate it if you could address this issue or provide guidance on how to resolve it in my project.
Thank you so much for your help.

As far as I know (Im rather new in kotlin/compose), the idea behind viewmodel is to survive recomposition. That should be the intented behavior

I found that, if you not specify unique key for screen
override val key: ScreenKey = uniqueScreenKey

koinScreenModel() every time return the same view model, unique parameter of parametersOf doesn't guaranty that.
I think, need to update documentation to clarify that sample


small suggest that can improve the I/O efficiency for the function write_chains_to_file in emcee.py

Hey there!
I am using your super useful Emcee wrapper! Thanks a lot for developing such an amazing tool.
I noticed that the current Emcee core is taking a lot of time when writing the chains to file, with the function
def write_chains_to_file(self, sample):
    chain_file = self.checkpoint_info.chain_file
    temp_chain_file = chain_file + '.temp'
    if os.path.isfile(chain_file):
        copyfile(chain_file, temp_chain_file)
    if self.prerelease:
        points = np.hstack([sample.coords, sample.blobs])
    else:
        points = np.hstack([sample[0], np.array(sample[3])])
    with open(temp_chain_file, "a") as ff:
        for ii, point in enumerate(points):
            ff.write(self.checkpoint_info.chain_template.format(ii, *point))
    shutil.move(temp_chain_file, chain_file)

However, after some slight modifications, I found I could cut the entire running time for a 5000-step sampling chain writing time by almost 60%. The modified version is as follows. I am not entirely sure if the suggestion will break anything. So far, I have tested and found no issue. It essentially reduces one copy time and also concatenates in a slightly different manner.
def write_chains_to_file(self, sample):
    chain_file = self.checkpoint_info.chain_file
    temp_chain_file = chain_file + '.temp'

    if self.prerelease:
        points = np.hstack([sample.coords, sample.blobs])
    else:
        points = np.hstack([sample[0], np.array(sample[3])])

    data_to_write = "\n".join(self.checkpoint_info.chain_template.format(ii, *point) for ii, point in enumerate(points))

    with open(temp_chain_file, "w") as ff:
        ff.write(data_to_write)

    with open(temp_chain_file, 'rb') as ftemp, open(chain_file, 'ab') as fchain:
        shutil.copyfileobj(ftemp, fchain)

    os.remove(temp_chain_file)

Not sure if this helps, but in my case (5000 steps), I reduced about one minute.

Here is the running time collected by SnakeViz:

Original version:

After modification:

Hey there! In order to avoid this issue getting lost, I added a PR for this change.

Can I ask if there is any updates? Any possibility of public contribution to this project?

Hi @yangcht, you can open an issue on the main git.ligo.org/lscsoft/bilby development repo by emailing it to<EMAIL_ADDRESS>I think you can attach your patch (https://patch-diff.githubusercontent.com/raw/lscsoft/bilby/pull/29.patch) to the email.

Thanks @mattpitkin! I am then closing the issue since it has been patched.


Guess value for thermodynamicstate.X

Reported by filip.jorissen on 10 Jun 2014 16:55 UTC
I have a model where 'X[2]' of a moist air was chosen by Dymola as the iteration variable of a nonlinear system of equations. The default guess value is 0, which causes an error:
The following error was detected at time: 0

Model error - power: (r1) ** (n[1]) = (-3.83338) ** (-1.5)

The stack of functions is:
Buildings.Media.PerfectGases.MoistAir.sublimationPressureIce
Buildings.Media.PerfectGases.MoistAir.saturationPressure
Buildings.Media.GasesPTDecoupled.MoistAir.T_phX
Buildings.Media.GasesPTDecoupled.MoistAir.T_phX(menergaAdsolair.heating.state_a1_inflow.p, menergaAdsolair.filter.port_b.h_outflow, menergaAdsolair.filter.port_b.Xi_outflow)
First evaluation failed for non-linear solver.

etc etc

ERROR: Failed to solve non-linear system using Newton solver.
To get more information: Turn on Simulation/Setup/Debug/Nonlinear solver diagnostics/Details
Solution to systems of equations not found at time = 0
   Nonlinear system of equations number = 15
   Failed to evaluate any residual. Try to give better start-values.
   Iteration is not making good progress.
   Accumulated number of residue calculations: 4
   Last values of solution vector:
menergaAdsolair.heating.state_a1_inflow.X[2] = 1E-09
menergaAdsolair.thermostatic3WayValve.k = 0.5
menergaAdsolair.filter.port_b.h_outflow = 45301
Error: could not solve simplified initialization for homotopy method.
Error: could not solve simplified initialization for homotopy method.
Error: Failed to start model.

I solved this by setting the initial guess value for ThermodynamicState.X equal to reference_X. I suggest to implement this by default in MSL and possibly also for p, T and h.
The hotfix for my own package was:
redeclare record extends ThermodynamicState(X(start=reference_X))
  "ThermodynamicState record for moist air"
end ThermodynamicState;

Migrated-From: https://trac.modelica.org/Modelica/ticket/1509

Comment by hubertus on 10 Jun 2014 17:55 UTC
Thanks for the report, this is actually the intention of the variable reference_X. I am not sure whether it shoudl be set int the library though: the problem is that the mere existence of a value for the start attribute influences a number of algorithms (e.g. state selection, afaik at least in some tools), so that there can be unintended consequences from adding it. I'll think a bit about this and might introduce your fix.
For that matter: it would probably be nicer if setting start values would have no other effects than exactly setting a start value. In that case, the fix shoudl of course be applied

Comment by fcasella on 31 Aug 2015 11:24 UTC
I got a similar request on Stackoverflow (http://stackoverflow.com/questions/31644258/fluidport-connector-with-start-values-for-composition) which suggests adding reference_X as a default start value for connector variables.
In fact, a better choice would be to add start = reference_X to MassFraction type definition of the medium, which would cover all the cases at once.
I am also unsure that this might trigger negative consequences on existing models. Maybe it would be worth trying on the existing testuites. What do you think?

Comment by hubertus on 12 Dec 2015 22:53 UTC
Francesco, your ideas does not work because the mass fraction type is not a vector. It maybe should be and should be used, but that would not be an allowed change for a minor version number update.

Comment by hubertus on 12 Dec 2015 23:03 UTC
Fixed in trunk in 67ba73b85115cf06cc6707d83b8dd1c55253335a

Changelog modified by hubertus on 12 Dec 2015 23:03 UTC
Fixes missing start value for composition vector in ThermodynamicState

Modified by beutlich on 13 Dec 2015 08:26 UTC

Changelog modified by beutlich on 13 Dec 2015 08:26 UTC
Fixed missing start value for composition vector in ThermodynamicState

Comment by fcasella on 14 Dec 2015 13:55 UTC
Replying to [comment:3 hubertus]:

Francesco, your ideas does not work because the mass fraction type is not a vector. It maybe should be and should be used, but that would not be an allowed change for a minor version number update.

You're right, I overlooked this.


The best open-source facial animation model I've ever used

Great job! And solute the open source spirit of your team!
I tried many hours today on this and it really impressed me. Here are some results Hallo generated.
https://github.com/fudan-generative-vision/hallo/assets/172945862/fbe66aad-5598-4cee-ad85-3f66df154d31
https://github.com/fudan-generative-vision/hallo/assets/172945862/ab4f63bd-57cf-4979-9a13-302ec40919b5
https://github.com/fudan-generative-vision/hallo/assets/172945862/99bda8aa-0feb-4c2c-9781-65c1bc28c4f6

Thanks! Have fun with it!

What are your settings/hardware specs ?


⚠ ClamAV has degraded performance

In a720f2c, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 288 ms

Resolved: ClamAV performance has improved in 29ed559 after 20 minutes.


Telegram as SMS provider

Discussed in https://github.com/casdoor/casdoor/discussions/1378

Originally posted by Vladimir-Va December  7, 2022
Hello Casdoor team.
Is possible add Telegram provider for send message for telegram bot?
I think that when implementing this request it will be very helpful.
By @Vladimir-Va
We can consider integrating: https://github.com/nikoksr/notify to support a lot of message types like Telegram

I'm working on this.


footer upgrade

Purpose

The purpose of this PR is to fix #240 #239
Goals
To upgrade footer to new design
remove unwanted code

I think i created a branch accidentally. can any1 remove?


CORE-4865 Move membership libs and components to use Clock instead of Instant

CORE-4865 Move membership libs and components to use Clock instead of Instant
https://r3-cev.atlassian.net/browse/CORE-4865
Files that still use Instant

RegistrationRequestProgressDto
RegistrationRequestProgress
MemberInfoExtension

There's also a build failure at the moment.


SQL autocommit issue during startup of v4.1.1

hi all,
I'm trying to setup an instance of germinate v4.1.1 and mysql using dockers (following docker-compose instructions provided).
But when I start germinate in the docker, I take an error (mysqld starts ok):
germinate | 26-Oct-2020 09:34:43.054 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.5.57
germinate | 26-Oct-2020 09:34:43.160 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR Deploying web application archive [/usr/local/tomcat/webapps/ROOT.war]
germinate | java.sql.SQLNonTransientConnectionException: Can''t call rollback when autocommit=true
germinate | 	at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:110)
germinate | 	at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:97)
germinate | 	at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:89)
germinate | 	at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:63)
germinate | 	at com.mysql.cj.jdbc.ConnectionImpl.rollback(ConnectionImpl.java:1851)
so an idea should be to pass autocommit=false in config.properties, in some manner (or to launch mysqld with a similar option).
may you please tell me if you are able to reproduce this situation, and how to fix it?
thanks a lot for your patience,
with best regards.
/gp

Thanks for reporting this. It's something that we are aware of and it's nothing to be concerned about. It can safely be ignored.
Is everything else working as expected?

hi,
thanks for the quick reply, but I don't know how to expect, other errors occur - I've attached here the output
germieLog_20201026.log
BTW, is there a test URL to check the setup is ok?
Thanks again, best regards
/gp

That'll depend on your Docker setup. It'll be running at root level in the container you've set up using the port you chose.
It looks like the URL of Gatekeeper isn't set correctly, or, if you're not planning to use Gatekeeper, you have to set the property. authentication.mode to none.

indeed, no Gatekeeper planned usage. In my config.properties I set
...
#authentication.mode = <either 'SELECTIVE', 'FULL' or 'NONE'>
authentication.mode = NONE
same result.
May you be so kind to post a working (except of usernames/passwords, of course) test config.properties?
TIA
/gp

Try specifically setting the following:
gatekeeper.url=
gatekeeper.username=

I'll fix this in the next release.
Here's a working config.properties from our production server, albeit with Gatekeeper:
database.username = <USERNAME>
database.password = <PASSWORD>
database.server  = <SERVER>
database.name    = <DATABASE>
database.port    =

germinate.client.url=https://ics.hutton.ac.uk/germinate-demo/

gatekeeper.url=https://ics.hutton.ac.uk/germinate-gatekeeper-4/api
gatekeeper.username=<GK USERNAME>
gatekeeper.password=<GK PASSWORD>
gatekeeper.registration.enabled=true
gatekeeper.registration.requires.approval=true

color.primary=
colors.charts=#00a0f1,#5ec418,#910080,#222183,#ff7c00,#c5e000,#c83831,#ff007a,#fff600
dashboard.categories=

data.directory.external=/data/germinate

data.import.mode=VERIFY

brapi.enabled=true

authentication.mode=SELECTIVE
gdpr.notification.enabled=true

comments.enabled=true
google.analytics.key=

files.delete.after.hours.async=12
files.delete.after.hours.temp=12

hidden.pages=

HURRAH - blanking
gatekeeper.url=
gatekeeper.username=
it works.
Now at http://localhost:9080 it shows a "Germinate Template Database" page.
I suppose we can close this issue. Thanks a lot for your patience and support.
/gp

No problem at all, thanks for getting in touch and I'll incorporate the things you had issues with into the documentation and code for the next release!


Unable get rid of web component warning

Version
3.0.0-beta.15
Reproduction link
https://github.com/blacksonic/vue-3-playground
Steps to reproduce

Create a webcomponent with the name x-username
Modify the app instance config to test for webcomponents
Include the webcomponent in a vue template
Config of the application
app.config.isCustomElement = tag => /^x-/.test(tag);

What is expected?
The application shouldn't log warning as it is configured to treat the element as a webcomponent
What is actually happening?
Vue logs warning:
[Vue warn]: Failed to resolve component: x-username
The component is displayed however

I wanted to find a replacement from Vue 2 ignoredElements
Vue.config.ignoredElements = [/^x-/];

Not 100% yet, but I think we have to extend idNativeTag to check against app.context.isCustomElement.
https://github.com/vuejs/vue-next/blob/e4dc03a8b17d5e9f167de6a62a645878ac7ef3e2/packages/runtime-dom/src/index.ts#L99-L106
It seems to me that we only use it in the compiler so far, so any custom element declared in a render function (or compiled during build) will resolve in a failure here.

You can add the blew config into vite.config.js.Because your template will compiled by sfc compiler.
vueCompilerOptions: {
    isCustomElement: tag => {
      return /^x-/.test(tag)
    }
  }

Other the app.config.isCustomElement = tag => /^x-/.test(tag);  only work with  runtime-dom compiler.

@underfin how can I add the same to Vue CLI?

You can add this into webpack config.It should work (I'm not test it).
{
        test: /\.vue$/,
        loader: 'vue-loader',
        options: {
          compilerOptions: {
    isCustomElement: tag => {
      return /^x-/.test(tag)
    }
  }
        }

Oh so we really only check during compile time? My mistake then.

@blacksonic for vue-cli you would have to do something like this:
// vue.config.js
module.exports = {
  chainWebpack: config => {
    config.module.rule('vue-loader').tap(options => {
      option.compilerOptions = {
         ...(options.compilerOptions || {})
         isCustomElement: tag => /^x-/.test(tag)
      }
    })
  }
}

Oh so we really only check during compile time? My mistake then.
Look it is for now and this will not generate code for customer component import and don't check it with runtime.

@LinusBorg
What can I do if the tap function doesn't exist?
The webpack-chain packages documentation seems to call use before calling tap.
I get this message:
(node:10740) UnhandledPromiseRejectionWarning: TypeError: config.module.rule(...).tap is not a function

I've tried this
config.module
      .rule('vue')
      .use('vue-loader')
      .loader('vue-loader')
      .tap(options => {
        options.compilerOptions = {
          ...(options.compilerOptions || {}), // merge existing compilerOptions, if any
          isCustomElement: tag => /^e-/.test(tag)
        }
      });

but now it seems that it tries to compile components with vue-template-compiler.
Vue packages version mismatch:

-<EMAIL_ADDRESS>(/Users/esysuser/workspace/vue-example-client/node_modules/vue/index.js)
-<EMAIL_ADDRESS>(/Users/esysuser/workspace/vue-example-client/node_modules/vue-template-compiler/package.json)

This may cause things to work incorrectly. Make sure to use the same version for both.
If you are using<EMAIL_ADDRESS>simply update vue-template-compiler.
If you are using<EMAIL_ADDRESS>or vueify, re-installing vue-loader/vueify should bump vue-template-compiler to the latest.

Module build failed (from ./node_modules/vue-loader/lib/index.js):
TypeError: Cannot read property 'parseComponent' of undefined

As pointed out, Vue 3 requires configuring custom elements via compiler options if pre-compiling templates.
This seems to be now a Vue CLI specific configuration problem so I'm closing it. But feel free to continue the discussion.
/cc @sodatea

I've found the fix.
The Vue CLI config is:
module.exports = {
  chainWebpack: config => {
    config.module
      .rule('vue')
      .use('vue-loader')
      .loader('vue-loader')
      .tap(options => {
        options.compilerOptions = {
          ...(options.compilerOptions || {}),
          isCustomElement: tag => /^x-/.test(tag)
        };
        return options;
      });
  }
};

And in addition, I needed to install the beta version of vue-loader

This seems to break now that vue-cli isn't using vue-cli-plugin-vue-next anymore.
I'm getting
Module Error (from ./node_modules/vue-loader/lib/index.js):
[vue-loader] vue-template-compiler must be installed as a peer dependency, or a compatible compiler implementation must be passed via options.

When removing the vue-loader rule the app will compile but the warnings show up again.
My uneducated guess is that setting the compilerOptions will force vue-loader to use vue-template-compiler?
Any idea how to fix this?

I'm still getting the following error:
Failed to resolve component: xyz
Versions:
"vue": "^3.0.2",
"vue-loader": "^16.0.0-rc.1"

Webpack:
{
...
rules: [
      {
        test: /\.vue$/,
        loader: 'vue-loader',
        options: {
          compilerOptions: {
            isCustomElement: tag => /^xyz/.test(tag),
          },
        },
      },
     ...
],
...
plugins: [
    new VueLoaderPlugin(),
    ...
]
}

需要安装vue-loader@next和vue-template-compiler能行

@vuesomedev worked for me, hoewever I had to get rid off one line, otherwise vue-cli wouldn't compile:
module.exports = {
  chainWebpack: (config) => {
    config.module
      .rule("vue")
      .use("vue-loader")
      .tap((options) => {
        options.compilerOptions = {
          ...(options.compilerOptions || {}),
          isCustomElement: (tag) => /^x-/.test(tag),
        };
        return options;
      });
  },
};

"vue": "^3.0.0",
"vue-loader": "^15.9.6"
"@vue/cli-service": "~4.5.0",
"@vue/compiler-sfc": "^3.0.0",

Thanks to everyone else who has shared.
This is what worked for me (i.e. I'm building with mode=development and expect the warnings about custom elements to go away, and they finally did):
// package.json
{
  "name": "...",
  "version": "0.1.0",
  "private": true,
  "scripts": {
    "build": "vue-cli-service build",
    "build:dev": "vue-cli-service build --mode development --dest ../server/public --no-clean --watch",
    ...
  },
  "dependencies": {
    "core-js": "^3.6.5",
    "vue": "^3.0.0",
    "vue-router": "^4.0.0-0"
  },
  "devDependencies": {
    "@vue/cli-plugin-babel": "~4.5.0",
    "@vue/cli-plugin-eslint": "~4.5.0",
    "@vue/cli-plugin-router": "~4.5.0",
    "@vue/cli-plugin-unit-jest": "~4.5.0",
    "@vue/cli-service": "~4.5.0",
    "@vue/compiler-sfc": "^3.0.11",
    "@vue/test-utils": "^2.0.0-0",
    "babel-eslint": "^10.1.0",
    "eslint": "^6.7.2",
    "eslint-plugin-vue": "^7.0.0",
    "lint-staged": "^9.5.0",
    "typescript": "~3.9.3",
    "vue-jest": "^5.0.0-0",
    "vue-loader": "^16.2.0"
  },
  ...
}

// vue.config.js
module.exports = {
  ...
  chainWebpack: config => {
    // Ignore custom HTML tags/Custom Elements
    config.module
      .rule('vue')
      .use('vue-loader')
      .loader('vue-loader')
      .tap(options => {
        options.compilerOptions = {
          ...(options.compilerOptions || {}),
          isCustomElement: tag => /^(m|octo)-/i.test(tag)
        };
        return options;
      });
  }
}

Hi,
I am using the suggested setup, like @jfbrennan , and when running the application on dev env using "vue-cli-service serve" I do not get the warnings. However, on production, I see the warnings in the console. I assumed these are build-time created warnings, and I am using the vue-cli-service for build with the same set up. So what could I be missing?

@vuesomedev What about solution for Vite.config.js

For vite this worked for me:
// vite.config.js
import vue from "@vitejs/plugin-vue";

export default {
  plugins: [
    vue({
      template: {
        compilerOptions: {
          isCustomElement: (tag) => tag.startsWith("cds-"),
        },
      },
    }),
  ],
};

@blabbath can you explain how you import your components? Please.
I've tried your solution... it isnt work.

typescript: ^4.5.4
vite: ^2.8.0
vue: ^3.2.25

webpack.config.js
{
  ...
  module: {
    rules: [
      {
        test: /\.vue$/,
        use: {
          loader: 'vue-loader',
          options: {
            compilerOptions: {
              isCustomElement: tag => /^s-/.test(tag)
            }
          }
        }
      },
      ...
  },
  plugins: [
    new VueLoaderPlugin(),
    ...
  ]
}


How to ensure database security for LLM's text2sql

I need the big model to help me with text2sql, but I am concerned about the risk of maliciously generating destructive SQL and potentially deleting the database. Can e2b take precautions against database security

Suggest adding database security detection function in the future


[UNDERTOW-1885] remove escape char from delimitered strings

Issue: https://issues.redhat.com/browse/UNDERTOW-1885
Upstream PR: https://github.com/undertow-io/undertow/pull/1165

Thanks @baranowb !

This PR have been reverted in the repository, see https://issues.redhat.com/browse/UNDERTOW-1885 for more information.


Unhandled error, please open a Github issue so we can fix it!

Unhandled error, please open a Github issue so we can fix it!
2017-12-07 10:19:59 Error list index out of range
Traceback (most recent call last):
File "lendingbot.py", line 94, in
Lending.lend_all()
File "/home/user1/poloniexlendingbot/modules/Lending.py", line 249, in lend_all
lend_all()
File "/home/user1/poloniexlendingbot/modules/Lending.py", line 249, in lend_all
lend_all()
File "/home/user1/poloniexlendingbot/modules/Lending.py", line 249, in lend_all
lend_all()
File "/home/user1/poloniexlendingbot/modules/Lending.py", line 247, in lend_all
usable_currencies += lend_cur(cur, total_lent, lending_balances, ticker)
File "/home/user1/poloniexlendingbot/modules/Lending.py", line 418, in lend_cur
orders = construct_orders(active_cur, active_bal, active_cur_total_balance, ticker)  # Build all potential orders
File "/home/user1/poloniexlendingbot/modules/Lending.py", line 319, in construct_orders
top_rate, bottom_rate = get_gap_mode_rates(cur, cur_active_bal, cur_total_balance, ticker)
File "/home/user1/poloniexlendingbot/modules/Lending.py", line 373, in get_gap_mode_rates
top_rate = get_gap_rate(cur, top_depth, order_book, cur_total_balance, True)
File "/home/user1/poloniexlendingbot/modules/Lending.py", line 306, in get_gap_rate
return Decimal(order_book['rates'][i])
IndexError: list index out of range

Thanks for the bug report @k0ni
There are a lot of these we need to tidy up. It shouldn't be anything to worry about, the bot should continue after this message.

Duplicate of #566


LDAP backend does not elevate admins to superuser in Django

My actions before raising this issue

[x] Read/searched the docs
[x] Searched past issues including old repo

In my adventures, completing #39 I have come discovered that users in the proper group, "CVAT Admins" in my case, are not promoted to superuser as expected by the login here. https://github.com/cvat-ai/cvat/blob/4708b5ecf8dd224adad11dc640e5485157a1f3ea/cvat/apps/iam/signals.py#L44
Expected Behaviour
Users that are a member of CN=CVAT Admins,CN=Users,DC=ad,DC=example,DC=com are elevated to superuser when DJANGO_AUTH_LDAP_GROUPS looks similar to the following
AUTH_LDAP_ADMIN_GROUPS = [
    'CN=CVAT Admins,CN=Users,DC=ad,DC=example,DC=com',
]
AUTH_LDAP_BUSINESS_GROUPS = [
    'CN=CVAT Managers,CN=Users,DC=ad,DC=example,DC=com',
]
AUTH_LDAP_WORKER_GROUPS = [
    'CN=Users,DC=ad,DC=example,DC=com',
]
AUTH_LDAP_USER_GROUPS = [
    'CN=Users,DC=ad,DC=example,DC=com',
]

DJANGO_AUTH_LDAP_GROUPS = {
    "admin": AUTH_LDAP_ADMIN_GROUPS,
    "business": AUTH_LDAP_BUSINESS_GROUPS,
    "user": AUTH_LDAP_USER_GROUPS,
    "worker": AUTH_LDAP_WORKER_GROUPS,
}

Current Behaviour

Users can authenticate, but it is unclear that they are properly assigned their roles. Admins cannot access the Django dashboard.
Possible Solution

Steps to Reproduce (for bugs)

Use the config that is described in https://github.com/cvat-ai/cvat/pull/39 (incomplete) and https://github.com/openvinotoolkit/cvat/issues/311
Login with user that only exists in Active Directory and is a member of "CVAT Admins".
Attempt to access dashboard.

 No
Operating System and version (e.g. Linux, Windows, MacOS): Fedora 36 (WSL) and Windows Server 2022 for Active Directory.
Code example or link to GitHub repo or gist to reproduce problem: Docs located in https://github.com/cvat-ai/cvat/pull/39

Resolved in another thread found here https://github.com/openvinotoolkit/cvat/issues/311#issuecomment-1193244501


New Functions for JMESPath

I'd like to propose a few additional functions for inclusion in the JMESPath specification:
https://github.com/the-g-man/jmespath-ext
They're not complex to implement but they add a great deal of power - for instance in dealing with recursive or normalized data structures.
I've added documentation and compliance tests for each of the three functions.

Oooh. The zip function could be really useful for a project I'm currently working on. Nice ideas there @the-g-man


strptime does not zero tm struct before calling c_strptime

man strptime gives an example code like the below:
   int
       main(void)
       {
           struct tm tm;
           char buf[255];

           memset(&tm, 0, sizeof(struct tm));
           strptime("2001-11-12 18:31:01", "%Y-%m-%d %H:%M:%S", &tm);
           strftime(buf, sizeof(buf), "%d %b %Y %H:%M", &tm);
           puts(buf);
           exit(EXIT_SUCCESS);
       }

The tm struct is zeroed before calling. datetime-fortran strptime does not do this which means that depending on the time string/format parts of the tm struct can be left containing uninitialised values.

Good catch! Did you encounter any case where this caused unexpected behavior?
Would something like this work?
type,bind(c) :: tm_struct

  !! A derived type provided for compatibility with C/C++ time struct.
  !! Allows for calling strftime and strptime procedures through the
  !! iso_c_binding.

  integer(kind=c_int) :: tm_sec = 0  !! Seconds      [0-60] (1 leap second)
  integer(kind=c_int) :: tm_min = 0  !! Minutes      [0-59]
  integer(kind=c_int) :: tm_hour = 0 !! Hours        [0-23]
  integer(kind=c_int) :: tm_mday = 0 !! Day          [1-31]
  integer(kind=c_int) :: tm_mon = 0  !! Month        [0-11]
  integer(kind=c_int) :: tm_year = 0 !! Year - 1900
  integer(kind=c_int) :: tm_wday = 0 !! Day of week  [0-6]
  integer(kind=c_int) :: tm_yday = 0 !! Days in year [0-365]
  integer(kind=c_int) :: tm_isdst= 0 !! DST          [-1/0/1]

endtype tm_struct


Update probs prefix to w3id.org and version of rdflib

@ricklupton
Hi Rick
I've made changes that are needed for building rdf files from md files in petrochemical-integrated-data using new w3id.org prefix.
Do you want me to bump src/sphinx_probs_rdf/version.py and update  CHANGELOG and if so what version number to use.
Also, do you want to keep as separate branch or merge into master. I think you will need to upload to twine.
Thanks

Hi @stephenjboyle I've added an example of how I'd update the changelog (can be done in the "unreleased" section independently of releasing a new version; when publishing a new version we just add a new heading for the new version making the unreleased section empty again). In this case it will be a breaking change so 0.4.x -> 0.5.0. I can do that after this is merged.
I took the opportunity to give a better prefix for the PROBS_RECIPE URIs. I don't think we have adapted any other code to use a new prefix here, so I think it's safe to choose this freely at this point (let me know if you think not).
Unless you see a problem with that change, please go ahead and merge this and tag me in the comment & I can release a new version. The other issue to increase compatibility with RDFox v6.2 can then be a bug fix as release 0.5.1.

@ricklupton
Hi Rick, I've copied function preferredLabel from rdflib as mentioned in https://github.com/ricklupton/sphinx_probs_rdf/issues/4
(did not see this earlier) and also modified setup.cfg to install at least rdflib 6.2.
I've tried using  petrochemical-integrated-data with rdflib 6.2 and tasks build_docs_rdf and enhance_data_unfccc run without errors when using icis object icis:SBR_\(Includes_SBCs\), so its seems to have fixed the problems we were having.
Is this ok to merge with master?

Thanks sounds good. One small comment above, and there should be a corresponding note added to the changelog that the required rdflib version had changed.

@ricklupton
branch https://github.com/ricklupton/sphinx_probs_rdf/tree/new_probs_prefix merged into master.

Thanks @stephenjboyle. I've released version 0.5.0 including those changes.


Add some more options

Add some more options to enable passive mode FTP behind NAT with dynamic IP as well as overriding default file permissions.

@mindrunner Hi. Thank you for enhancing options! But i'm not sure about default value of PASV_ADDR_RESOLVE. Can we use No as provided by fauria/docker-vsftpd?

Will come up with another PR to not mess around with your intellij-idea stuff


KeyError: 'PolarMask is not in the detector registry'

@xieenze when i run train.py,it appear KeyError: 'PolarMask is not in the detector registry', i do'nt know how to solve the problem,i expect your helpness

Maybe issue #11 will be helpful for you.
I also encountered this problem a few days ago, and I think maybe you should execute python setup.py develop in PolarMask but not in mmdetection.
Hope my answer can help you.

Maybe issue #11 will be helpful for you.
I also encountered this problem a few days ago, and I think maybe you should execute python setup.py develop in PolarMask but not in mmdetection.
Hope my answer can help you.

yes, you should install PolarMask not MMdetection


Don't add erroneous @type tags.

I missed these with my earlier @return tag fix. Same issue.

Thanks!


NIFI-11066 Removed unnecessary tag from minifi-c2-docker

Summary
NIFI-11066
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[x] Apache NiFi Jira issue created

Pull Request Tracking

[x] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[x] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[x] Pull Request based on current revision of the main branch
[x] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[x] Build completed using mvn clean install -P contrib-check

[x] JDK 8
[ ] JDK 11
[ ] JDK 17

Licensing

[ ] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[ ] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[ ] Documentation formatting appears as expected in rendered files

looks good +1


Update reporter.py

Adding better command handling for subprocess.run
This function runs the command directly (without going through a shell).
This fixes issues when folder path containing spaces and avoids shell injection vulnerabilities.

@navchandar Thank you for your contribution!


Can I prevent editing when clicking a link?

I have an atomic block that contains a link.
When I click the link, I want it to open the link but I do not want to start editing.
If I use e.preventDefault() on the  element, then the editor will not start editing but it will also not open the link.
I tried using e.preventDefault() on a container  around the link but editing would still start.
I've also tried setting contentEditable={false} both on the link and the container but editing would still start.
Any help would be appreciated if anybody has solved this issue.

Hey @thesunny, could you provide a fiddle reproing the issue you are having? We could try to edit it there and think of a solution.
Here is something you can start with:
https://jsfiddle.net/stopachka/m6z0xn4r/

Hi @stopachka, thanks for the starting fiddle and offering to help find a solution.
Here is the updated fiddle:
https://jsfiddle.net/m6z0xn4r/11/
Basically, I've pre-populated the editor with two blocks, the second of which is an atomic block that renders a link.
I want to be able to click that link to open a new page without having the editor start editing.
I've set it up so that start of editing, which calls the onFocus method, does a console.log of a message so that you can easily tell when the editor has set its focus. The goal is to be able to click the link without having the message logged; however, clicking the text should console.log the message.

not a clean way, calling blur in the Link click listener can leave the editing state.

set content editable false

@jan4984 Unfortunately, not a great solution because of the way my app works. Basically, I need it to not call focus at all.
@mzbac. Already tried setting contentEditable to false but that didn't work. It's already in the fiddle.

Okay, I found a solution. basically, what you have to do is on the  tag, set onMouseDown only to stopPropagation and preventDefault. You do not do anything to onClick.
I assume what's happening is that the focus is being set somewhere during the onMouseDown phase but the link opening handling of the browser is done during the onClick. I ran across it accidentally but seems to be working.
Here is the updated fiddle where it is working.
https://jsfiddle.net/m6z0xn4r/22/

great，I will change my "blur after focus" way to your solution in my project. Thanks for sharing.


Is there any way to disable the logs?

There is a lot of logging output in the container. Could you provide a way to disable logging. We have tried setting the system properties log4.debug and log4j.configuration, they were applied, but without affect. Thank you.

Hi @weltallerdemensct,
There is an issue to fix it. From now, I advise you run docker using -d ( “detached” mode, in the background)
Best,


Export doesn't respect currently selected KPI

The export button always POSTs to a url like /experiments/:experiment_name/export, even when on a page with a url like /experiments/:experiment_name/?kpi=:kpi_name

This seem to still be an issue?


Support pagination and realtime listening in future?

I just started using fireorm and have to say it is a great library and I am wondering if pagination and realtime listening are supported in future? As roadmap seems not listed these features.
At moment, I use custom repositorieswith copy and modify original code to do startAfter.

Hey!, yes, realtime listening and pagination are features that are in our roadmap! https://github.com/wovalle/fireorm/issues/1
Don't have the time or resources to set a date but is in my things to do.


Will there ever be Armada370/Armada375 support?

Hi!
Couldn't find the question here :). Will there ever be support in the future for the Synology's that are running with the Armada370/Armada375 chipset? Or isn't this possible?
Thank you for your time and keep up the great work, devs!

NASes with this chipset have a kernel version that is too old (3.2.40) to support WireGuard (requires 3.10). There are three possible ways of supporting it:

Pressure Synology into releasing a new version of DSM with a newer kernel (the best way)
Patching WireGuard to support older kernels (I think this is a lot of work)
Virtualize another OS on your NAS and install WireGuard in that one. (I don't know if this works, and if it does it's probably pretty slow)

If someone from the community steps up and does the work with patching WireGuard I'll be happy to merge it.
To explicitly answer your question. It'll probably never work and I don't think it'll ever be possible.

I am not questioning that the kernel is too old on these older boxes (3.2.101 on DSM 7). But then I ponder, how does the official Tailscale package for Synology work on these older boxes (works on DS214+), since Tailscale uses wireguard as the underlying VPN protocol, right? I guess there must be some way.

They are running WireGuard in userspace. I went to their GitHub to confim and they just package some statically linked binaries written in Go. This repository will only package the kernel module. There are other userspace implementations of WireGuard that may work on these older devices. I have never tried any of them myself though.


Browser freezing under 'heavy' subs

I recently got JavascriptSubtitlesOctopus up and running and testest a few videos, most which work great, but I noticed a couple videos with heavy intro subs (animation and effects) overloads my browser and freezes. From my understanding it should be able to handle it without lag. Perhaps I need to adjust some configurations? Below is a screenshot of the console output log.

Could you share the subs you're having trouble with?

@Yay295 Thanks for replying. Here is the ASS file along with the fonts used: https://drive.google.com/drive/folders/10li-vh6EO-0YfvK3GZqTW0Tqm1jfNI31?usp=sharing

@Yay295 did you get the chance to look into it?

A bit, but I don't have a conclusion. It is a big file, but it doesn't actually have anything too complex in it, and you can see from this demo that it can handle similar files (mostly) fine. I think it's probably just the sheer number of subtitle "lines" in the file. For the OP, some of the individual letters are composed of 50 or more lines to make it look how it does.

In my experience, at least in chrome, freeze happens when cache grows too large (or too fast?). Seems like memory reallocations in emscripten are becoming too expensive. But I don't really know much about it.
And after freeze video will actually play ok.
One more thing. Usually only 1080p are affected, while 720p are perfectly fine - another evidence of memory hog.

Scratch my previous comment, through maybe its a different issue.
Today I played with some heavy subs, and I noticed that they have large number of bitmaps for each frame.
So I tried to rewrite rendering part using createImageBitmap and got pretty good results.
Keep in mind, I'm not very familiar with this stuff.
I'm not sure if async breaks something, and there is no exception handling.
subtitles-octopus.js
function renderFrames() {
    var data = self.renderFramesData;
    var beforeDrawTime = performance.now();
    self.ctx.clearRect(0, 0, self.canvas.width, self.canvas.height);
    for (var i = 0; i < data.bitmaps.length; i++) {
        var image = data.bitmaps[i];
        self.ctx.drawImage(image.bitmap, image.x, image.y);
    }
    if (self.debug) {
        var drawTime = Math.round(performance.now() - beforeDrawTime);
        console.log(data.bitmaps.length + ' bitmaps, libass: ' + Math.round(data.libassTime) + 'ms, decode: ' + Math.round(data.decodeTime) + 'ms, draw: ' + drawTime + 'ms');
        self.renderStart = performance.now();
    }
}

subtitles-octopus-worker.js
self.render = function (force) {
    self.rafId = 0;
    self.renderPending = false;
    var startTime = performance.now();
    var renderResult = self._render(self.getCurrentTime() + self.delay, self.changed);
    var changed = Module.getValue(self.changed, "i32");
    if (changed != 0 || force) {
        var result = self.buildResult(renderResult);
        var newTime = performance.now();
        var libassTime = newTime - startTime;
        var promises = [];
        for (var i = 0; i < result[0].length; i++) {
            var image = result[0][i];
            var imageBuffer = new Uint8ClampedArray(image.buffer);
            var imageData = new ImageData(imageBuffer, image.w, image.h);
            promises[i] = createImageBitmap(imageData, 0, 0, image.w, image.h);
        }
        Promise.all(promises).then(function (imgs) {
            var decodeTime = performance.now() - newTime;
            var bitmaps = [];
            for (var i = 0; i < imgs.length; i++) {
                var image = result[0][i];
                bitmaps[i] = { x: image.x, y: image.y, bitmap: imgs[i] };
            }
            postMessage({
                target: "canvas",
                op: "renderMultiple",
                time: Date.now(),
                libassTime: libassTime,
                decodeTime: decodeTime,
                bitmaps: bitmaps
            }, imgs);
        });
    }
    if (!self._isPaused) {
        self.rafId = self.requestAnimationFrame(self.render);
    }
};

Here is some stats.
Before:
...
19:54:49.747 subtitles-octopus.min.js:1 176 canvases, 7 ms (+ 51 ms draw)
19:54:49.788 subtitles-octopus.min.js:1 176 canvases, 7 ms (+ 40 ms draw)
19:54:50.086 subtitles-octopus.min.js:1 184 canvases, 7 ms (+ 20 ms draw)
19:54:50.107 subtitles-octopus.min.js:1 184 canvases, 7 ms (+ 21 ms draw)
19:54:50.126 subtitles-octopus.min.js:1 184 canvases, 7 ms (+ 18 ms draw)
...

After:
...
20:13:15.469 subtitles-octopus.min.js:1 176 bitmaps, libass: 6ms, decode: 3ms, draw: 1ms
20:13:15.519 subtitles-octopus.min.js:1 176 bitmaps, libass: 11ms, decode: 10ms, draw: 1ms
20:13:15.536 subtitles-octopus.min.js:1 176 bitmaps, libass: 4ms, decode: 3ms, draw: 1ms
20:13:15.569 subtitles-octopus.min.js:1 180 bitmaps, libass: 6ms, decode: 3ms, draw: 1ms
20:13:15.603 subtitles-octopus.min.js:1 180 bitmaps, libass: 4ms, decode: 3ms, draw: 0ms
...

@no1d I'm testing your code, and it seems that solved the problem.

@no1d Test code: https://dador.github.io/JavascriptSubtitlesOctopus/experimental/no1d-render/stress.html

It is process intensive but it doesn't freeze much if at all, though at one point in a random test the subtitles just decided to not render at all when it became a burden, but I just like the fact that it doesn't freeze (as often as the previous one):


[New feature] Add a link to public RSS from public bookmarks page

Hello! This is my first issue.
I recently set up a public page with shared bookmarks and invited friends to follow my public RSS, but then I realized that the public RSS URL is only available in settings. I think it should be possible for a user looking at a public bookmarks page to discover the RSS link.
How about adding a <link rel="alternate" type="application/rss+xml" to the public bookmarks page if one is available? A RSS icon somewhere in page body would also help with discoverability.
I'm assuming that the public bookmarks page and public bookmarks RSS are always both enabled or both disabled. Does that sound correct?
(I might take a stab at adding it next week if it sounds ok? maybe good first commit for me?)

Both the public bookmarks page and the RSS feed are always accessible.
Adding a <link> would be OK. Adding a visible link (anchor) to the UI should be opt-in, in general I try to avoid adding any additional clutter to the bookmark view unless users enable that feature explicitly.


patch fix cec path issue

@davidusb-geek

This should work. This is because the root path is /data for forecast.py

This is not ideal. As its placed in the data directory. I may still change to use parent paths to fix this.

Ok I see. Many thanks!

#247 Tries to fix these types of issues.


Add check from compression

Compressed images not supported in release 1

Currently returns the checksum for the compressed Image data, so a check for compression is not strictly needed.


Performance 2022 custom metrics

Additional metadata about the LCP element:

is_lcp_discoverable: boolean whether it was discoverable in the raw HTML
is_lcp_preloaded: boolean whether it was preloaded
boundingClientRect: dimensions and position of the rendered element
naturalHeight, naturalWidth: intrinsic image dimensions
lcp_resource: full WPT response metadata
raw_lcp_element: node name and attributes of the element in the raw HTML
styles: allowlist of computed style prop/value pairs, set to background-image for now

Everything is applicable to images. The boundingClientRect will also be available for text-based LCP elements.
Tests

Image preloaded image, not discoverable

URL: https://rviscomi.github.io/demos/lcp_preloaded.html
Results: https://webpagetest.httparchive.org/result/220526_QT_12/1/details/#waterfall_view_step1

Image not preloaded, discoverable

URL: https://www.nytimes.com/
Results: https://webpagetest.httparchive.org/result/220526_ND_10/1/details/#waterfall_view_step1

Sourceset image not preloaded, discoverable

URL: https://almanac.httparchive.org/en/2021/css
Results: https://webpagetest.httparchive.org/result/220526_EE_14/1/details/#waterfall_view_step1

Background image not preloaded, not discoverable?

URL: https://codepen.io/rviscomi/pen/wvyPQoM
Results: https://webpagetest.httparchive.org/result/220526_H2_15/1/details/#waterfall_view_step1

Not an image

URL: https://www.example.com/
Results: https://webpagetest.httparchive.org/result/220526_V1_11/1/details/#waterfall_view_step1

Background image not preloaded, not discoverable?

This is an interesting case. The metric evaluates to not discoverable because there is no src or srcset on the page set to that image URL. But lcp_resource.initiator.type is "parser" so it seems to be discoverable? That might only be the case because the CSS is in an inline style block, haven't tested it with an external stylesheet. Should we drop the discoverable field and always check the initiator type?

Yeah hopefully that gives us enough metadata to figure it out later in SQL if there were any false negatives. We can analyze the next crawl to see how reliable the discoverable field is vs initiator.type.


Add vLLM integration for the generation API

vLLM allows for subtantially faster inference via smart management of the KV-cache. The library proposes seemless integration with some of the most popular HuggingFace models. We suggested in #150 to re-use some of the ideas in this paper/library for Outlines.
In a first iteration we can dispatch the sequence generation functions introduced in #139 to use vLLM's user-facing APIS, although the use would be limited to the simplest generation methods. Longer term, we should look into vLLM's internals and see if we can make Outlines compatible.

Agree, would be nice to see an integration for vLLM into outlines

Is there any progress on this? I'm using vllm with outlines - I'd be willing to help out / try and put out a PR if there's interest in any community contribution here.

There's always an interest in community contributions :) However, this requires substantial changes in Outlines' codebase that has far-reaching design implications. We need a bit more time. After that design change the integration should be very straightforward.

Oh absolutely. Not trying to nag. OSS work is voluntary and time consuming. Just showing interest, and willing to help out if it'd accelerate things. Thanks for the update!

Hi @rlouf, outline is really awesome!
I'm from the vLLM team and I'm quite excited about guideline's approach. We recently added the logits_processors API and I tried to integrate vLLM with outlines. Here's a hacky version that I got working
import outlines.models as models
from outlines.text.generate.regex import Regex

from vllm import LLM, SamplingParams
import torch

prompts = [
    "What is the IP Address of Google",
]

# We are not using this model for actual inference. But it seems to be required for Regex class.
model = models.transformers("gpt2-medium", device="cuda")

regex_processor = Regex(
    model,
    regex_string=r"((25[0-5]|2[0-4]\d|[01]?\d\d?)\.){3}(25[0-5]|2[0-4]\d|[01]?\d\d?)",
    max_tokens=16,
)

def create_proposal(token_ids, logits):
    token_ids = torch.Tensor([token_ids]).long().to("cuda")
    return  regex_processor.create_proposal(token_ids, logits)

sampling_params = SamplingParams(
    logits_processors=[create_proposal],
    max_tokens=16,
)

# Create an LLM in vLLM.
llm = LLM(model="gpt2-medium")

for _ in range(10):
    outputs = llm.generate(prompts=prompts, sampling_params=sampling_params, use_tqdm=False)
    regex_processor.last_fsm_states.clear() # We have to do this because we are sharing a FSM.
    for output in outputs:
        prompt = output.prompt
        generated_text = output.outputs[0].text
        print(f"Prompt: {prompt!r}, Generated text: {generated_text!r}")

However, there are a few issues:

The compilation time is about 10s, which is pretty long if it is used in online setting and supplied by the users. (I posted an issue here #383)
There is no "processor" only API. Outlines currently "wraps" transformers. From vLLM's point of view, we want to continue to expose users the logits_processors in SamplingParams. It would be great if the users can use both library without one wrapping the other.

As in above code, the model has to be initiated twice due to the reliance of model in Regex class
Does #366 address this? If so what would the API be like?

There's also some issues in sharing Regex processor is impossible here due to statefulness of FSM.

Hi @rlouf, outline is really awesome!

Thank you, so is vLLM!

The compilation time is about 10s, which is pretty long if it is used in online setting and supplied by the users. (I posted an issue here Tokenizer Aware FSM Construction #383)

Compilation might be an issue when calling the model as a one-off. When deployed in a service this hardly matters since it only needs to happen once. We'll update the examples to show compilation and inference can be separated. In the following compilation only happens when generator is created:
import outlines

model = outlines.models.transformers("gpt2")
generator = outlines.text.generate.regex("[a-Z]")

result = generator("prompt")

There is no "processor" only API. Outlines currently "wraps" transformers. From vLLM's point of view, we want to continue to expose users the logits_processors in SamplingParams. It would be great if the users can use both library without one wrapping the other.

I agree, this is partly what motivated #366. Everything is coupled and it's not ideal.

Does Refactor the sequence generation #366 address this? If so what would the API be like?
There's also some issues in sharing Regex processor is impossible here due to statefulness of FSM.

Yes, the refactor in #366 addresses this and removes the statefulness. Here's the design that is being implemented:

Generator holds the state. When it calls the Finite-State Machine with a state id, it gets the logits mask back. One it has generated the new token it queries the FSM for the nex state id by passing the new token id and the current state. Does this make sense?
It should then be much easier to integrate outlines into vLLM by only having to pass the FSM part to the logits processor.

LM Format enforcer is a library with some capability overlap with outlines, and has vLLM support. It may be suitable for your use case.


Which pre-trained weights from SoCo is used in depart

I notice in https://github.com/hologerry/SoCo there are several types of pre-trained weights based on R-50. And I wonder which one is used in this paper ?

SoCo_FPN_Star_400ep


warn when used in client components

closes #115

I've upgraded @edge-runtime/jest-environment to 2.2.0-beta.6 which includes https://github.com/vercel/edge-runtime/pull/328. This resolved the server-only issues when testing with @edge-runtime/jest-environment
I've added testEnvironmentOptions.customExportConditions to the configs, which resolved the server-only issues when testing with node

I realized we can mock server-only to make the unit tests pass.
But now some integration tests are failing due to server-only. I'm not sure whether those failures are legit or what we would expect from our packages.
vercel-storage-integration-test-suite:integration-test:     [Desktop Chrome] › @vercel/blob/blob.visual.test.ts:10:9 › @vercel/blob › page › serverless ────
vercel-storage-integration-test-suite:integration-test:     [Desktop Chrome] › @vercel/postgres/index.test.ts:95:11 › @vercel/postgres › pages directory › client › edge
vercel-storage-integration-test-suite:integration-test:     [Desktop Chrome] › @vercel/postgres/index.test.ts:99:11 › @vercel/postgres › pages directory › client › node
vercel-storage-integration-test-suite:integration-test:     [Desktop Chrome] › @vercel/postgres/index.test.ts:105:11 › @vercel/postgres › pages directory › pool › edge
vercel-storage-integration-test-suite:integration-test:     [Desktop Chrome] › @vercel/postgres/index.test.ts:109:11 › @vercel/postgres › pages directory › pool › node
vercel-storage-integration-test-suite:integration-test:     [Desktop Chrome] › @vercel/postgres-kysely/index.test.ts:63:11 › @vercel/postgres-kysely › pages directory › api › edge
vercel-storage-integration-test-suite:integration-test:     [Desktop Chrome] › @vercel/postgres-kysely/index.test.ts:67:11 › @vercel/postgres-kysely › pages directory › api › node
vercel-storage-integration-test-suite:integration-test:     [Desktop Firefox] › @vercel/postgres/index.test.ts:95:11 › @vercel/postgres › pages directory › client › edge
vercel-storage-integration-test-suite:integration-test:     [Desktop Firefox] › @vercel/postgres/index.test.ts:99:11 › @vercel/postgres › pages directory › client › node
vercel-storage-integration-test-suite:integration-test:     [Desktop Firefox] › @vercel/postgres/index.test.ts:105:11 › @vercel/postgres › pages directory › pool › edge
vercel-storage-integration-test-suite:integration-test:     [Desktop Firefox] › @vercel/postgres/index.test.ts:109:11 › @vercel/postgres › pages directory › pool › node
vercel-storage-integration-test-suite:integration-test:     [Desktop Firefox] › @vercel/postgres-kysely/index.test.ts:63:11 › @vercel/postgres-kysely › pages directory › api › edge
vercel-storage-integration-test-suite:integration-test:     [Desktop Firefox] › @vercel/postgres-kysely/index.test.ts:67:11 › @vercel/postgres-kysely › pages directory › api › node
vercel-storage-integration-test-suite:integration-test:     [Desktop Safari] › @vercel/postgres/index.test.ts:95:11 › @vercel/postgres › pages directory › client › edge
vercel-storage-integration-test-suite:integration-test:     [Desktop Safari] › @vercel/postgres/index.test.ts:99:11 › @vercel/postgres › pages directory › client › node
vercel-storage-integration-test-suite:integration-test:     [Desktop Safari] › @vercel/postgres/index.test.ts:105:11 › @vercel/postgres › pages directory › pool › edge
vercel-storage-integration-test-suite:integration-test:     [Desktop Safari] › @vercel/postgres/index.test.ts:109:11 › @vercel/postgres › pages directory › pool › node
vercel-storage-integration-test-suite:integration-test:     [Desktop Safari] › @vercel/postgres-kysely/index.test.ts:63:11 › @vercel/postgres-kysely › pages directory › api › edge
vercel-storage-integration-test-suite:integration-test:     [Desktop Safari] › @vercel/postgres-kysely/index.test.ts:67:11 › @vercel/postgres-kysely › pages directory › api › node

It seems like server-only is throwing incorrectly in those cases as they seem to be legitimate uses within pages/api

Closing as this didn't get any response from the storage team. Can be reopened later when it becomes relevant again.


Only unsuspend the board before updating text object positions

We no longer unsuspend when updating a text anchor, only before setting text positions. This allows for fewer unsuspend/suspends while updating comments and labels correctly.

👍 Looks good -- worked with @ekosmin on the final form of the changes.


Change referenced Ansible Roles to the new location

SAP related community roles have been moved to 'https://github.com/redhat-sap/' which means existing references to previuos repositories or Galaxy roles need to be updated as this case.

@berndfinger PTAL

fine for me. Sorry for the delay.


serverutil(engine): don't panic when notifier is closed in executor watcher

What problem does this PR solve?

Issue Number: close #6875
What is changed and how it works?

Use correct context when starting serverutil2.WatchExecutors goroutine
Return directly instead of panic when executor watcher returns an empty change result, which means the notifier has been closed.

Check List
Tests

Unit test
Integration test

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
None

/run-verify

/run-verify

Codecov Report

Merging #6876 (2ff7efe) into master (7c5032c) will decrease coverage by 5.4793%.
The diff coverage is 55.7692%.

Flag
Coverage Δ

cdc
?

dm
52.0161% <ø> (+0.0176%)
:arrow_up:

engine
62.6110% <55.7692%> (-0.0244%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.
@@               Coverage Diff                @@
##             master      #6876        +/-   ##
================================================
- Coverage   59.9224%   54.4430%   -5.4794%
================================================
  Files           783        416       -367
  Lines         89519      51597     -37922
================================================
- Hits          53642      28091     -25551
+ Misses        31168      20813     -10355
+ Partials       4709       2693      -2016

/merge

/run-all-tests

/run-check-issue-triage-complete


LinkError when running in browser

After successfully building the examples on the wasm32-unknown-unknown target and serving them alongside the .html file from the miniquad readme (which appears to be the correct way to deploy to web according to the current instructions) I get the following error in the browser (Chrome):
Uncaught (in promise) LinkError: WebAssembly.instantiate(): Import #57 module="env" function="time" error: function import requires a callable
The examples from miniquad itself work fine following the same process.

Is this related to this? https://github.com/not-fl3/miniquad/commit/a36e05300f8c59fc2fbbe1747324d2f44ba8b81b

Modifying the gl.js provided with miniquad to provide an import for 'time' instead of 'now' gets this working, but a more robust fix is probably needed.

good-web-game should update to the fresh miniquad version to use lasted gl.js
Workaround right now - use the link to gl.js with a versoin:

Relevant miniquad PR: https://github.com/not-fl3/miniquad/pull/97
I believe in the near future we will be able to avoid manually update gl.js version. But right now it is a problem - you either need to host and update appropriate gl.js version(or use the one from miniquad-samples, but with appropriate version)
Or always update miniquad and use the latest gl.js.
However I think the best place to continue this discussion is in the linked miniquad's PR.
Fill free to reopen if the workaround with the version did not fix the problem!

Hello what is the apporpriate version of gl.js for
macroquad = "0.2.9"
?

Hello what is the apporpriate version of gl.js for
macroquad = "0.2.9"
?
If I use
<script src="https://not-fl3.github.io/miniquad-samples/gl.js"></script>
Then I got :
LinkError: WebAssembly.instantiate(): Import #72 module="env" function="__web_on_grow" error: function import requires a callable

https://not-fl3.github.io/miniquad-samples/gl-0.1.19.js worked for me with macroquad 0.2


Protocol version in archive db

Add a protocol_version_id column to the blocks table in the archive db, which refers to a new table protocol_versions. Precomputed and extensional blocks get a new field protocol_version.
This change will make it easy to know which hard fork blocks were created in. In particular, the replayer can avoid checking ledger hashes for blocks prior to the berkeley hard fork.

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me


Update Xcode project

Some additional housekeeping for Xcode 10
The most significant change is the merger of the “Version Notes”, “Code Sign ID” and “Archive and Prep for Upload” into a single target called “Deployment”. The individual script phases have been added to it.

This works on macOS 10.13 / xcode 10.1 as long as you follow the instructions on https://learningswift.brightdigit.com/swift-5-0-xcode-10-1/
Basically:

Download Swift 5.0 RELEASE tool chain
Edit this file: /Applications/Xcode.app/Contents/PlugIns/Xcode3Core.ideplugin/Contents/SharedSupport/Developer/Library/Xcode/Plug-ins/XCLanguageSupport.xcplugin/Contents/Resources/Swift.xcspec

        SupportedLanguageVersions = (

            3.0,

            4.0,

            4.2,

            5.0

        );

        LanguageVersionDisplayNames = {

            3.0 = "Swift 3";

            4.0 = "Swift 4";

            4.2 = "Swift 4.2";

            5.0 = "Swift 5.0-RELEASE";

        };


luci-app-advanced-reboot: better information for snapshots

Signed-off-by: Stan Grishin<EMAIL_ADDRESS>

Thanks


Support translation rendering in source language

If there are translations in the source language on Transifex,
use those instead of rendering based on the original source string,
thus unlocking the "edit source string" feature.
Also, make a small optimization by using string interpolation
for ICU pluralized strings instead of concatenating 3 strings
together.

Codecov Report

Merging #54 (20be85e) into devel (614316d) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##            devel      #54   +/-   ##
=======================================
  Coverage   77.40%   77.40%
=======================================
  Files          36       36
  Lines        2793     2793
=======================================
  Hits         2162     2162
  Misses        631      631

Impacted Files
Coverage Δ

transifex/native/cds.py
97.29% <ø> (ø)

transifex/native/core.py
94.82% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 614316d...20be85e. Read the comment docs.


Possible error in the return of the update method

I have been creating the update_or_create method based on the get_or_create and update methods, doing some tests I found a possible bug in the update method.
in the database I have the following data.
[
  {
    "name": "Venom",
    "year": 2023
  },{
    "name": "Venom2",
    "year": 2021
  }
]

and when executing the next query Movie.query({Movie.name: "Venom"}).update({Movie.year: 2021}), what I would expect is for the method to return
[
  {
    "name": "Venom",
    "year": 2021
  }
]

But what it returns is
[
  {
    "name": "Venom",
    "year": 2021
  },{
    "name": "Venom2",
    "year": 2021
  }
]

Is this a bug or is expected to happen?

I agree this is not expected, I think this is a bug.
Will you be able to take a look?

Of course, today is difficult for me, but I will take a look at it in the next few days.

is there really a need for update_or_create func?

Well the use case is different. Can you explain why you think it's not needed?

@aminalaee, could you explain why *args is used?
https://github.com/aminalaee/mongox/blob/e6698f62be29b00dc372884a82f7f0b07078f1ea/mongox/models.py#L207
and the error is because it is looking for the last updated field for the return and ignores the initial filter, I already have a possible solution but I want to understand the above first.

The args are the fields that need to be updated. More like a bulk update updating all matching criteria:
movies = await Movie.query(Movie.year == 1990).update(Movie.year == 2000)

We also have single object update (might not be related):
movie = await Movie.query().get()

movie.name = "Another Movie"
movie = await movie.save()

but it would be more like this
movies = await Movie.query({Movie.year: 1990}).update({Movie.year: 2000})

and if we want to update more fields it would be
movies = await Movie.query({Movie.year: 1990}).update({Movie.year: 2000, Movie.name: "Venom"})

if what we want is to be able to pass field to field it would be
movies = await Movie.query({Movie.year: 1990}).update(year=2000, name=Venom)

but for this we must use is **kwargs

I get your point now.
Maybe we need to fix that in a separate PR? Probably we can fix update in a PR when we add test in the update case as you explained.

I agree that this should be a separate PR and it should be before creating the PR with the update_or_create method.
So, now I'll work on reorganize the update.

Great, Thank you @MAD-py

Issue resolved #28

@MAD-py Awesome, thank you. Do you think we could extend the tests for this, to make sure it works as expected? I mean if you're interested feel free, otherwise I can do that.

But this is already tested in these lines.
https://github.com/aminalaee/mongox/blob/c5161e53912d58320666033c079b0df9428dad31/tests/test_models.py#L264-L269
I have added those lines to the tests to support the solution of this bug.

Oh sorry my comment wasn't clear. I meant we found this  when working with get_or_create so we could add it there. But you're right that's tested and not related here.

Ok, so that's all right?

Yeah perfect. Thanks


FEATURE REQUEST node / Typescript equivalent

is there a nodejs / typescript equivalent of this project ?

Hi! We currently don't have any plans of porting these rotation lambdas to another language. Could elaborate the need for this?


Ghantasalaphanidhar patch 2

Updated changes for GCC apps
"To make your app available for GCC users, the auth process/flow should identify and route the user to the specified/expected content URL for GCC users as opposed to have duplicate apps listed in the store."

Docs Build status updates of commit 18a9469:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/concepts/deploy-and-publish/appsource/publish.md
:bulb:Suggestion
View
Details

msteams-platform/concepts/deploy-and-publish/appsource/publish.md

Line 2, Column 8: [Suggestion-duplicate-titles] Title 'Microsoft Teams app approval process guidance - Teams' is duplicated in: 'concepts/deploy-and-publish/appsource/publish.md(2,8), onboard-teams-dev-platform/doc-links/publish.md(2,8)'. Titles must be unique within a docset.
Line 3, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Describes the approval process for getting your app published to the Microsoft Teams app store' is duplicated in 'concepts/deploy-and-publish/appsource/publish.md(3,14)', 'onboard-teams-dev-platform/doc-links/publish.md(3,14)'. NOTE: This Suggestion will become a Warning in late October, 2020.

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

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

File
Status
Preview URL
Details

msteams-platform/concepts/deploy-and-publish/appsource/publish.md
:bulb:Suggestion
View
Details

msteams-platform/concepts/deploy-and-publish/appsource/publish.md

Line 2, Column 8: [Suggestion-duplicate-titles] Title 'Microsoft Teams app approval process guidance - Teams' is duplicated in: 'concepts/deploy-and-publish/appsource/publish.md(2,8), onboard-teams-dev-platform/doc-links/publish.md(2,8)'. Titles must be unique within a docset.
Line 3, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Describes the approval process for getting your app published to the Microsoft Teams app store' is duplicated in 'concepts/deploy-and-publish/appsource/publish.md(3,14)', 'onboard-teams-dev-platform/doc-links/publish.md(3,14)'. NOTE: This Suggestion will become a Warning in late October, 2020.

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


DevTools isn't reliably starting when not already installed

Right now we only run "pub global activate devtools" at most once every 12 hours, which means in some cases, e.g. maybe on bots, it's not running when it should. We already run "pub global list", we should just use that to see if we need to ignore the 12 hour limit and install it regardless. Otherwise, people debugging issues by uninstalling things won't have things work automatically.

Tests for this are in https://github.com/flutter/flutter/pull/74533 but commented out for now.


SAVE/BOUNDS  should list the AXIS_bnds variables as dimensions.

Reported by ansley b manke on 3 Jun 2009 16:59 UTC
Compare these two cases.
The first, using SAVE/EDGES, behaves correctly. The DIMENSIONedges coordinate variables are listed among the dimensions, and so when the file is used, the output of ..varnames lists just the variable TEMP and the edges coordinate is listed among ..dimnames.
For SAVE/BOUNDS, the DIMENSION_bnds variables are not among the dimensions, so they are listed along with the data variables, with ..varnames and not as they should be, with ..dimnames.  Saving with /BOUNDS should behave in the same way as with /EDGES.
yes? use levitus_climatology
yes? save/clobber/file=temp_edges/EDGES  temp
 LISTing to file temp_edges

yes? use temp_edges
 *** NOTE: Evenly spaced axis has edges definition: XAXLEVITR - ignored
 *** NOTE: Evenly spaced axis has edges definition: YAXLEVITR - ignored

yes? list ..varnames
             VARIABLE : ..VARNAMES
             FILENAME : temp_edges.nc
        "TEMP"

yes? list ..dimnames
             VARIABLE : ..DIMNAMES
             FILENAME : temp_edges.nc
             SUBSET   : 6 points (X)
 1   / 1:"XAXLEVITR"
 2   / 2:"XAXLEVITRedges"
 3   / 3:"YAXLEVITR"
 4   / 4:"YAXLEVITRedges"
 5   / 5:"ZAXLEVITR"
 6   / 6:"ZAXLEVITRedges"

yes? sp ncdump -h temp_edges.nc
netcdf temp_edges {
dimensions:
        XAXLEVITR = 360 ;
        XAXLEVITRedges = 361 ;
        YAXLEVITR = 180 ;
        YAXLEVITRedges = 181 ;
        ZAXLEVITR = 20 ;
        ZAXLEVITRedges = 21 ;
variables:
        double XAXLEVITR(XAXLEVITR) ;
                XAXLEVITR:units = "degrees_east" ;
                XAXLEVITR:modulo = " " ;
                XAXLEVITR:point_spacing = "even" ;
                XAXLEVITR:axis = "X" ;
                XAXLEVITR:edges = "XAXLEVITRedges" ;
        double XAXLEVITRedges(XAXLEVITRedges) ;
                XAXLEVITRedges:edges = " " ;
        ...

The same commands, but saved with /BOUNDS:
yes? use levitus_climatology
yes? save/clobber/file=temp_bounds.nc/BOUNDS temp
 LISTing to file temp_bounds.nc

yes? use temp_bounds

yes? list ..varnames  ! The DIM_bnds variables incorrectly included.
             VARIABLE : ..VARNAMES
             FILENAME : temp_bounds.nc
             SUBSET   : 4 points (X)
 1   / 1:"XAXLEVITR_bnds"
 2   / 2:"YAXLEVITR_bnds"
 3   / 3:"ZAXLEVITR_bnds"
 4   / 4:"TEMP"

yes? list ..dimnames
             VARIABLE : ..DIMNAMES
             FILENAME : temp_bounds.nc
             SUBSET   : 3 points (X)
 1   / 1:"XAXLEVITR"
 2   / 2:"YAXLEVITR"
 3   / 3:"ZAXLEVITR"

yes? sp ncdump -h temp_bounds.nc
netcdf temp_bounds {
dimensions:
        XAXLEVITR = 360 ;
        bnds = 2 ;
        YAXLEVITR = 180 ;
        ZAXLEVITR = 20 ;
variables:
        double XAXLEVITR(XAXLEVITR) ;
                XAXLEVITR:units = "degrees_east" ;
                XAXLEVITR:modulo = " " ;
                XAXLEVITR:point_spacing = "even" ;
                XAXLEVITR:axis = "X" ;
                XAXLEVITR:bounds = "XAXLEVITR_bnds" ;
        double XAXLEVITR_bnds(XAXLEVITR, bnds) ;
                ...

Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/1666

Comment by ansley.b.manke on 5 Jun 2009 16:19 UTC
Note that the CF standard does not list bounds variables among the coordinate variables; here is an example from the standard for a bounds variable on a latitude axis:
dimensions:
  lat = 64;
  nv = 2;    // number of vertices
variables:
  float lat(lat);
    lat:long_name = "latitude";
    lat:units = "degrees_north";
    lat:bounds = "lat_bnds";
  float lat_bnds(lat,nv);

So, we should leave alone the way that Ferret writes data with SAVE/BOUNDS.  But, when reading in a dataset, we could save a parameter in the attribute-handling structure for variables DIMNAME_bnds, when the coordinate variable DIMNAME has the attribute DIMNAME:bounds = "DIMNAME_bnds". This parameter would mark DIMNAME_bnds as being among the coordinate information for the file, not a standard variable.

Comment by ansley.b.manke on 3 Apr 2017 21:42 UTC
this is long since addressed.


Support #[layout] without trailing #[route]

Problem
Wrapping the last path of a Route in a Router currently causes a compilation error. I think the macro is currently failing on a missing trailing variant.
Steps To Reproduce
Steps to reproduce the behavior:
enum Route {
    #[layout(Layout)]
        #[route("/")]
        Home {},
    #[end_layout]
}

error: expected identifier, found `}`
   |
6  | enum Route {
   |                 ----- while parsing this enum
...
13 | }
   | ^ expected identifier
   |
   = help: enum variants can be `Variant`, `Variant = <integer>`, `Variant(Type, ..., TypeN)` or `Variant { fields: Types }`

Expected behavior
A quick fix may be to handle where there is no syn::Variant.
Environment:

Dioxus version:  main
Rust version:    nightly
App platform:    all

Questionnaire

I would like to fix and I have a solution

Anyone else who encounters this, the solution is to remove the trailing #[end_layout]

Anyone else who encounters this, the solution is to remove the trailing #[end_layout]

thank you, you solve my problem


Support prune docker images in non-standard location

Currently, the docker volume location is hardcoded for the disk space check in the pruning function: https://github.com/eth-educators/eth-docker/blob/468c4fe98cdf3c7a3cad0959c79b4570029e6573/ethd#L679-L685
It could be dynamically detected using something like the following:
export GETH_VOLUME_MOUNTPOINT=`docker inspect eth-docker_geth-eth1-data | jq --raw-output '.[0].Mountpoint'`

In my case that gets me /data/docker/volumes/eth-docker_geth-eth1-data/_data, which works great with df.

That's a good point. Let me take a look at it.

This should now work and parses daemon.json for the docker data-root. Give it a whirl!


Update composition-api.md

Add the next NavigationGuard callback to enhance default behaviour of continuing navigation when return is void or true or undefined.
This is an appropriate behaviour in production.

Thank you but the  current version is the correct one


BUG: Colors not rendering in IE

This module doesn't render in IE and older browsers that do not support CSS variables. I was able to create a workaround by creating fallback CSS values for the colors that were using variables. Ideally we shouldn't have to do this.
I can post the fix I used if anyone needs it.

@manjot-cams please, create a GIST so we can include that in the README at least.