fix(engine): conversion from undefined to JSON

Context
Related task
Currently converting undefined to JSON panics, which causes jstz kernel to hang. We should throw a JS error Instead of panicking.
** Test **
To locally test, check out my branch locally, replace the following under the [patch.crates-io] with your local path in Cargo.toml
boa_ast = { git = "https://github.com/trilitech/boa.git", branch = "sam.finch@/context/expose-instruction-count" }
boa_engine = { git = "https://github.com/trilitech/boa.git", branch = "sam.finch@/context/expose-instruction-count" }
boa_gc = { git = "https://github.com/trilitech/boa.git", branch = "sam.finch@/context/expose-instruction-count" }
boa_interner = { git = "https://github.com/trilitech/boa.git", branch = "sam.finch@/context/expose-instruction-count" }
boa_macros = { git = "https://github.com/trilitech/boa.git", branch = "sam.finch@/context/expose-instruction-count" }
boa_parser = { git = "https://github.com/trilitech/boa.git", branch = "sam.finch@/context/expose-instruction-count" }
boa_profiler = { git = "https://github.com/trilitech/boa.git", branch = "sam.finch@/context/expose-instruction-count" }

Tested that kernel doesn't hang in case undefined is passed to Kv.set
Repl:
Before:

After:

Lgtm -- would you be able to do a PR on jstz that updates the patches


Allow fetching all rows from results endpoint

CATEGORY
Choose one

[ ] Bug Fix
[X] Enhancement (new features, refinement)
[ ] Refactor
[ ] Add tests
[ ] Build / Development Environment
[ ] Documentation

SUMMARY

Currently when results are fetched from /superset/results/ we apply DISPLAY_MAX_ROW, to limit the amount of data displayed in the UI. At Lyft, we have other clients accessing Superset programmatically, and we would like to bypass the limit when fetching data from these clients.
I changed the endpoint behavior so that by default DISPLAY_MAX_ROW is not applied, but it can be passed optionally. The frontend was changed to query /superset/results/${DISPLAY_MAX_ROW}, returning only a subset of the rows.

TEST PLAN

Tested with curl, confirmed it works. Added unit tests.
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

REVIEWERS

Codecov Report

Merging #8389 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #8389      +/-   ##
==========================================
- Coverage   67.57%   67.56%   -0.01%
==========================================
  Files         448      448
  Lines       22527    22529       +2
  Branches     2364     2364
==========================================
  Hits        15222    15222
- Misses       7167     7169       +2
  Partials      138      138

Impacted Files
Coverage Δ

superset/views/core.py
70.06% <0%> (-0.1%)
: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 2117d1e...179e676. Read the comment docs.

@etr2460 will do! I'll also add some unit tests.

Sorry, I probably should have thought of this before, but maybe we should have the client explicitly ask for DISPLAY_MAX_ROWS rows from the results instead of the backend automatically applying it.  So instead of adding an ignore_limit setting, we make the default pass back the entire results set, and the client adds a rows query param to /results that requests DISPLAY_MAX_ROWS rows. I think this might be a bit cleaner, and would make the superset backend behave more like a service with multiple consumers than just assuming the client is asking by default. thoughts @villebro @betodealmeida ?

No worries, I agree that's a better approach.

cc: @etr2460


Rework other branches to point to the master CHANGELOG

Instead of needing to keep up various different versions of the CHANGELOG.md file on all of the legacy branches, update the legacy branch versions of the change log to point to the master branch version of the file.
This will make the CHANGELOG mentioned in the gemspec the clear single authority about the change history of the Gem.

Closed by commits to each of the respective branches:

675f4a2
ca24914
c4073d5
1f47119


Downloads are pinned to de.archive.ubuntu.com/ubuntu/pool/main

I want to control the repo I download from, either an internal repo, or another mirror but I cant do it as the repo is hard-coded to de.archive.ubuntu.com
Pls change to use {{tomcat_ubuntu_repo}}, so  tasks/main.yml becomes:
- name: Download Tomcat from Ubuntu Package archive
  get_url:
    url: "{{ item }}"
    dest: "{{ tomcat_ubuntu_download_dir }}"
  with_items:
    - http://{{tomcat_ubuntu_repo}}/ubuntu/pool/main/t/tomcat8/tomcat8_{{ tomcat_ubuntu_version }}.deb
        etc....

Thanks for your good suggestion! Will add this ASAP.


Added a server config option to use a different HTTPS port

This pull request would allow users to use a different HTTPS port by setting sslPort in serverConfig.toml.
(The commit is unverified because there is no email address associated with my key. This is because I am uncomfortable branding my permanent cryptographic identity with the name of a corporation, but have yet to setup self-hosted email. I can offer as reassurance only my word that the key is mine and its private counterpart has never been leaked and is protected with a strong password. If you are nonetheless uncomfortable merging my changes due to the unverified commit, I would ask you to consider instead committing the same changes yourself, and would not hold it against you were you to do so.)

I'm sorry, on further reflection I think it was quite unreasonable of me to ask you to consider an unverified pull request, no matter the reason. As such, I've set up sef-hosted email, associated and verified an email address to my public key, and recommitted the same changes on a different branch using the modified key instead, so that the commit would display as verified. I'll now close this pull request and reopen it concerning that branch instead. I apologize again for my lack of professionalism in this regard.


Does not support ChatCompletion.acreate

hey, thanks for the report! We will be working on this shortly and should have it in the next week or 2.

Hello @mc-marcocheng  Please checkout our latest docs at https://wandb.me/weave. We have completely rewritten the application and underlying architecture. It is very likely that this issue is resolved with the latest package and apis (:


How do I deploy HDP 2.6 ?

I am using 1.14, how do I deploy HDP 2.6 ?

@desaiak
You have two choice:

If you are using 1.14.0 you can deploy HDP-2.6 if you are using a blueprint with HDP-2.6 and you configure the ambari and HDP repository to HDP-2.6 repos.
Second option is using an rc build (1.14.4 is unreleased currently) which can configure HDP-2.6 automatically if you have HDP-2.6 in your blueprint file
You can install the rc version with:

curl -Ls public-repo-1.hortonworks.com/HDP/cloudbreak/cloudbreak-deployer_1.14.4-rc.21_Linux_x86_64.tgz | sudo tar -xz -C /bin cbd && cbd version
cbd restart

Thanks Richard !
Will this command upgrade 1.14 to 1.14.4
In other words can I run it on the server that has 1.14 currently installed ?

@desaiak
Yes, but then you should run the 'cbd restart' in the deployment folder which /var/lib/cloudbreak-deployment by default

Thanks .. I have now used the latest AMI with 1.14.4


replace maid with janitor

Janitor is vastly superior to Maid. It does more things while also running better.
I'm about to go to bed, so I'll update this with a list tomorrow.

alright the benefits:

Janitor:Add returns whatever was added, which Maid doesn't.
Janitor:Add also accepts a custom method, if you want to call :Remove on a BasePart for whatever reason, you can do that.
Janitor:Add also accepts a custom reference to store under, which keeps the api more consistent. (Maid.A = X and Maid:GiveTask(Y) vs Janitor:Add(X, nil, "A") and Janitor:Add(Y))
Janitor also allows linking to an Instance, so when the Instance is destroyed, the Janitor cleans up everything along with it.

alright the benefits:

Janitor:Add returns whatever was added, which Maid doesn't.
Janitor:Add also accepts a custom method, if you want to call :Remove on a BasePart for whatever reason, you can do that.
Janitor:Add also accepts a custom reference to store under, which keeps the api more consistent. (Maid.A = X and Maid:GiveTask(Y) vs Janitor:Add(X, nil, "A") and Janitor:Add(Y))
Janitor also allows linking to an Instance, so when the Instance is destroyed, the Janitor cleans up everything along with it.

This was a bit old, so I decided to just revamp it. Closing for https://github.com/Sleitnick/Knit/pull/126


Possible improvement of meta data handling

CConfig.py contains the following code:
rMetaData      = CStruct(
                            sVersionSW = '',
                            sVersionHW     = '',
                            sVersionTest   = '',
                            sROBFWVersion  = get_full_version('Robot Framework')
                        )

together with:
if "version_sw" in suiteMetadata and self.rMetaData.sVersionSW == '':
    pass
else:
    BuiltIn().set_suite_metadata("version_sw", self.rMetaData.sVersionSW, top=True)
if "version_hw" in suiteMetadata and self.rMetaData.sVersionHW == '':
    pass
else:
    BuiltIn().set_suite_metadata("version_hw", self.rMetaData.sVersionHW, top=True)
if "version_test" in suiteMetadata and self.rMetaData.sVersionTest == '':
    pass
else:
    BuiltIn().set_suite_metadata("version_test", self.rMetaData.sVersionTest, top=True)

My impression is that this is very long winded.
This is much shorter - and should also work:
for parameter in ("version_sw", "version_hw", "version_test"):
    BuiltIn().set_suite_metadata(parameter, "", append=True, top=True)

And it is also possible, to use the same method in the same file to make a dump of all metadata.
I tried the following use case:

version_test not defined
version_hw defined within robot file as Metadata within *** Settings ***
version_sw defined within command line with: --metadata version_sw:metadata_version_sw_in_command_line
my_test_local_metadata defined within robot file as Metadata within *** Settings ***

Outcome in debug log:
Set suite metadata 'project' to value 'RobotFramework Testsuites'.
Set suite metadata 'machine' to value '...'.
Set suite metadata 'tester' to value '...'.
Set suite metadata 'testtool' to value 'Robot Framework 4.1.3 (Python 3.9.16 on win32)'.
Set suite metadata 'version' to value '0.6.0'.
Set suite metadata 'version_sw' to value 'metadata_version_sw_in_command_line '.
Set suite metadata 'version_hw' to value 'metadata_version_hw_within_file '.
Set suite metadata 'version_test' to value ''.
Entire meta data available during test execution:
Meta data 'machine' = '...'
Meta data 'my_test_local_metadata' = 'my_test_local_metadata_value_within_file'
Meta data 'project' = 'RobotFramework Testsuites'
Meta data 'tester' = '...'
Meta data 'testtool' = 'Robot Framework 4.1.3 (Python 3.9.16 on win32)'
Meta data 'version' = '0.6.0'
Meta data 'version_hw' = 'metadata_version_hw_within_file '
Meta data 'version_sw' = 'metadata_version_sw_in_command_line '
Meta data 'version_test' = ''

This is the alternative code:
suiteMetadata = BuiltIn().get_variables()['&{SUITE_METADATA}']

BuiltIn().set_suite_metadata("project"  , self.sProjectName, top=True)
BuiltIn().set_suite_metadata("machine"  , self.__getMachineName(), top=True)
BuiltIn().set_suite_metadata("tester"   , self.__getUserName(), top=True)
BuiltIn().set_suite_metadata("testtool" , self.rMetaData.sROBFWVersion, top=True)
BuiltIn().set_suite_metadata("version"  , VERSION, top=True)

# additional parameters that shall be present even in case the user does not set a value
# (but if already a value is available, this value shall not be overwritten)
for parameter in ("version_sw", "version_hw", "version_test"):
    BuiltIn().set_suite_metadata(parameter, "", append=True, top=True)

# output of entire metadata:
BuiltIn().log("Entire meta data available during test execution:")
suiteMetadata_updated = BuiltIn().get_variables()['&{SUITE_METADATA}'] # !!!
for md_parameter, value in suiteMetadata_updated.items():
    BuiltIn().log(f"Meta data '{md_parameter}' = '{value}'")

I cannot be sure not to overlook any side effect. Please check this code carefully (and give it a chance ;-).

Should solve:
https://github.com/test-fullautomation/robotframework-testsuitesmanagement/issues/102
See also:
https://github.com/test-fullautomation/robotframework-testsuitesmanagement/issues/103#issuecomment-1431245925

Much more complicated than I expected!
There is a difference between "suite" and "top level suite". Meta data in command line (by --metadata) are at top level.
Values defined with set_suite_metadata(...) are at top level only with top=True (like done in testsuites management).
Meta data values defined in Settings within a robot file seems to be local (= not at top level).
OK so far. But the Robot Framework documentation only gives a hint about the existence of this switch top - without any explanation about meaning and impact.
Side effects: In case of a single robot file is executed, there seems not to be a concrete difference between "local" and "top level". All together is stored in SUITE_METADATA. But when I execute a folder containing robot files, it's completely different:
When printing the content of SUITE_METADATA in CConfig.py, then only the local metadata are printed - and not the top level meta data values any more. Therefore I added the code to print the values also to the testcase_setup in CSetup.py - and I called this testcase_setup in my robot file. The outcome is: I have only the local values printed out now two times. But the top level ones are lost completely.
OK, I stop this now.
Two aspects:

We urgently need to learn more about the scopes of meta data (depending of a single file or a folder is executed) and about how the Robot Framework handles the values.
We need to clarify our requirements.

Only when this is clarified we have a chance to modify the code in an meaningful way.

OK, I try once a gain to get clarity:

In suite setup we need to find a way to get access to top level meta data (in both cases: a single file is executed and a folder is executed).
We need to find a way to distinguish already in the suite setup between top level values and local values.
In suite setup we print only the top level values - under an unmistakable headline (e.g. Suite metadata value:).
In test setup we need to find a way to get access to top level values. We print at first the top level values - also under the same unmistakable headline like used in the suite setup. This is a repetition only, but helpful (user has no need any more to scroll up to find the top level values.
In test setup we print in a second step all other meta data values, that are known in the scope of the current test only (the local ones). Also under an unmistakable headline (e.g. Local meta data value:).

Finally we have to clarify how we can consider all other parameters e.g. the ones provided by testsuites management, in this concept also.

Hello Holger,
As you already known, ROBFW could be triggered at robot file level or at directory level which can contains many robot files and sub-directories. We could set metadata for every robot file (defines in *** Settings ***) or set metadata for a directory (creates __init__.robot in the directory then defines in *** Settings *** of __init__.robot).
The following definition:
rMetaData      = CStruct(
                            sVersionSW = '',
                            sVersionHW     = '',
                            sVersionTest   = '',
                            sROBFWVersion  = get_full_version('Robot Framework')
                        )

aims to define and set a metadata at highest level when executing Robot test with TestsuitesManagement.
I created a small improvement in commit 0c3c8117b0dbd
Could you please help me check this ticket again?
Thank you,
Son

Ready for sprint 0.13.0 [09.08.24](jsonpreprocessor / tsm)


Altering datetime defaults causes panic

Describe the bug
I'm trying to alter a datetime column, that has DEFAULT NULL and nothing else, to have CURRENT_TIMESTAMP as DEFAULT and ON UPDATE.
Environment

Skeema version and OS:

skeema version 1.11.1-community
commit d637ed77fa1fe1f82f8fdd982740b99f754cf2d5, released 2023-12-04T22:50:03Z
Running on MacOS

Database vendor, version, OS/platform: MySQL 5.7.12-log (select version();) on RDS
Any other environmental notes or special configuration: ENGINE=InnoDB DEFAULT CHARSET=utf8

To Reproduce

skeema pull production - No file system changes, already up to date
Change updated_at datetime DEFAULT NULL, to updated_at datetime DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
skeema diff production (--debug)

General warnings Docker images for mysql:5.7 are not available. Substituting

Debug output:
2024-03-08 12:13:45 [DEBUG] goroutine 249 [running]:
                            runtime/debug.Stack()
                                /opt/hostedtoolcache/go/1.21.4/x64/src/runtime/debug/stack.go:24 +0x64
                            main.panicHandler()
                                /home/runner/work/skeema/skeema/exit.go:150 +0x114
                            panic({0x102c40a60?, 0x102e325d0?})
                                /opt/hostedtoolcache/go/1.21.4/x64/src/runtime/panic.go:914 +0x218
                            github.com/skeema/skeema/internal/applier.CreatePlanForTarget(0x14000386630,
                            0x14000384090?, {0x1, 0x2, 0x0, {0x0, 0x0}, {0x0, 0x0}, 0x0, ...})
                                /home/runner/work/skeema/skeema/internal/applier/applier.go:318 +0x7d0
                            github.com/skeema/skeema/internal/applier.ApplyTarget(0x14000386630, {0x102c91fb8,
                            0x14000125200})
                                /home/runner/work/skeema/skeema/internal/applier/applier.go:164 +0x4bc
                            main.PushHandler.func1()
                                /home/runner/work/skeema/skeema/cmd_push.go:121 +0xe8
                            golang.org/x/sync/errgroup.(*Group).Go.func1()
                                /home/runner/work/skeema/skeema/vendor/golang.org/x/sync/errgroup/errgroup.go:75 +0x58
                            created by golang.org/x/sync/errgroup.(*Group).Go in goroutine 1
                                /home/runner/work/skeema/skeema/vendor/golang.org/x/sync/errgroup/errgroup.go:72 +0x98

2024-03-08 12:13:45 [ERROR] Uncaught panic in github.com/skeema/skeema/internal/applier.CreatePlanForTarget at
                            /home/runner/work/skeema/skeema/internal/applier/applier.go:318: runtime error: invalid
                            memory address or nil pointer dereference
                            This situation indicates a bug in Skeema. Use --debug to view full stack trace.
                            Please file an issue report at https://github.com/skeema/skeema/issues with any available
                            background information.

Expected behavior
It should generate the diff
Additional context
Sample table
CREATE TABLE `mytable` (
  `id` int(11) unsigned NOT NULL AUTO_INCREMENT,
  `field1` varchar(20) NOT NULL,
  `updated_at` datetime DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  PRIMARY KEY (`id`),
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

This is the exact same issue you just reported in #226. Again, under these exact conditions you will get an uncaught panic:

Target database server is running MySQL 5.7 (or anything before MySQL 8)
Client machine is a recent Mac (Apple Silicon / ARM CPU)
Skeema is configured to use workspace=docker
At least one table has a column (anywhere in your schema) that uses the legacy 3-byte utf8 character set

It does not matter what is in the diff. If these conditions are true you will get a panic from skeema diff or skeema push, it's the exact same cause as already discussed in your other issue.

Ah ok, thanks, didn't realise it was related, sorry! It's against a different database that doesn't have the 0900 collation, so I assumed it was different.


Users can't clear pending uploads through UI

Package version (if known): v9.1
Describe the bug
If upload of a file through the deposit form fails due to a network interruption or some other issue, there is no way for the user to recover. The pending upload cannot be cleared, and the record cannot be published. This can only be resolved by using the API to delete the pending uploads.
Steps to Reproduce
I do not have a good way to interrupt an upload in process. This issue happens for us infrequently with larger files.
Expected behavior
Users should be able to clear pending uploads from the uploader.
Screenshots (if applicable)

Additional context

FYI @slint this is likely to cause a lot of support requests when Zenodo migrates. We’ve had a decent number with both our v9 and v12 instances and the resulting drafts are very broken. It’s easy to run the script to clear the pending uploads, but without it being an option in the UI it becomes an annoyance for support.

Thanks for bumping this up, indeed it would probably become a major issue for support if we had to deal with these. We'll take into the current pre-launch sprint as high priority, so you should expect a fix this or next week :)

Awesome! Our clearance script is https://github.com/caltechlibrary/caltechauthors/blob/main/scripts/clear_uploads.py, though the team will probably come up with something more elegant.

Since this was a high priority a year ago - what's the status of this?

By the way, the same can be provoked when uploading a (lager) file and while file is uploading clicking the browser's back-button.


check if function exists

if you use foundationpress with a child theme, you get an error.
PHP Fatal error:  Cannot redeclare foundationpress_breadcrumb()

Hi. Can not merge as the test have failed. There seems to be 45 errors in navigation.php. Could you fix the errors and push a new commit? https://travis-ci.org/olefredrik/FoundationPress/jobs/72619330#L225

@Stevie-Ray PSR-2 violations, easily fixed if you just follow the messages. This would be very useful to get this pulled in as it causes some issues if you where to copy it from parent to child.
We noticed an alternative fix would be for you just to create a library/navigation.php file within your child theme and use that in addition to parent. Our use shows that wordpress will still use both and not overwrite on or the other. Since of course functions only exist in parent and not child.

It seems to work ok now

:+1:


Add missing dependency for //kythe/go/util/oauth2 [phab:D176]

Created by schroederc at 2015-04-14 18:24:34:

zarko accepted this revision at 2015-04-14 19:26:55

schroederc closed via commit 640dd2fe73a048e72eed15eaaf18cbed7577f482 at 2015-04-14 19:27:52


Restruct DIA-NN step 3,4,5

fixes #164

PR checklist

[ ] This comment contains a description of changes (with reason).
[ ] If you've fixed a bug or added code that should be tested, add tests!

[ ] If you've added a new tool - have you followed the pipeline conventions in the contribution docs
[ ] If necessary, also make a PR on the nf-core/quantms branch on the nf-core/test-datasets repository.

[ ] Make sure your code lints (nf-core lint).
[ ] Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
[ ] Usage Documentation in docs/usage.md is updated.
[ ] Output Documentation in docs/output.md is updated.
[ ] CHANGELOG.md is updated.
[ ] README.md is updated (including new tool citations and authors/contributors).

This comment is stopping the PR https://github.com/bigbio/quantms/issues/164#issuecomment-1120653490

LFQ failing. See my other msstats issue.

Looks VERY good from my side. The only thing I noticed, is that the results from the workflow that are uploaded in the GitHub Action (https://github.com/bigbio/quantms/actions/runs/2330274194) are 4GB for DIA 😆  We should reduce this. Do you think those are all important intermediate results? If so, we should change the config of the test profile. If not, just do not publish them with publishDir.

The converted mzML files has accounted for 4G

.

Hmm yes, we definitely don't need it in CI. We actually could skip conversion by uploading mzML files for CI (which might also make it a bit faster). I think conversion is tested in the phospho CI step already.
Let me discuss with @ypriverol about the defaults.

Can you also add IDs to some of the steps that are missing it?
[1f/58c543] Submitted process > NFCORE_QUANTMS:QUANTMS:DIA:SILICOLIBRARYGENERATION (1)
[11/e83042] Submitted process > NFCORE_QUANTMS:QUANTMS:DIA:DIANN_PRELIMINARY_ANALYSIS (RD139_Narrow_UPS1_0_1fmol_inj2)
[26/815e8d] Submitted process > NFCORE_QUANTMS:QUANTMS:DIA:DIANN_PRELIMINARY_ANALYSIS (RD139_Narrow_UPS1_0_1fmol_inj1)
[63/fb6221] Submitted process > NFCORE_QUANTMS:QUANTMS:DIA:DIANN_PRELIMINARY_ANALYSIS (RD139_Narrow_UPS1_0_25fmol_inj1)
[26/b936c2] Submitted process > NFCORE_QUANTMS:QUANTMS:DIA:DIANN_PRELIMINARY_ANALYSIS (RD139_Narrow_UPS1_0_25fmol_inj2)
[74/35cf3d] Submitted process > NFCORE_QUANTMS:QUANTMS:CUSTOM_DUMPSOFTWAREVERSIONS (1)
[05/e66ccb] Submitted process > NFCORE_QUANTMS:QUANTMS:DIA:ASSEMBLE_EMPIRICAL_LIBRARY (1)
```

Hi @daichengxin we decided that we will keep the converted mzmls by default. Can you add a config that "deletes" the publishDir in the Thermorawfileparser step for the test_dia profile?


Feature/remove ruby 2 2

Summary
Remove any Ruby 2.2 logic / tests from repo
Details
As written above
Motivation and Context
It's been EOL for ages and no cucumber gem supports 2.2 anywhere
How Has This Been Tested?
CI
Screenshots (if appropriate):
Types of changes

[x] Refactor (code change that does not change external functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[ ] I've added tests for my code
[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

2 key review points

I've not added tests for 2.6 yet, there's a branch in progress from Aslak that I may hijack after merging this in
Rubocop has been bumped from 0.58.x to 0.64.x - This is sufficient a bump to be meaningful whilst not forcing people extremely high up the tool-chain. But we probably should look to bump this up another bunch sooner rather than later.

Will merge this in as it's passed CI.
As aslak is off on his summer holidays I may have some time in a week or so to begin having a look at the Ruby 2.6 stuff. But it did seem as though some additional stuff was needed. But no idea.


Feedback for Nokia page

its not just
adb shell settings put global setting.duraspeed.enabled 0
you also need
adb shell settings put system setting.duraspeed.enabled 0
I think the system setting is the default for the boot receiver
I decompiled the code of duraspeed and found:
public static void setDuraSpeedStatus(Context context, boolean isEnable) {
System.putInt(context.getContentResolver(), "setting.duraspeed.enabled", isEnable);
Global.putInt(context.getContentResolver(), "setting.duraspeed.enabled", isEnable);
}
and this is called from the DuraSpeedMainActivity / DuraSpeedFragment when clicking the switch to activate/deactivate.
DuraSpeedMainActivity is not accessible on every device, because it has no launcher and manufactures need to add this to their settings page.

Big thanks! Added in commit 28494d056af62892b4b459df400c7af743ec5825


Add txt token

Project background:
Official announcement:
TXT is short for TRUST, which is the token issued by TXT Game Platform. TXT uses an innovative token economic design to reward contributors of TXT Platform. Hold TXT now to share 50%+ profit of TXT Platform.
official announcement link: https://twitter.com/Trust_Dice/status/1152169971637559297
Project team background:
The team is composed of game veterans and blockchain geeks (10+ games shipped in total, including 2 blockchain games). Their vision is to bring blockchain to the mass market with games, and continuously pushing the boundaries of DApp development.
Project basic information:
October ,2018： Trust Dice was launched and TXT was listed on Newdex exchange.
November, 2018：TXT mining starts
December ,2018：Lottery and Crash games were launched
Febuary, 2019:  Add chatroom, forum, and leaderboard
April, 2019: support BTC, ETH, and other ERC 20 tokens
Media publications:

https://t.me/trust_dice
https://www.linkedin.com/company/19257600/
https://www.reddit.com/r/TrustDice/
https://medium.com/@trustdice
https://discord.gg/ybsVstu
https://www.youtube.com/channel/UCnRu2PGAsDt3r9rnwQGleSA/videos
https://bitcointalk.org/index.php?topic=5126117.0
https://twitter.com/Trust_Dice
https://www.facebook.com/trustdice.win/

Tradeable exchanges:
Recommended Gas Limit (For ERC-20 project teams) for transaction: 60000

欢迎在社区中推荐用户使用 imToken 2.0 管理资产。


Changes in get_mc_id_string implementation

Summary

Accumulate the amount of bytes read and compare
it to the amount of bytes to receive. Do not
ask for more bytes if all bytes have been received

@malozanoff Supermicro's X9 servers were the one with that limitation and we have decommissioned all of them. DCIB is not pruning mc_id_strings also


more than one tikv panic repeatedly and service is unavailable when run workload and add index

Bug Report

What version of TiKV are you using?
./tikv-server -V
TiKV
Release Version:   7.5.0
Edition:           Community
Git Commit Hash:   30b578fdf20c1fd0d73a00ca26d57adb0242652f
Git Commit Branch: heads/refs/tags/v7.5.0
UTC Build Time:    2023-11-17 08:36:40
Rust Version:      rustc 1.67.0-nightly (96ddd32c4 2022-11-14)
Enable Features:   pprof-fp jemalloc mem-profiling portable sse test-engine-kv-rocksdb test-engine-raft-raft-engine cloud-aws cloud-gcp cloud-azure
Profile:           dist_release
2023-11-20T20:50:32.131+0800
What operating system and CPU are you using?
8c/32g
Steps to reproduce
tidb_enable_dist_task='on'
1、run sysbench
2、add index for one table
3、rolling restart pd
What did you expect?
add index can success and no panic
What did happened?
tikv panic repeatedly
{"container":"tikv","pod":"tc-tikv-2","level":"FATAL","namespace":"endless-ha-test-add-index-tps-4710408-1-283","log":"[lib.rs:510] ["assertion failed: !last_change_ts.is_zero()"] [backtrace="   0: tikv_util::set_panic_hook::{{closure}}\n             at home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/components/tikv_util/src/lib.rs:509:18\n   1: <alloc::boxed::Box<F,A> as core::ops::function::Fn>::call\n             at rust/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/boxed.rs:2032:9\n      std::panicking::rust_panic_with_hook\n             at rust/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:692:13\n   2: std::panicking::begin_panic_handler::{{closure}}\n             at rust/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:577:13\n   3: std::sys_common::backtrace::__rust_end_short_backtrace\n             at rust/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/sys_common/backtrace.rs:137:18\n   4: rust_begin_unwind\n             at rust/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:575:5\n   5: core::panicking::panic_fmt\n             at rust/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/panicking.rs:65:14\n   6: core::panicking::panic\n             at rust/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/panicking.rs:114:5\n   7: tikv::storage::txn::actions::common::next_last_change_info\n   8: tikv::storage::txn::actions::prewrite::PrewriteMutation::check_for_newer_version\n             at home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/src/storage/txn/actions/prewrite.rs:437:21\n   9: tikv::storage::txn::actions::prewrite::prewrite\n             at home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/src/storage/txn/actions/prewrite.rs:86:10\n  10: tikv::storage::txn::commands::prewrite::Prewriter::prewrite\n             at home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/src/storage/txn/commands/prewrite.rs:647:35\n      tikv::storage::txn::commands::prewrite::Prewriter::process_write\n             at home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/src/storage/txn/commands/prewrite.rs:535:19\n  11: <tikv::storage::txn::commands::prewrite::Prewrite as tikv::storage::txn::commands::WriteCommand<S,L>>::process_write\n             at home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/src/storage/txn/commands/prewrite.rs:250:9\n      tikv::storage::txn::commands::Command::process_write\n             at home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/src/storage/txn/commands/mod.rs:691:37\n  12: tikv::storage::txn::scheduler::TxnScheduler<E,L>::process_write::{{closure}}::{{closure}}\n             at home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/src/storage/txn/scheduler.rs:1287:21\n      tikv::storage::metrics::with_perf_context::{{closure}}\n             at home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/src/storage/metrics.rs:360:19\n      std::thread::local::LocalKey::try_with\n             at rust/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/thread/local.rs:446:16\n      std::thread::local::LocalKey::with\n             at rust/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/thread/local.rs:422:9\n      tikv::storage::metrics::with_perf_context\n             at home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/src/storage/metrics.rs:351:5\n      tikv::storage::txn::scheduler::TxnScheduler<E,L>::process_write::{{closure}}\n             at home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/src/storage/txn/scheduler.rs:1286:17\n  13: <core::future::from_generator::GenFuture as core::future::future::Future>::poll\n             at rust/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/mod.rs:91:19\n      tikv::storage::txn::scheduler::TxnScheduler<E,L>::process::{{closure}}::{{closure}}\n             at home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/src/storage/txn/scheduler.rs:1177:71\n      <core::future::from_generator::GenFuture as core::future::future::Future>::poll\n             at rust/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/mod.rs:91:19\n      <resource_metering::InTags as core::future::future::Future>::poll\n             at home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/components/resource_metering/src/lib.rs:266:9\n      tikv::storage::txn::scheduler::TxnScheduler<E,L>::process::{{closure}}\n             at home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/src/storage/txn/scheduler.rs:1191:9\n      <core::future::from_generator::GenFuture as core::future::future::Future>::poll\n             at rust/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/mod.rs:91:19\n      tikv::storage::txn::scheduler::TxnScheduler<E,L>::execute::{{closure}}\n             at home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/src/storage/txn/scheduler.rs:748:54\n      <core::future::from_generator::GenFuture as core::future::future::Future>::poll\n             at rust/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/mod.rs:91:19\n  14: <tracker::tls::TrackedFuture as core::future::future::Future>::poll::{{closure}}\n             at home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/components/tracker/src/tls.rs:64:23\n      std::thread::local::LocalKey::try_with\n             at rust/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/thread/local.rs:446:16\n      std::thread::local::LocalKey::with\n             at rust/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/thread/local.rs:422:9\n      <tracker::tls::TrackedFuture as core::future::future::Future>::poll\n             at home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/components/tracker/src/tls.rs:62:9\n      tikv_util::yatp_pool::future_pool::PoolInner::spawn::{{closure}}\n             at home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/components/tikv_util/src/yatp_pool/future_pool.rs:178:27\n      <core::future::from_generator::GenFuture as core::future::future::Future>::poll\n             at rust/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/mod.rs:91:19\n      yatp::task::future::RawTask::poll\n             at rust/git/checkouts/yatp-e704b73c3ee279b6/5572a78/src/task/future.rs:59:9\n  15: yatp::task::future::TaskCell::poll\n             at rust/git/checkouts/yatp-e704b73c3ee279b6/5572a78/src/task/future.rs:103:9\n      <yatp::task::future::Runner as yatp::pool::runner::Runner>::handle\n             at rust/git/checkouts/yatp-e704b73c3ee279b6/5572a78/src/task/future.rs:387:20\n  16: <tikv_util::yatp_pool::YatpPoolRunner as yatp::pool::runner::Runner>::handle\n             at home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/components/tikv_util/src/yatp_pool/mod.rs:199:24\n  17: yatp::pool::worker::WorkerThread<T,R>::run\n             at rust/git/checkouts/yatp-e704b73c3ee279b6/5572a78/src/pool/worker.rs:48:13\n      yatp::pool::builder::LazyBuilder::build::{{closure}}\n             at rust/git/checkouts/yatp-e704b73c3ee279b6/5572a78/src/pool/builder.rs:114:25\n      std::sys_common::backtrace::rust_begin_short_backtrace\n             at rust/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/sys_common/backtrace.rs:121:18\n  18: std::thread::Builder::spawn_unchecked::{{closure}}::{{closure}}\n             at rust/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/thread/mod.rs:551:17\n      <core::panic::unwind_safe::AssertUnwindSafe as core::ops::function::FnOnce<()>>::call_once\n             at rust/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/panic/unwind_safe.rs:271:9\n      std::panicking::try::do_call\n             at rust/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:483:40\n      std::panicking::try\n             at rust/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:447:19\n      std::panic::catch_unwind\n             at rust/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panic.rs:137:14\n      std::thread::Builder::spawn_unchecked::{{closure}}\n             at rust/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/thread/mod.rs:550:30\n      core::ops::function::FnOnce::call_once{{vtable.shim}}\n             at rust/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ops/function.rs:513:5\n  19: <alloc::boxed::Box<F,A> as core::ops::function::FnOnce>::call_once\n             at rust/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/boxed.rs:2000:9\n      <alloc::boxed::Box<F,A> as core::ops::function::FnOnce>::call_once\n             at rust/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/boxed.rs:2000:9\n      std::sys::unix::thread::Thread::new::thread_start\n             at rust/toolchains/nightly-2022-11-15-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/sys/unix/thread.rs:108:17\n  20: start_thread\n  21: __clone3\n"] [location=components/txn_types/src/types.rs:611] [thread_name=sched-worker-pool-1] [thread_id=0x5]"}

/type bug
/severity critical

refer to #48804


Tables too wide on Visualizer reference page

See https://numberscope.colorado.edu/doc/doc/behind-the-scenes/ where a lot of horizontal scrolling has to happen to read all of the information.
It would be best if the descriptions line-wrapped in table columns of fixed width.
One possible solution might be to install and use  https://pypi.org/project/markdown-grid-tables/
Alternately, there might be an HTML/CSS solution that limited the width of these table elements, and then maybe the columns would just adjust to reasonable widths. But the we might also need to somehow (manually?) insert <p> elements in the description cells.

PR #486 abandons tables for this information in favor of definition lists -- there just seemed to be too mich information per item for a table. So this will become moot


how to train a coco pretrained model by myself?

Recently, I try to use cascade RCNN(https://github.com/guoruoqian/cascade-rcnn_Pytorch) in my own dataset. However it only has imagenet pretrained model, without pretrained model in MScoco. Can someone know how to train a pretrained model in MScoco dataset? I only have 2 1080Ti.
And the pretrained model just means the CNN model's parameters, right?

I wonder how do you get the resnet-101 pretrained model that you have prepared in Ms CoCo dataset?

I wonder how do you get the resnet-101 pretrained model in Ms CoCo dataset?


Add Export to JSON option

Currently, we support Export to Text File and Export to PDF options. Similarly we want to add support for exporting notes to JSON. Reason for adding is we want to support exporting of notes from one device and import it into another device, JSON is easy to process in such cases.
Tasks

[ ] You can refer the exportNotesToTextFile function in lib/features/notes/data/repositories/export_notes_repository.dart. Similarly add exportNotesToJsonFile function in same class.
[ ] Display another settings tile Export to JSON File and call the exportNotesToJsonFile function

I would like to work on this issue. Could you please add the Hacktoberfest label and assign it to me?

Hi @vprathap21 , you can pick this, I have added hacktoberfest topic to repo itself so all PRs will be counted

@vprathap21 are you working on this?

Sure @AyushJagaty


Using typescript with ctxmenu - TypeError: this.cy.ctxmenu is not a function

I get TypeError: this.cy.ctxmenu is not a function when trying to add ctxmenu to cytoscape graph.
import * as cytoscape from 'cytoscape';
import * as ctxmenu from 'cytoscape-cxtmenu';

... removed for brevity ...
        this.cy = cytoscape({
            container: this.cytoscapeElem.nativeElement,
            elements: [
                { data: { id: 'a' } },
                { data: { id: 'b' } },
                { data: { id: 'ab', source: 'a', target: 'b' } }
            ],
            style: [
                {
                    selector: 'node',
                    style: {
                        'background-color': '#666',
                        'label': 'data(id)'
                    }
                },
                {
                    selector: 'edge',
                    style: {
                        'width': 3,
                        'line-color': '#ccc',
                        'target-arrow-color': '#ccc',
                        'target-arrow-shape': 'triangle'
                    }
                }
            ],
            layout: {
                name: 'cose'
            }
        });

        let defaults = {
            menuRadius: 100, // the radius of the circular menu in pixels
            selector: 'node', // elements matching this Cytoscape.js selector will trigger cxtmenus
            commands: [ // an array of commands to list in the menu or a function that returns the array
              /*
              { // example command
                fillColor: 'rgba(200, 200, 200, 0.75)', // optional: custom background color for item
                content: 'a command name' // html/text content to be displayed in the menu
                contentStyle: {}, // css key:value pairs to set the command's css in js if you want
                select: function(ele){ // a function to execute when the command is selected
                  console.log( ele.id() ) // `ele` holds the reference to the active element
                },
                enabled: true // whether the command is selectable
              }
              */
            ], // function( ele ){ return [ /*...*/ ] }, // example function for commands
            fillColor: 'rgba(0, 0, 0, 0.75)', // the background colour of the menu
            activeFillColor: 'rgba(1, 105, 217, 0.75)', // the colour used to indicate the selected command
            activePadding: 20, // additional size in pixels for the active command
            indicatorSize: 24, // the size in pixels of the pointer to the active command
            separatorWidth: 3, // the empty spacing in pixels between successive commands
            spotlightPadding: 4, // extra spacing in pixels between the element and the spotlight
            minSpotlightRadius: 24, // the minimum radius in pixels of the spotlight
            maxSpotlightRadius: 38, // the maximum radius in pixels of the spotlight
            openMenuEvents: 'cxttapstart taphold', // space-separated cytoscape events that will open the menu; only `cxttapstart` and/or `taphold` work here
            itemColor: 'white', // the colour of text in the command's content
            itemTextShadowColor: 'transparent', // the text shadow colour of the command's content
            zIndex: 9999, // the z-index of the ui div
            atMouse: false // draw menu at mouse position
        };

        this.cy.ctxmenu(defaults);

Same issue

Is there a cytoscape.use(ext) after import?

Hi maxkfranz,
yes, the code's structure is similar to the author's one with cytoscape.use(ext) in it.
in component side:
import * as cytoscape from 'cytoscape';
import * as cxtmenu from 'cytoscape-cxtmenu';
cytoscape.use(cxtmenu);

in typings.d.ts:
declare module 'cytoscape-cxtmenu';
in angular.json scripts are also included.
It does not see cy.ctxmenu();
Thank you for your help!

If the TS import is the same as the ES import, then you need to use the default export rather than *.

import cytoscape from 'cytoscape';
import cxtmenu from 'cytoscape-cxtmenu';

cytoscape.use( cxtmenu );

I have same issue. I have error message in visual sutido code "Property 'cxtmenu' does not exist on type 'Core'". Is it possible use it in typescript? I try add to index.d.ts this:
declare module 'cytoscape-cxtmenu' {
const ext: cytoscape.Ext;
export = ext;
}
But still not working.

Isn't it because it's cxtmenu and not ctxmenu?

I managed to use cytoscape.js-context-menus extension (https://github.com/iVis-at-Bilkent/cytoscape.js-context-menus) on angular 7 project.
I added "node_modules/cytoscape-context-menus/cytoscape-context-menus.css" to styles of the project inside angular.json file and use it as suggested

I managed to use cytoscape.js-context-menus extension (https://github.com/iVis-at-Bilkent/cytoscape.js-context-menus) on angular 7 project.
I added "node_modules/cytoscape-context-menus/cytoscape-context-menus.css" to styles of the project inside angular.json file and use it as mentioned in the readme of the extension

I did the same but its still giving me error this.cy.contextMenu() is not a function in angular 7.

I have same issue, when trying to integrate ctxmenu in my angular project.
So, the issue is closed, but I could not understand the solution.
Please help me !

import cxtmenu from 'cytoscape-cxtmenu';
cytoscape.use(cxtmenu);
...
let cy = cytoscape({ opt });
cy.cxtmenu({ cxtOpt });
Can not register cxtmenu for core since cxtmenu already exists in the prototype and can not be overridden
Alternative
let cy = cytoscape({ opt });
cy.cxtmenu({
selector: 'node, edge',
...
Uncaught (in promise) TypeError: cy.cxtmenu is not a function
I haven't had any luck.
I am using Svelte & Sapper. I have the graph working fine without cxtmenu, adding it in, it breaks. Any feedback would help!

So, was anyone able to come up with a solution?

Had the same issue. Solved it by calling cxtmenu not on the module but on the instance of cytoscape.


Mesh local address communication fails eventually

We observe a strange behavior where our nodes stop sending packets to NCPs Mesh local address. This is a rare case but as we have 140 hardware nodes setup it happens lets say once a day on a single device. Power reboot fixes the issue and normal communication comes back. Before the reboot we can see problem persisting for days.
Deeper investigation on a failed node showed that:

it is alive, and CLI works fine
sending packets to the same destination using RLOC instead of Mesh Local works fine
sending packets to the same destination using ALOC works fine
sniffer showed that the node is not even trying to send anything when Mesh Local is used as a destination. No packets translated to RLOC nor /a/aq to get the RLOC from ML
all other (139) nodes send packets to the same Mesh Local address just fine

I did tests with ping command sent from CLI and a sniffer sitting close to a problematic device.

ping fd3c:9b17:1634:0:0:ff:fe00:4c00   (pcap frame 104739)
16 bytes from fd3c:9b17:1634:0:0:ff:fe00:4c00: icmp_seq=23 hlim=64 time=31ms
ping fd3c:9b17:1634:0:fd33:96eb:becc:8097
ping fd3c:9b17:1634:0:fd33:96eb:becc:8097
ping fd3c:9b17:1634:0:fd33:96eb:becc:8097
ping fd3c:9b17:1634:0:0:ff:fe00:4c00  (pcap frame 108632)
16 bytes from fd3c:9b17:1634:0:0:ff:fe00:4c00: icmp_seq=30 hlim=64 time=38ms

Attaching sniff screen and all commands executed in CLI. I've got full 12MB, 30 min sniff from that setup and there was a big mess (lots of reparenting and connection problems) during that time. This could be also interesting for you. Can share on a separate channel if needed.

no_ml_commnads_used.txt

@mwilniewiec, thank you for raising this issue.
I wonder if this is related to the EID-to-RLOC cache. Are you able to provide the output of the eidcache CLI command?

From what I see our nodes have only 1 entry in the eidcache which is reasonable:
eidcache
fd3c:9b17:1634:0:fd33:96eb:becc:8097 201d
Done

This is ML-EID of our NCP and the only EID used by our application.
NCP on the other hand has lot of entries in Thread:AddressCacheTable property and it acts a bit strange, Im currently investigating it.
Sometimes it returns ~100 entries, sometimes it freezes for a few seconds and returns Thread:AddressCacheTable:  (7)
It seems that the table is dropped too many times on our NCP.

From what I see our nodes have only 1 entry in the eidcache which is reasonable:
eidcache
fd3c:9b17:1634:0:fd33:96eb:becc:8097 201d
Done

This is ML-EID of our NCP and the only EID used by our application.

Does the RLOC16 match what you expect on the NCP?

NCP on the other hand has lot of entries in Thread:AddressCacheTable property and it acts a bit strange, Im currently investigating it.
Sometimes it returns ~100 entries, sometimes it freezes for a few seconds and returns Thread:AddressCacheTable: <empty> (7)
It seems that the table is dropped too many times on our NCP.

The EID-to-RLOC cache gets cleared any time the NCP resets or reattaches to the network. Are you able to enable NCP logs and provide the log output from wpantund?

The problem occurred one more time so I was able to do more investigation.
For a failed node we have:

empty eidcache -  (other nodes have valid NCP EID->RLOC entry)
pings to NCP RLOC work ~ 80% of the time
pings to NCP ML-EID are not working as described in the bug

The most important part I found and I think is the clue is the buffer info:
bufferinfo
total: 128
free: 2
6lo send: 0 0
6lo reas: 0 0
ip6: 0 0
mpl: 0 0
mle: 0 0
arp: 0 0
coap: 0 0
coap secure: 0 0
application coap: 63 126
Done

Does it mean that our application coap filled all the buffers and there is no more room for a/aq ?
I will surely have to look deeper into that problem.

From what I see a/aq is a NON_CONFIRMABLE message so full buffers shouldn't be a problem in that case. I have a new feeling:
From what I see there is a 15 sec retry with 2* backoff on address resolver with max retry delay = 8 hours.
There could be a situation where in high packet loss environment this backoff is so big that we are waiting several minutes / hours to send next a/aq. Sniffer as described previously wouldn't show any ICMP as EID is not known and isn't showing a/aq as we are waiting for the next timer which can take half an hour.
Does is make sense? Do you know any easy way to confirm that?
I can see that most of our problems lead us to the same thing: losing lots of packets and losing links between nodes.
PS. I also checked full buffers problem on such node and it's another mystery. This node wasn't sending app coap messages for at least 3 minutes. After that time send confirmable coap failed with No buffers error. We have default timeouts for coap so queue should be empty after maximum 93 seconds but it wasn't.

From what I see a/aq is a NON_CONFIRMABLE message so full buffers shouldn't be a problem in that case. I have a new feeling:
From what I see there is a 15 sec retry with 2* backoff on address resolver with max retry delay = 8 hours.
There could be a situation where in high packet loss environment this backoff is so big that we are waiting several minutes / hours to send next a/aq. Sniffer as described previously wouldn't show any ICMP as EID is not known and isn't showing a/aq as we are waiting for the next timer which can take half an hour.
Does is make sense? Do you know any easy way to confirm that?

Yes, we have seen this in practice. In Google Nest products, we actually configure ADDRESS_QUERY_MAX_RETRY_DELAY to 120 seconds (overriding the 8 hours stated in the Thread Specification). See similar discussion in https://github.com/openthread/openthread/issues/4542#issuecomment-584758632.

I changed 8 hours to 240 sec in our project. I was considering your 120 suggestion but as we have more than 120 nodes in a single network I would prefer to avoid multicast every second.
At the end we plan to remove (nodes->ncp) ML-EID communication and use service ALOCs instead as no extra multicasts are needed but we still have problems with invalid servers in network data. #4768 reported yesterday.
I have a feeling that the original problem is much deeper but reported issue seems to be an expected behavior, closing for now.


[Discovery] Query Results not available in Javascript (AuraEnabled)

Problem
When I write the code like the following:
String environmentId = 'myEnvironmentId';
List<String> collectionIDs = new List<String>();
collectionIDs.add('collectionId1');
collectionIDs.add('collectionId2');
String query = 'my query';

IBMDiscoveryV1 discovery = new IBMDiscoveryV1(IBMDiscoveryV1.VERSION_DATE_2017_09_01);
IBMDiscoveryV1Models.FederatedQueryOptions options = new IBMDiscoveryV1Models.FederatedQueryOptionsBuilder(environmentId, collectionIDs).naturalLanguageQuery(query).build();

System.debug(discovery.federatedQuery(options).getResults());

I get the following response:
[
  {
    "id": "my_id",
    "score": 1.0,
    "collection_id": "my_collection_id",
    "additional_properties" : {
       //more fields here
    }
  }
]

However, when I try to access the same response in Javascript (aura) layer with the following code:
action.setParams({
    "environmentId": "myEnvironmentId",
    "collectionIDs": ["collectionId1", "collectionId2"],
    "query": "my query"
});
action.setCallback(this, function(response) {
    var resp = response.getReturnValue();
    console.log(resp.results);
});
$A.enqueueAction(action);

I get the following:
[
  {
    "id": "my_id",
    "score": 1.0,
    "collection_id": "my_collection_id"
  }
]

Expected
I expect to be able to retrieve the following response for both situations:
[
  {
    "id": "my_id",
    "score": 1.0,
    "collection_id": "my_collection_id",
    //more fields here
  }
]

(specifically, no additional_properties object)
Solution
I believe an @AuraEnabled flag needs placed somewhere on the dynamic models for the parent class of IBMDiscoveryV1Models.QueryResult. Not exactly clear where.

Some of the restrictions for adding an @AuraEnabled flag that currently pose a challenge for the dynamic part of the models include:

Parameters cannot be passed into non-static methods
the keyword get needs to be present for instance methods, from here the method deserialize would become getDeserialize therefore not having a virtual declaration on the base class IBMWatsonDynamicModel

In the meantime the dynamic part of the models are adjusted to be visible from Lightning, a workaround could be returning just a String from the action using this code
return JSON.serialize(discovery.federatedQuery(options).getResults());
From the client or the lightning component, then do the reverse operation,
var QueryResultList = JSON.parse(response.getReturnValue());

A negative side effect of the serialize/parse approach is that every single resulting field gets _serialized_name appended to it because Apex uses the class variable names as keys.

FYI, to go along with what @benjdewan was saying, the approach suggested actually outputs a rather unusable JSON string.
Example, given a query result from WDS like this:
{
  "id": "d3bc1fbb27320771e436af4c48b8e9e49835930f47a1fac65cbfc4280d0ce268",
  "score": 0.13112299,
  "collection_id": "7f6b6c22-db23-4626-93d5-81b53b98f9fd",
  "metadata": null,
  "CASENUMBER": "00001001",
  "STATUS": "Closed",
  "ISCLOSED": "true",
  "ROWID": "500f0000007AmhlAAC",
  "extracted_metadata": {
    "sha1": "6b095bc7b521452cd5f9e60ae841ab2956969095",
    "filename": "filename",
    "file_type": "json"
  },
  "SUBJECT": "Performance inadequate for second consecutive week",
  "REASON": "Performance",
  "OBJECT_TYPE": "CASE",
  "CLOSEDDATE": "2016-09-19 14:59:51.0"
}

the workaround approach produces this:
{
  "additional_properties": {
    "CASENUMBER_serialized_name": "00001001",
    "STATUS_serialized_name": "Closed",
    "ISCLOSED_serialized_name": "true",
    "ROWID_serialized_name": "500f0000007AmhlAAC",
    "extracted_metadata_serialized_name": {
      "sha1_serialized_name": "6b095bc7b521452cd5f9e60ae841ab2956969095",
      "filename_serialized_name": "filename",
      "file_type_serialized_name": "json"
    },
    "SUBJECT_serialized_name": "Performance inadequate for second consecutive week",
    "REASON_serialized_name": "Performance",
    "OBJECT_TYPE_serialized_name": "CASE",
    "CLOSEDDATE_serialized_name": "2016-09-19 14:59:51.0"
  },
  "score_serialized_name": 0.13112299,
  "metadata_serialized_name": null,
  "id_serialized_name": "d3bc1fbb27320771e436af4c48b8e9e49835930f47a1fac65cbfc4280d0ce268",
  "collection_id_serialized_name": "7f6b6c22-db23-4626-93d5-81b53b98f9fd"
}


✨ Added shift tracker

Adds a tracker for your shifts, defaults to 8 hours, and can be used with the --shift option.

Looks amazing!
Hear me out: what if it could show me how much of my 8 hours shift is left from when I first turn on the computer?
- u/HoboWarZ

Build from CI: Time Left.zip


Error: Cannot find module 'agario-client'

Hello,
I try to run the script. I followed all the steps.
I wanted to know if we needed the agario-client module?
When launching the  "node feeder.js", I get the following error: "Error: Can not find module agario-customer"
Thanks for your help.

npm install agario-client

Thank you hairnet.
I miss a lot of node modules; you have a tip to avoid installing them one by one?


HDsys.ibm

Operational test

Operational test

Hello, is there anything you might want to discuss with me, perhaps a change or how to make it better


QSB support

Feature
It would be great if this was QSB compatible so we could co-op the vision mod.
Context
There's probably a good reason it's not supported but I haven't seen an answer.

we're working on it https://github.com/Outer-Wilds-New-Horizons/nh-qsb-compatibility

thanks!

Is there anything that could be helped with?

Most of the issues are on the QSB end, right now it works well enough there's just weird bugs with Epic transport or smthng. You can try asking them about it, either on their repo or the modding Discord server linked on the website https://outerwildsmods.com/

closing this as qsb nh support is not feasible anymore


[Error] Internal error processing T2I request: System.NullReferenceException: Object reference not set to an instance of an object.

When using a custom workflow I get the following error
 08:02:45.977 [Error] Internal error processing T2I request: System.NullReferenceException: Object reference not set to an instance of an object.    at StableSwarmUI.Builtin_ComfyUIBackend.ComfyUIAPIAbstractBackend.<>c__DisplayClass13_1.<<GetAllImagesForHistory>g__LoadImage|0>d.MoveNext() in W:\SDXL-Apps\Swarm\2023-10-07\StableSwarmUI\src\BuiltinExtensions\ComfyUIBackend\ComfyUIAPIAbstractBackend.cs:line 294 --- End of stack trace from previous location ---    at StableSwarmUI.Builtin_ComfyUIBackend.ComfyUIAPIAbstractBackend.GetAllImagesForHistory(JToken output, CancellationToken interrupt) in W:\SDXL-Apps\Swarm\2023-10-07\StableSwarmUI\src\BuiltinExtensions\ComfyUIBackend\ComfyUIAPIAbstractBackend.cs:line 311    at StableSwarmUI.Builtin_ComfyUIBackend.ComfyUIAPIAbstractBackend.AwaitJobLive(String workflow, String batchId, Action1 takeOutput, CancellationToken interrupt) in W:\SDXL-Apps\Swarm\2023-10-07\StableSwarmUI\src\BuiltinExtensions\ComfyUIBackend\ComfyUIAPIAbstractBackend.cs:line 265
at StableSwarmUI.Builtin_ComfyUIBackend.ComfyUIAPIAbstractBackend.GenerateLive(T2IParamInput user_input, String batchId, Action1 takeOutput) in W:\SDXL-Apps\Swarm\2023-10-07\StableSwarmUI\src\BuiltinExtensions\ComfyUIBackend\ComfyUIAPIAbstractBackend.cs:line 510    at StableSwarmUI.Text2Image.T2IEngine.CreateImageTask(T2IParamInput user_input, String batchId, GenClaim claim, Action1 output, Action1 setError, Boolean isWS, Single backendTimeoutMin, Action2 saveImages, Boolean canCallTools) in W:\SDXL-Apps\Swarm\2023-10-07\StableSwarmUI\src\Text2Image\T2IEngine.cs:line 178
08:02:45.977 [Debug] Refused to generate image for local: Something went wrong while generating images.
`
The base install of swarm works fine, generated and saved an image no problem. Loaded up a custom workflow that I've been using in comfy and it gives the above error.
disregard the date in the file name, I just updated swarm this morning.
Any ideas on what in my workflow could be causing this error? I have a bunch of custom_nodes going, some might be incompatible?

disregard the date in the file name, I just updated swarm this morning. when was 'this morning'? The relevant section of code changed earlier today and also changed yesterday.
Is this a Comfy API-by-URL or Self-Start backend? (Self-Start is the default if you didn't customize backends) (Self-Start is the better option)
Do you have any custom nodes that are saving outputs? Specifically other than the standard PreviewImage/SaveImage nodes.
Are there any errors coming out of Comfy? Since you appear to have LogLevel set to Debug they should show in console.
If none of the above leads to the answer, could you post your workflow file?

Thanks for the reply.  This morning was a couple hours ago. 7:30am-ish eastern us time on 10-25. I will re-update again just in case.
The error happens both in the self-start and the url. Will look at my custom nodes that may be saving any outputs and look deeper in the logs.

Well I feel dumb. There was a typo in the swarmui settings for my clipvision folder. Folder didn't exist.
Fixed the setting and all is well.


GitHub repository config includes broken demo URL

GitHub shows http://ember-signature-pad.divshot.io as project URL but that one is broken. It should be changed to https://ember-signature-pad.firebaseapp.com/.

This has been updated.


Add support for generic namespaces

As an improvement for Catch, I would like to suggest support for generic feeds and namespace naming, instead of it being strictly specific to showRSS.
This means:

Instead of checking the URL format, check the content of the given URL to see if it is a valid format
Accepting generic namespace tags, in addition to the ones that are currently support.

The proposed namespace tags are:

tv:show_id (equivalent to showrss:showid)
tv:show_name (equivalent to showrss:showname)
tv:episode_id (equivalent to showrss:episode)
tv:raw_title (equivalent to showrss:rawtitle)
tv:info_hash (equivalent to showrss:info_hash)

Thanks! :)

Done in 780d57f84fa4f06831848704c3fbca35a54438f5 and c1548579a630f5ebb4cf168ea33a8afff65e2131


Add support for .html suffix to the paths when the file doesn't exist but the .html does

Currently, certain static site generators generate the following files when generating the public folder (such as the popular next.js and others):
/posts.html
/posts/my-first-article.html
/posts/my-second-article.html

This is the case, for example, when using Next.js for generating the Wasmer website (you can run the build locally with npm run build and inspect the out directory).
This worked great when deploying to places such as Netlify, Vercel or Cloudflare Pages. They all allow accessing those pages to the urls:
/posts
/posts/my-first-article
/posts/my-second-article

Here are the route-matching rules in Cloudflare: https://developers.cloudflare.com/pages/platform/serving-pages/#route-matching

For example, here's the page https://wasmer.io/posts/WAI-is-the-answer which returns the content from /posts/WAI-is-the-answer.html.
Now, we want to move from Netlify or Cloudflare Pages to our own servers using static-web-server, but currently https://localhost:9000/posts or https://localhost:9000/posts/WAI-is-the-answer return 404 in the Static Web Server.
Proposed solution
The proposed solution would be, in case /posts is not found (nor /posts/index.html) try to resolve /posts.html.

This can be closed as #180 is now merged in master :)


modules: tfm: Exclude non-secure TF-M application from build

Exclude the non-secure TF-M application from being built by TF-M.
This also stops the building of the tfm_ns_api library that we were
linking against.
This library is defined by the tf-m regression tests.
Add the installed interface source files exported by the TF-M build
system compile them in the zephyr build system.
Signed-off-by: Joakim Andersson<EMAIL_ADDRESS>

@tejlmand Exluding the Non-Secure application wasn't as trivial as it first seemed.
The two libraries tfm_api_ns and platform_ns was not available to be linked against.
From what I can see the tfm_api_ns is the library that we actually needed. It was created by the test repository, so it makes most sense to compile it ourselves from the source files that are exported.
The platform_ns still has some definitions that we need, but most of it should be exluded.
Things like nrfx_glue should be coming from zephyr, not TF-M for the non-secure.
However the IOCTL functions are needed, so will have to resolve the organization of these with the TF-M project.
Is there a way we could build all of the *.c source files that are present in the folder?
TF-M build system exports the ones that are required based on the configurations.
Since some of the configurations are internal, like multicore support, we need to have access to the TF-M configurations or duplicate it. Or just build all of the files given.

Update:
Fixed build errors related to the tfm_psa_test sample / test. This required to link against some of the libraries that are built as part of the non-secure, but still not have the non-secure application running.
For this reason there is a separate kconfig for building NS, and using the NS app.

@microbuilder Yeah, thanks for checking, that was my conclusion as well.
The DNM label is because the west.yml is pointing to a dependent PR, which has to be merged first, and the west.yml needs to point to a SHA. This was automatically added by the zephyrbot.

@joerchan Merged https://github.com/zephyrproject-rtos/trusted-firmware-m/pull/73 if you want to update the manifest here.

@carlescufi Anyone on your side that can do a second review here for the missing +1?

@joerchan CI failures seem unrelated to PR.


Update docs with alternative to bcyprt-cli which is now deprecated

Our documentation currently recommends the use of https://github.com/bitnami/bcrypt-cli/ here:

https://docs.gitops.weave.works/docs/getting-started/#configure-access-to-the-dashboard
http://localhost:3000/docs/next/configuration/securing-access-to-the-dashboard/#login-via-a-cluster-user-account

bcyrpt-cli has recently been marked as read-only and deprecated, with alternatives suggested here https://github.com/bitnami/bcrypt-cli/issues/15.
As a follow up / alternatively, we could consider whether the gitops CLI could provide a command to configure this within the helm chart / secret.

I /think/  htpasswd -nbBC10 n/a password | cut -d ':'  -f2 should be an appropriate replacement (and not require installing anything else).


Is this bundle dead?

@baldurrensch do you have any interest in keeping this bundle up to date?

:(

A few things:

Alice does not scale well for a large fixture data set. We use it some places, but have moved to a different system that handles our large data set better.
The person who wrote this bundle, @baldurrensch , is at a different company.

If someone wants to help maintain this bundle, we can ceratainly provide write access or we will support a fork.

Thanks for your answer @hjr3.
Well, IMO there is several issues:

generators are kept internal to loaders making it difficult to share the same instance of Faker (which might be useful if you wish to set a specific seed)
keeping the generators internal doesn't make really sense since most providers needs to be injected a faker instance to be instantiated and we inject directly providers to loaders
the responsibility of the DataFixturesLoader is not clear: it behaves as both a Doctrine fixtures interface and a provider
defining custom providers outside the DataFixturesLoader, like Faker's providers, is not simple

Some issues make it difficult to scale it for large set of data, which is a pity since a really useful system to play with different set of data, for testing, integration and production purpose.
Regardless of some design issues, the lack of reactivity for this bundle and nelmio/alice is definitely a problem. This topic really interest me and I would happily help to develop and maintain this bundle. But some changes would be far from trivial and I'm by no means a senior developer, so it would still require the guidance of some people :)
That being said, while I was looking around thinking of how to redesign this bundle, I've came accross KnpLabs/rad-fixtures-load, much more recent. There is a few things I'm not really happy with and that I would like to change, but it's definitely something worth to check over.
What do you think of it @hjr3? Would it be best to try to change this bundle to achieve our goals or would it be better to try to enhance KnpLabs/rad-fixtures-load?
cc @dunglas, @PedroTroller

If Knp is supporting that repo, then I think we should partner with them to improve that one.

Well, we don't have much visibility about how the bundle will evolves and be managed for now but maybe @PedroTroller will enlighten us :)
Anyway I should still do a PR for this bundle to change a few things that make it easier to define custom faker data providers.

Hi @hjr3.
I don't think that the idea of Alice is to provide a system to load a huge amont of data. I'm a supporter of really simple components for really simple tasks.
I think, if you have problems with data loading ascalability and resource dependencies, you don"t have to use Alice, it's not designed for this kind of problems. And so, you don't have to use the rad-fixtures-load.

That being said we have some projects were it handles well a fair amount of data (over 100 fixtures files) for dev/inte/prod usage. For now it's doing well. Where I find it lacking is when it comes to custom data providers which we want to completely extract from the DataFixturesLoader to keep things maintainable and not too messy.

@hjr3 there is a lot of changes with the version ~2.0 of nelmio/alice. I think an upgrade will really help it. I'll try to upgrade it on my fork and will do a PR for that :)

@hjr3 could you take a look at theofidry/AliceBundle? There is still lots of things to do/check but that's the gist of it, the upgrade of nelmio/alice changes lots of things but it's a very great upgrade.


Add a loading animation when loading page.

When refreshing the page, and messages are being loaded, it just says "loading..." next to the zulip logo, having a nice loading animation would improve the experience in my opinion. The animation can be used for many things like when an image is loading or similar. I will be working on it.

cc @brockwhittaker
https://chat.zulip.org/#narrow/stream/GCI.20general/subject/animation/near/392976

@Tanonic  You can claim the issue by commenting @zulipbot claim

@zulipbot claim

@zulipbot claim

On it! :)

@zulipbot claim


[SUGGESTION]  Leave Job Confirmation

Hello ! I have some things at suggest to you:

Add a confirmation message for leaving a job for example: "Are you sure to leave your job? Type Yes or No"

Add more possibility in lang.yml, for modify "minecraft days" for example ^^

Nice day at you !

Hello, about the second suggestion, I really think It is already added. You can just go to your language file and delete the time translations. Minecraft does not have a translation so it is not added to the file.


comments on Amsterdam Call for Action on Open Science

with @gwenfranck https://docs.google.com/document/d/1vDsQhgygHS_cctuP2dQOfIbT-LPyBQfgres5VQ3G39s/edit

submitted by @gwenfranck. i'd like for CC to do a blog post on this to explain our comments.

https://docs.google.com/document/d/1NVamkmBinhlWH33szpfh0yMCJAU5EumVyYkmpC4iu7g/edit

done https://blog.creativecommons.org/2016/05/03/europe-moving-right-direction-support-open-science/


Unable to verify Unreal EULA

Describe the bug
When attempting to verify the Unreal EULA, a top pops up in my browser, I accepted the EULA, but I still cannot install Unreal Engine. The button is grayed out.
To Reproduce
Steps to reproduce the behavior:
Click on the Green + that says Install Engine,
Click on the Life  Ring to sign the EULA
Sign the EULA
Re-open Epic Asset Manager, and the button is still grayed out. I clicked refresh in the top left, clicked revalidate next to the life ring, and even signed out and back in again and I am still unable to click the button.
Expected behavior
I expected to be able to download Unreal Engine after signing the EULA
Desktop (please complete the following information):

OS: Debian
Browser Firefox
Version Debian 12

Duplicate of #249, sadly Epic did lock down the verification there, so far I have not been able to bypass it, though I do have a "workaround" in the works, need to figure out last couple bits. I will close this in favour of the other issue.


Fix unuran builds for older compilers

Reference issue

What does this implement/fix?

Additional information

cc @tirthasheshpatel, @chrisb83, @rgommers
Otherwise builds fail with undefiend symbol isfinite.
See https://dev.azure.com/numpy/numpy/_build/results?buildId=19164&view=results

Did you try to build with ("HAVE_DECL_ISFINITE", "0") on line 75?

Nope. I don't have a scipy build locally and just trying at https://github.com/MacPython/scipy-wheels. As you can see, the CI there is failing.

I have proposed #14632 to see if SciPy builds with definitions for C99 functions removed. @isuruf If you can locally replicate the failures on MacPython/scipy-wheels, try to build it with #14632.
@mckib2 would you be able to help confirm this and gh-14632?

@tirthasheshpatel, I redid the PR


Set deployment target to iOS 9

Related issues:

FH-3923 - Set deployment target to iOS 9 on helloworld-ios
FH-3948 - Move helloworld-ios from Travis CI to CircleCI

@jcesarmobile Done!


'profile active get' does not work

| # ratbag-command profile active get
| Error: Can't open 'get': Invalid argument
| Error: Device 'get' is not supported

closing, can't fix without info


Libmath Import Error

I am getting this error when running the script. Checked everyting and followed all steps:
python3 Object_detection_picamera.py
Traceback (most recent call last):
File "Object_detection_picamera.py", line 23, in
import cv2
File "/usr/local/lib/python3.7/dist-packages/cv2/init.py", line 5, in
from .cv2 import *
ImportError: libImath-2_2.so.23: cannot open shared object file: No such file or directory

Hello, I have a similar issue, have you found a solution yet?


undefined passes enum test

I have this:
revalidator.validate({foo: undefined}, {
    properties: {
        foo: {
            enum: ['foo', 'bar'],
            type: 'string',
        },
    },
});

Which doesn't generate any error, surely undefined is not ['foo', 'bar'] nor is it a string, shouldn't this throw an error?

Only if you have required: true in the schema for foo.

I tried with required but IIRC it passed as well, I had to convert the rule to a pattern: '(foo|bar)' currently


If I upgrade from 3.8.0 to anything else, the page breaks.

Hi,
I've not visited here for a while, but I thought I'd see if there has been any developments, and there really has!
My glossary is using 3.8.0, and if I change it too anything more recent than that, I just get a page saying "Glossary Page Template
This page includes a web interface..."
Clearly I've done something wrong, but what is it?!  Thanks.
Gray

I haven't been able to reproduce this yet, unfortunately -- are you hosting the static assets yourself or pointing to glstatic.net? Can you maybe share the glossary file and/or the steps you were following to upgrade in more detail please?

I'm pointing to glstatic.net.  Works with 3.8.0 but not with 5.
It's obviously something I've done wrong my end, so I've editted and attached my file.
glossary2.zip

Thanks for reporting this and helping me reproduce this. You weren't doing anything wrong -- I had changed the behaviour without documenting this properly :grimacing:.
From version 4.0.0 onwards, opening the glossary.html file directly in a browser (as a file:// URL) only shows the help message, not the actual glossary. So opening it as a file in the browser now just meant as a starting point. To see the glossary contents, you will need to either use the node command in the help message that runs the built-in editor, or "host" the file using e.g.
python3 -m http.server 8000

For what it's worth, I was forced to make this change so that I could start using query parameters (to keep track of the tag currently being filtered by, and the current sort order), and I couldn't see any good alternatives. It's unfortunate that this adds more friction.
(I've belatedly documented this change in the CHANGELOG and the release notes for version 4.0.0.)

Thanks for the reply. So, am I stuck with using 3.8.0 for my glossary? It's no big deal, it's still works perfectly for my needs. On another note, is there a way I can use the dark theme by default? At the moment it defaults to the light theme. Thanks again for creating this, it's great. Graeme Sent from my Galaxy
-------- Original message --------From: Hilverd Reker @.> Date: 15/09/2024  6:27 pm  (GMT+00:00) To: hilverd/glossary-page-template @.> Cc: the-real-graybags @.>, Author @.> Subject: Re: [hilverd/glossary-page-template] If I upgrade from 3.8.0 to anything else, the page breaks. (Issue #11)
Thanks for reporting this and helping me reproduce this. You weren't doing anything wrong -- I had changed the behaviour without documenting this properly 😬.
From version 4.0.0 onwards, opening the glossary.html file directly in a browser (as a "notranslate">node command in the help message that runs the built-in editor, or "host" the file using e.g.
python3 -m http.server 8000
For what it's worth, I was forced to make this change so that I could start using query parameters (to keep track of the tag currently being filtered by, and the current sort order), and I couldn't see any good alternatives. It's unfortunate that this adds more friction.
(I've belatedly documented this change in the CHANGELOG and the release notes for version 4.0.0.)
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

Sorry for the delay -- yes opening a glossary file via a file:// URL no longer works properly after 3.8.0. But I think I have found a way to fix that. I will also add an option under "Settings" to allow changing the default theme.
I will post an update here once I have managed to release those changes.

This should now be fixed in v5.1.0 which also adds the ability to change the default theme.
If you want to try it then hopefully upgrading shouldn't be too painful, although there were breaking changes in v4.0.0 and v5.0.1.
I'll close this issue now but can reopen it if something isn't OK.


IncorrectJaxRsPluginsException: ERROR!  No jax-rs application plugins found

I am using Microboot- hoping to leverage SpringBoot and use the Grizzly server too. I am getting the following error:
Exception in thread "My-Web-Service" com.aol.micro.server.module.IncorrectJaxRsPluginsException: ERROR!  No jax-rs application plugins found
at com.aol.micro.server.servers.JaxRsServletConfigurer.addServlet(JaxRsServletConfigurer.java:25)
at com.aol.micro.server.servers.grizzly.GrizzlyApplication.run(GrizzlyApplication.java:69)
at com.aol.micro.server.servers.ServerRunner.lambda$start$54(ServerRunner.java:69)
at com.aol.micro.server.servers.ServerRunner$$Lambda$85/1192603187.run(Unknown Source)
I have this application class sitting in the base package:
@Microboot
public class App {
public static void main(String[] args) {

    new MicroserverApp(() -> "My-Web-Service").start();
}

}
I have my web service define like this in a sub package:
@Rest
@Path("/my-web-service")
public class MyWebService {
...
}
When I run the App I can see promising logs like these:
2016-03-02 18:55:04,276 INFO [main] c.g.o.r.e.t.a.App [StartupInfoLogger.java:57] Started App in 11.605 seconds (JVM running for 13.857)
2016-03-02 18:55:04,298 DEBUG [main] o.s.b.f.s.DefaultListableBeanFactory [AbstractBeanFactory.java:251] Returning cached instance of singleton bean 'myWebService'
However, I also get the above error and my web service does not respond http requests.
Any ideas how to solve this problem?
Thanks

Hi Mario,
Add micro-jersey to the classpath to add a jax-rs plugin to your app.
https://github.com/aol/micro-server/tree/master/micro-jersey

Further to that if you have micro-jersey on the classpath but are still seeing this error, the most likely cause is that the plugin files in micro-jersey are being overwriten during the generation of a 'fat' jar. With gradle shadow jar you can write
    shadowJar {
      mergeServiceFiles()
    }

Brilliant! Adding micro-jersey to the classpath solved it.
Thanks very much for such a quick response :)

Is there a way to configure the http port on which Grizzly listens to in the above setup?

You can set My-Web-Service.port property to port value

@mario786  as @earlzero  says you can use a property (either in a properties file, or via Microserver annotation or as a system property). E.g. your application will look for a file application.properties on the classpath or in the user directory and if that has a property
My-Web-Service.port=8090
Then the port will be set to 8090.
https://github.com/aol/micro-server/wiki/Defining-Properties
https://github.com/aol/micro-server/wiki/Configuring-the-port-or-hostname

That's lovely! Thanks very much for your help guys :)
Note to self: Put some effort in reading the Wiki before asking :P


Encountered problems while using pymoo parallelization, hoping to seek help

class MyProblem(Problem):

    def __init__(self):
        super().__init__(n_var=13,  # x
                         n_obj=2,   #
                         n_ieq_constr=4,  #
                         n_eq_constr=1,  #

                         xl=np.array([0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]),  #
                         xu=np.array([6.63, 3.18, 2.09, 1.8, 2.4, 1.3, 2.7, 2.7, 1.8, 1.8, 1.1, 2.2, 2.2]))    #

    def _evaluate(self, X, out, *args, **kwargs):

        def my_eval1(x):
            return ((x[0] * ρ_coal + x[1] * ρ_pv + x[2] * ρ_wt + x[3] * ρ_coal + x[4] * ρ_pv + x[5] * ρ_wt + x[6] * ρ_coal + x[7] * ρ_gas + x[8] * ρ_pv + x[9] * ρ_wt + x[10] * ρ_gas + x[11] * ρ_pv + x[12] * ρ_wt)  # total

            )  #  obj ：f1

        def my_eval2(x):
            return ((((1-eff1_a) + (1-eff1_b)) * (x[0] + x[1] + x[2]) )
                     + (((1 - eff5_a) + (1 - eff5_b)) * (x[3] + x[4] + x[5]))
                     + 1000 * ((res_line5_6 / 160000 * (((x[3] + x[4] + x[5] + P_line5_6) ** 2) - (P_line5_6 ** 2))))
                     + (((1 - eff6_a) + (1 - eff6_b)) * (x[3] + x[4] + x[5]))  # MG
                     + 1000 * ((res_line3_6 / 160000 * (((x[3] + x[4] + x[5] + P_line3_6) ** 2) - (P_line3_6 ** 2))) )
                     + ((1 - eff3_b) + (1 - eff3_c)) * (x[3] + x[4] + x[5])
                       + (((1 - eff8_a) + (1 - eff8_c)) * (x[6] + x[7] + x[8] + x[9]) )
                         + (((1 - eff9_a) + (1 - eff9_c)) * (x[10] + x[11] + x[12]) )
                         + 1000 * ((res_line7_9 / 160000 * (((x[10] + x[11] + x[12] + P_line7_9) ** 2) - (P_line7_9 ** 2))) )
                         + (((1 - eff7_a) + (1 - eff7_b)) * (x[10] + x[11] + x[12]) )
                )   #  obj ：f2
        def my_ueq1(x):
            return x[0] + x[1] + x[2] - 10.9

        def my_ueq2(x):
            return x[3] + x[4] + x[5] - 4.0

        def my_ueq3(x):
            return x[6] + x[7] + x[8] + x[9] - 9.2

        def my_ueq4(x):
            return x[10] + x[11] + x[12] - 5.5  #  <=

        def my_eq(x):
            return x[0] + x[1] + x[2] + x[3] + x[4] + x[5] + x[6] + x[7] + x[8] + x[9] + x[10] + x[11] + x[12] - 22

        params = [[X[k]] for k in range(len(X))]
        F1 = pool.starmap(my_eval1, params)
        F2 = pool.starmap(my_eval2, params)
        G1 = pool.starmap(my_ueq1, params)
        G2 = pool.starmap(my_ueq2, params)
        G3 = pool.starmap(my_ueq3, params)
        G4 = pool.starmap(my_ueq4, params)
        H = pool.starmap(my_eq, params)

        out["F"] = np.array([F1,F2])
        out["G"] = np.array([G1,G2,G3,G4])  # <=
        out["H"] = np.array([H])  #

I suspect that there is an issue with my code in these few lines, which resulted in the solved ‘x’ not being able to correspond to ‘f1’ and ’f2‘
       out["F"] = np.array([F1,F2])
        out["G"] = np.array([G1,G2,G3,G4])  # <=
        out["H"] = np.array([H])

I want to know how to write parallelized code when there are multiple objective functions or constraints.

Please look at the parallelization tutorial: https://pymoo.org/problems/parallelization.html
I recommend either parallelization directly with NumPy or over the entire _evaluation function call (instead over Fs and Gs indepdently)

Even though H is supported, please note that evolutionary algorithms are not designed to easiliy satisfy them.


remove redundant type parameters

Follow up on PR #1720 - remove unnecessary type parameters

Current coverage is 96.86% (diff: 100%)

Merging #1734 into master will not change coverage

@@             master      #1734   diff @@
==========================================
  Files            87         87
  Lines         11215      11215
  Methods           0          0
  Messages          0          0
  Branches       1882       1882
==========================================
  Hits          10863      10863
  Misses          210        210
  Partials        142        142

Powered by Codecov. Last update 177a393...4ad1c38

Thank you!


Feature/kan experiment

Add KAN model
Benchmark of KAN on M3 and M4 dataset against MLP and NBEATS

@marcopeix we also need to add KAN to the evaluation pipeline in https://github.com/Nixtla/neuralforecast/tree/main/action_files. You can check with Olivier how to add it,

@cchallu I already added KAN to the evaluation pipeline in action_files. Olivier checked it and says it's good! Let me know if I am missing something!

This PR is getting pretty big. Is it possible to review it and merge it soon? @cchallu @AzulGarza. Thanks! 😄

@marcopeix Convolutional KAN could also be considered, see: https://github.com/IvanDrokin/torch-conv-kan


SwiftLint + HoundCI

Added config files for both.  @tannernelson you’ll need to sign up and enable on houndci.com

Okay I enabled Vapor on houndci. Can you do another commit to trigger it?

Looks like it ran, but I'm skeptical it was that fast...


Add headers to HTTP responses

The API should return a Content-Type: application/json header.
Also, a Last-Modified: header would be nice to allow the creation of a local cache.

Content type header is now set correctly.

Looking at solutions for the last modified problem

For the time being I added a Last-Modified header that I can update each time I add to the database, as a temporary solution. Looking at a better way to dynamically generate the date based on real-time updates to the database instead of updating the repo with the newest date for each change.


failed to write request: Broken pipe (os error 32)rust-analyzermacro-error

/// Instructions supported by the generic Name Registry program
#[derive(Clone, BorshSerialize, BorshDeserialize, PartialEq)]
pub enum AggregatorInstruction {
    /// Accounts:
    ///   0. [writable] The aggregator to initialize
    ///   1. [sign] Owner
    ///   2. [] Rent sysvar
    ///   3. [] Clock sysvar
    Initialize(Config),
    /// Accounts:
    ///   0. [writable] The aggregator
    ///   1. [sign] Oracle
    ///   2. [] Clock sysvar
    Submit { timestamp: Timestamp, value: Value },
}

it show some error
failed to write request: Broken pipe (os error 32)rust-analyzermacro-error
failed to write request: Broken pipe (os error 32)rust-analyzermacro-error

Just to confirm. Are those proc macros from the borsh crate?

yep, it used borsh

This is breakage probably caused by the merging of this PR: https://github.com/rust-lang/rust/pull/87264
I'm guessing it has to do with being on the latest rustc nightly rather than a specific crate's proc macros :)

TvT

https://github.com/rust-lang/rust/pull/87264/files#diff-b42e9adad2cfc0be65632a15d616c95b812effe27357d9f5aee13cd949d68190R65
the proc macro bridge will need to be updated. https://github.com/rust-analyzer/rust-analyzer/tree/master/crates/proc_macro_srv/src/abis needs to get a new directory for the 1.58 abi. @alexjg would you mind doing this?

I'll sort it out tomorrow!

idk if tomorrow means fix will ship this Monday or next, but to whomst'd've it may've concerned, the temporary fix is:
rustup default nightly-2021-11-12

to undo:
rustup default nightly
rustup uninstall nightly-2021-11-12

great!!!

I'm using nightly-2021-11-12-x86_64-unknown-linux-gnu unchanged - rustc 1.58.0-nightly (936238a92 2021-11-11) and rust-analyzer extension v0.2.817 from VSCode and still getting this error.
Do either of these version seem wrong? Thanks!

Having the same problem in VS Code with rust-analyzer. Will prefer to stay on stable and not upgrade to nightly, so there is no fix for me yet.

@Sword-Smith we were downgrading the nightly, and that has since been resolved in #10769 and released yesterday.
We can all return to the current nightly now.
If you are currently having a problem with stable rustc, which is 1.56.1, it's either a regression for the old ABI or an unrelated problem altogether.
Please make sure:

you rustup update your stable
Ctrl-Shift-P > Rust Analyzer: Show RA Version shows rust-analyzer version: 183ef048f 2021-11-22 stable (that's the actual rust-analyzer binary that the matklad.rust-analyzer VS Code extension downloads separately). If not, close all your VS Code windows, it will try to update on next open.
cargo clean your project

and then post the particular error you are getting.

@Sword-Smith we were downgrading the nightly, and that has since been resolved in #10769 and released yesterday. We can all return to the current nightly now. If you are currently having a problem with stable rustc, which is 1.56.1, it's either a regression for the old ABI or an unrelated problem altogether.
Please make sure:
1. you `rustup update` your stable

2. Ctrl-Shift-P > Rust Analyzer: Show RA Version shows `rust-analyzer version: 183ef048f 2021-11-22 stable` (that's the actual rust-analyzer binary that the `matklad.rust-analyzer` VS Code extension downloads separately). If not, close **all** your VS Code windows, it will try to update on next open.

3. `cargo clean` your project

and then post the particular error you are getting.

I went through all your steps but had to add another one, even though VS Code showed the version you described in step 2:

Close all VS Code windows and open them again.

Just encountered the same problem as @Sword-Smith, I believed it happened just after I updated to the latest version of VSCode. I ran rustup update and then quit VSCode and restarted it and the error messages went way (not sure if the rustup update was necessary or if fully restarting VSCode would have sufficed).

Unfortunately this error message is fairly general and will be caused by many different scenarios. I'm fairly sure the code posted in this issue no longer causes the problem. If you're experiencing a problem I think the best way to proceed would be to open a new issue with your rust-analyzer and rustc versions and a sample of code which causes the problem, it's much easier to diagnose the problem that way.

Same issue with rust-analyzer v0.2.826.
rustup 1.24.3 (ce5817a94 2021-05-31)
info: The currently active `rustc` version is `rustc 1.54.0 (a178d0322 2021-07-26)`

I also encountered  [rust-analyzer macro-error] [E] failed to write request: Broken pipe (os error 32) when using rust-analyzer d9b2291f5 2021-11-29 stable via coc-rust-analyzer  v0.56.0, but only on codeblocks using derive(StructOpt) https://docs.rs/structopt/0.3.25/structopt/index.html#how-to-derivestructopt on a project that had pinned the rust-toolchain to 1.54.0. Upgrading the toolchain to 1.56.1 fixed the issue for me.

I also encountered this error. My system was VSCode + WSL. I made a mistake of using WSL on Windows FileSystem, but then I came to know about the Remote-WSL extension. I switched VSCode to Ubuntu 20.04 filesystem(WSL) and then error was no more. Weird things happen if VSCode is used on Windows Filesystem.
I referred this link for getting the Extension idea. Follow this if you are using WSL + VSCode: https://harsimranmaan.medium.com/install-and-setup-rust-development-environment-on-wsl2-dccb4bf63700

1. you `rustup update` your stable

2. Ctrl-Shift-P > Rust Analyzer: Show RA Version shows `rust-analyzer version: 183ef048f 2021-11-22 stable` (that's the actual rust-analyzer binary that the `matklad.rust-analyzer` VS Code extension downloads separately). If not, close **all** your VS Code windows, it will try to update on next open.

3. `cargo clean` your project

I went through all your steps but had to add another one, even though VS Code showed the version you described in step 2:

Close all VS Code windows and open them again.

Edit: I took the liberty to post this on Stack Exchange as there is there are too few Rust questions on Stack Exchange: stackoverflow.com/questions/70079983/rust-analyzer-failed-to-write-request-broken-pipe-os-error-32/70079984

For me another key step was to ensure the rustc version you are using is actually the one that is provided by rustup. I ended up using a Homebrew installation of my rust toolchain and it has a higher precedence in my PATH and in result I'm using a more older rust toolchain, specifically rustc 1.54.0.
Check using which rustc gives me /usr/local/bin/rustc, which clearly isn't where rustup is installing the toolchain to. By using brew uninstall rust and cargo clean then cargo run everything now works like a charm! :heart:

Installed RA Version 0.2.817 (2 versions prior)
Restarted VSCode, everything worked.

I tried all the other steps and reverting to an older version of the plugin was the only thing that worked for me. I don't want to stop using RA, so I'll stay on this version until this issue gets resolved.

Hi. I'm still seeing this error in v0.2.853 when using the crate https://crates.io/crates/builder-pattern with just the example code.


Numeric font-weight values

According to font-weight values in dictionary it’s should be possible to expand following abbreviations:
fw100 — font-weight:100;
fw10 — font-weight:100;
fw1 — font-weight:100;

But it’s not :(

:+1:


ImportError: cannot import name _thread , Need  help

Need help with this problem , thanks.
Traceback (most recent call last):   File "run.py", line 4, in <module>     from slackbot.bot import Bot   File "/usr/local/lib/python2.7/site-packages/slackbot/bot.py", line 9, in <module>     from six.moves import _thread ImportError: cannot import name _thread

I find the solution by add
import sys sys.path.insert(1,'/Library/Python/2.7/site-packages')
http://stackoverflow.com/questions/27630114/matplotlib-issue-on-os-x-importerror-cannot-import-name-thread


[iOS][Desktop][Tablet][Safari] Modal window does not scroll

Modal window does not scroll and show odd behavior on Desktop Tablet running iOS and Safari.
*google corporate account required to access video link
https://drive.google.com/a/google.com/file/d/0B5iXI7eBqeIOdkZZajF1UEpINDQ/view?usp=sharing

Same issue experienced on iPad 10 inch running iOS 10.1.1