Add multiple methods to Array

Bump version to 0.9.0
Add unshift, shift, dup, to_s and reverse to Array
Update ruby-sys required version to 0.3.0

I would like to add some tests. I was thinking of creating a ruby project and add rspec tests. What do you think @d-unseductable ?

As a note for anyone looking at this, it requires https://github.com/steveklabnik/ruby-sys/pull/10 to be released.

Regarding tests, Travis does not support multi language stuff, so if you wanted it done through CI you'd either need a script to install either rust or ruby (I'd go with rust tbh, much simpler) or to use multiple CI services.

It's not too difficult to run both Rust and Ruby tests with Travis CI, I do so in rusty_blank (powered by Ruru).
My personal preference is to have Ruby tests written with minitest because that's what's already bundled with Ruby and it's similar to how Rust tests are written. But it's not my project, so I'll leave it up to @d-unseductable.

@elifoster, do you mean the ```ruby sections in documentation?
Those are just examples and they are not executed with CI. Every rust example (doctest) has its corresponding ruby example which is basically the same code written in ruby. IMO it's sometimes easier for users to understand an example reading both rust code and its ruby analog.
@malept, it's a good idea to have rspec/minitest test suite.
Since most of the ruru methods are just simple bindings (receive and process arguments and call the corresponding ruby-sys function, like Array.push() or RString::new()), IMO one test (doctest) per method is enough to be sure that those bindings work correctly.
For more complicated cases I wanted to have integration tests using ruby test frameworks, but at that time it was problematic to set the things up. It was quite a long time ago, before thermite was created. So maybe it's good time to try it once again :)

👌 Working on:
[ ] Format code
[ ] Remove version
[ ] Adjust NEWS
[ ] Adjust Cargo.toml
[ ] Rebase

Great job, @simon0191! Thank you!

FYI @simon0191 969ef55f8a926536154faa10071c4679c7ca51b7...8b92dc46c24ce9bad2a4224a3806abd46b340c36


Fail fast when env DATASET_API_KEY is missing

When I check the current output of the failed job - https://github.com/scalyr/opentelemetry-exporter-dataset/actions/runs/6608806398/job/18843984634?pr=31#step:9:19
18 2023-11-20T09:57:05+00:00 DATASET_URL: https://app.scalyr.com/
19 2023-11-20T09:57:05+00:00 DATASET_API_KEY: XXXXX
...
50 Error: invalid configuration: exporters::dataset/logs: api_key is required
51 2023/11/20 09:57:08 collector server run finished with error: invalid configuration: exporters::dataset/logs: api_key is required

It's little bit confusing, since the real error is hidden in the middle. So lets fail fast when the environmental variable is not set.

Codecov Report

Merging #41 (fa4d27f) into main (c5c9e66) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #41   +/-   ##
=======================================
  Coverage   97.01%   97.01%
=======================================
  Files           5        5
  Lines         469      469
=======================================
  Hits          455      455
  Misses         11       11
  Partials        3        3

I am confused, pipeline that is part of this PR - https://github.com/scalyr/opentelemetry-exporter-dataset/actions/runs/6939949355/job/18878098524?pr=41 - succeeds, because env. variable is indeed set:
2023-11-21T06:09:07+00:00 DATASET_URL: 'https://app.scalyr.com/'
2023-11-21T06:09:07+00:00 DATASET_API_KEY: 'G4A-' (last 4 characters)

All the actions triggered by dependabot do have variables but do not have secret:

Missing secrets for PRs created by Dependabot are feature not a bug - https://github.blog/changelog/2021-02-19-github-actions-workflows-triggered-by-dependabot-prs-will-run-with-read-only-permissions/


Safer regex and readability in build_java_x files

Signed-off-by: Ashish Kumar Mishra<EMAIL_ADDRESS>

Part of the commit message should include the justification for the change.

Done, added commit description


71 Terminal Abstract Class

Added the Terminal abstract class which represents values that will not change after evaluation.
Closes #71

@coderabbitai review


update to 0.1.5 leads to invalid option in system.conf

Hello.
Performing the update from 0.1.4 to 0.1.5 via the web interface left behind the line
DISABLE_CLOUD=&PASSWORD
in system.conf for me. I can't tell what it was before while on 0.1.4., but probably it was =no.
Somehow this prevented changes made on the configuration page to be saved.
Manually changing the setting system.conf via ssh fixed this for me.

Other users reported the same problem.

Closing as duplicate of #24


New logo wanted for Ruia

Need a logo meaning "Light and Fast crawler", I think the logo looks like a running girl.

Thanks for your response @howie6879 , I make it like a crawler. If you need something else I will make it.

Hi, are you doing this?

Thanks for your response @howie6879 , I make it like a crawler. If you need something else I will make it.

Hi, is this thing still going on?

Why you named it ruia?

Why you named it ruia?

To my love ~ a lovely girl

Some ideas about the logo：

Left: parallel lines can evoke async streams
Right: Like a girl on the run

Hi @howie6879 Sorry, did not see the notification. How about this? If you need anything change i'll fix it.

@mirzazulfan
So beautiful, i think this is a good one, btw, can there be more changes in color?
What do you think? have any ideas for improvement?

Hi @howie6879 Sorry, did not see the notification. How about this? If you need anything change i'll fix it.

I have already invited you. can you submit the logo to this project? ruia-assets

Im glad you liked it. Sure, what color and size do you prefer? :)

Im glad you liked it. Sure, what color and size do you prefer? :)

What about red？

I'll send all files tomorrow. :)

I'll send all files tomorrow. :)

Thank you very much, so beautiful.

It seems that there is no circular logo in the project.

I've uploaded all of them. also you can download all files here. If you need anything change in the future, please let me know. :). Thanks @howie6879 im glad to help your project.

@mirzazulfan
Great job,  thank you so much


Train griefing in to the other when spawning

When the train is spawning on the platform rail, the spacing train can over lay the exiting train.

This is an issue with the train timing, you'll either need to change your timing so that the trains don't overlap (use the same track/platform at the same time), add collision detection to the mod, or make one platform per line per direction.


sphinx docs

I am aware there is a module for obtaining CLI documentation.
However I would ALSO prefer if the code behind the CLI were to be properly documentable by autodoc in the normal way. (treating it as a method/function, etc.)
This way I could put my CLI documentation alongside the code docs and have the correct formatting when looking at the module in terms of code rather than user interface behavior.
Currently, unless i'm doing something wrong, it appears the decorators from click are hiding the methods, signatures, and docstrings from autodoc, so I end up with an empty module documentation page.
If indeed this is my fault, would you have any guidance for what I ought to do? (I am getting successful output from the click parser ".. click:: module" etc. Its pretty nifty: https://github.com/click-contrib/sphinx-click )

If you have a command example, then example.callback is the original function, which you can point autodoc at. However, note that commands are not intended to be called as standard Python functions after being decorated, so thismay be more confusing than helpful, but that's up to you.

I'm not completely familiar with Sphinx-Click, but it sounds like you may be interested in requesting or contributing functionality similar to sphinxcontrib.autohttp.flask and autohttp.flaskqref.


Hard-delete objects that were never committed

User story
In general, objects should be removed from the storage when there are no valid pointers from lakeFS to them.
In particular, objects that were removed from the staging area without ever being committed should be hard-deleted from the underlying storage.
Requirements
In case an object exists only in the staging area of a branch (does not belong to any commit) - hard-delete it immediately when it has no lakeFS entries that use it as a physical address. This may happen when:

The object is deleted in lakeFS.
The object is overwritten in lakeFS.
All uncommitted changes on the branch are reverted.
The branch is deleted.
The repository is deleted.

Important: the implementation should take into account that lakeFS sometimes uses the same object for multiple entries (AKA deduplication).
Proposal
The requirements can be kept by the following:

When removing staged data (by delete or by revert) delete the data from underlying storage as well (*this could be done only if deduplication works only on committed data)
When removing a branch delete all staged data from underlying storage.
TBD - handle Objects that where overwritten within staging

Summary of meeting (@nopcoder & @arielshaqed):
Collect in...

Online: (enhanced) lakeFS+
Batch: (enhanced) GC

Delete everything **lakeFS knows about**.
Delete everything under a storage namespace that is not referenced

Pros

Works for all users.

Cons

Requires one-time upgrade (which will be a simple GC-like process!)
    Not fsck: cannot delete a file that lakeFS does not know about (for whatever reason).
    Slower (online!) put.

Pros

Trivial upgrade
    Simpler to code

Cons

Needs to understand special "directories" used by lakeFS _not_ for staging
    Must `ls -R` (or inventory).  In future might have a smaller listing if we scan by all staging tokens, e.g. track "live" staging tokens (everything uncommitted + committed in past week).
    Requires Spark (or a separate non-Spark implementation)
    Slower.  But note that if GC is enabled (and it will be whenever people care about forgetting the past and/or total space!), then uncollected lost files are a fixed proportion of all stored files!
    Still hits staging (requires new lakeFS API to find or work by staging tokens and also to do this efficiently)

Decision
Overwritten and deleted objects on staging areas are a lakeFS (versioning) issue, that is probably easiest to handle on the GC process.  We assume that it is OK to handle object removal in GC only: users who care about compliance anyway need to have GC as well; users who care about storage will not have that many files overwritten on staging (and if they do, we can add a "best-effort" patch to lakeFS to try to delete the old file if it is in the current staging area of the storage namespace on overwrite or delete).
So this is a joint @treeverse/versioning  + @treeverse/ecosystem effort.  Versioning should lead (and design): most unknowns are on the versioning side, and it probably needs to be designed for the KV world.  Eco can supply knowledge of how to parallelize lakeFS access without overloading it and how to use Spark to compute huge diffs in the physical address world, as well as parallel bulk delete codes.  The implementation itself might be in the same GC job or in a different jobs.
Why S3 Lifecycle policies won't work

Non-AWS S3 backends might not even have lifecycle (although Minio has lifecycle management)
Separate implementation on S3, Azure (which might split into blobstore and datalake!), GCS
Tags and deletes are not transactional, making it very hard for code guarantee any dropped file will be deleted.

Adding my 2 cents. lakeFS gets criticized for not collecting uncommitted objects from users throughout the funnel, even if they are just evaluating it.  We know that most users don't bother to configure their lakeFS GC since it's not that trivial for everyone. Given the way that Spark works, I understand users frustration with 3x data being stored for Spark jobs. While I understand the limitations of an online-only solution, I do think that we need to think of an online way to prevent uncommitted garbage, even if it's not hermetic and requires the users to run GC for 100% cleanups.

Any news about when this issue will be fixed? I am very interested in this one

Hey @isabela-angelo, we started the design for this one. It's not that trivial as a proper cleanup will require the user to run some offline Spark GC job with information on the storage from the lakeFS server. We try to reduce the friction of running an external job as much as possible. I estimate it will be ready by Q4.

Nice! Thanks for the reply

@johnnyaug a requirements question:
Do we want to clear uncommitted garbage on every GC job run? I mean, should this happen by default or by a user configuration? The latter makes more sense to me, but I will be happy to get your input.


Merging with foldamers

Description
The big merge of CG_openmm/foldamers.
Structural analysis code (such as clustering, angle distributions) went to a new repo called analyze_foldamers, while everything else from foldamers went here. (See https://github.com/shirtsgroup/foldamers/issues/44) From now on, the foldamers repo will act as an archive, though it seems that the commit history of everything transferred is preserved. This was all done using git filter-branch --subdirectory-filter commands.
I deleted a lot of the structure files in examples - in particular, varying_model_parameters/scan_torsions had ~3700 files.
We will also need to remake the structure library so it is empty for now. All of the original structures are preserved in foldamers.
Todos

[ ] Check if the updated imports are right
[x] Clean up the rest of the structure files (these are all saved in foldamers)
[ ] Sort out which functions of parameters.secondary_structure should stay here

Status

[ ] Ready to go

Codecov Report

Merging #50 into master will decrease coverage by 4.57%.
The diff coverage is 1.56%.

Also, can probably not move over a lot of the ensembles of pdbs - those will be stored for now in the old foldamers repository, we don't need to move them over.

Hmm yes it seems like there was some issue pulling from the most recent version of cg_openmm. I will try that again.

The files in question are reverted to the general_heteropolymer commit - should be fixed now. It seems to have been only 4 files affected: examples/simulation.py, examples/run_replica_exchange.py, build/cg_build.py, and utilities/iotools.py.

I got rid of a bunch more pdb files as well.


Update cloud.google dependencies

The cloud.google dependencies are very old and some features are not enabled (namely cloud kms for bring-your-own-key buckets).
I tried to update, but there were loads of transitive dependency changes, so I'm not very sure about it. Would be great if someone who knew the codebase could take a look.
Thanks.

Did you try using govendor (https://github.com/kardianos/govendor)? That's the tool we are using for dependency management. We are in the process of moving to Go modules (see #212) but that is likely going to take some more time.

Sorry for the late reply. Wow that's a big list of TODOs!
I've got a fairly restricted environment and govendor wouldn't work for me.
I switched to go mod and set the GOPROXY and it's working fine (for my very simple use-case). All existing tests pass as well.
Also updated the google libs only to find out that it's still an unimplemented feature.
For anyone on GCS, Buckets using CMEK (custom managed encryption keys) is (1) slow (2) ComposeFrom doesn't work. They may never fix (but no earlier than 2020 Q1 if ever).
For my use-case I patched tusd to use Copier instead of Composer if there is only one chunk. Would anyone be interested in a PR for that? It's a minor change.

Also updated the google libs only to find out that it's still an unimplemented feature.
For anyone on GCS, Buckets using CMEK (custom managed encryption keys) is (1) slow (2) ComposeFrom doesn't work. They may never fix (but no earlier than 2020 Q1 if ever).

That's good to know. So is upgrading the Google Cloud SDK of no benefit right now?

For my use-case I patched tusd to use Copier instead of Composer if there is only one chunk. Would anyone be interested in a PR for that? It's a minor change.

If there is a benefit, we would be very interested in a PR! Does it improve performance or what is the reason for this change? Sorry for the question but I am not too experienced with GCS.

Correct. No real benefit for my particular scenario - CMEK.
In fact, the PR is not required, as the Copier takes just as long to upload and causes performance to drop by half. For the time being, we decided to just wrap gsutil as it works well enough for us. Thank you for the feedback and such.

 Thank you for your efforts!


repeating dates when scrolling to previous/next week using week mode (1 row)

Hi, thanks for creating this awesome library. It is really simple to setup, high performance, and really customizable.
I am trying to set calendar to display weekly view by creating configuration parameter like this.
let parameters = ConfigurationParameters(
    startDate: startDate,
    endDate: endDate,
    numberOfRows: 1,
    calendar: Calendar.current,
    generateInDates: .forAllMonths,
    generateOutDates: .tillEndOfRow,
    firstDayOfWeek: .sunday)

The issue occurs when i try to scroll to previous week to the end of the month or scroll to next week to the beginning of the month. The date of the week is being repeated so i have to scroll 2 times to advance or go back to the week i want to scroll to.
Do you have any suggestion on how to fix this behavior
Thanks

Yes, this behavior is expected.
The repeating dates you are seeing are inDates and outDates.
You are used to seeing them on a 6-row calendar here:

When you have single row set to on, then you will see these inDates and outDates.
I see that you have your inDates set to show for all months, and your outDates is set to show till the end of grid for single row.
For single row, set your outDates to off and your problem should be resolved.
Spread the word about the calendar :)
Cheers man.

I will add a section to the tutorials so explain all these things to people

Thanks for the explanation. I hope you will continue to maintain this great library!

Thanks man. If you know anyone that can help translate the documentation into other languages, let me know. If not, its cool. I'll keep maintaining it. Have a good one. 🍺


The Great Courses Plus

Checklist

[x ] I'm reporting a new site support request
[ x] I've verified that I'm running youtube-dl version 2019.05.20
[ x] I've checked that all provided URLs are alive and playable in a browser
[ x] I've checked that none of provided URLs violate any copyrights
[ x] I've searched the bugtracker for similar site support requests including closed ones

Example URLs
https://www.thegreatcoursesplus.com/films/title/linear-algebra-powerful-transformations
I'll send account via PM

The other post is currently closed, how to re-open a request?

Where is the other thread? I can't find it.


fetch all rows is not working v6.0.0 in MAC

System information:

Operating system (distribution) and version -  MAC
DBeaver version - 6.0.0
Java version <IP_ADDRESS>
Additional extensions

Connection specification:

Database name and version - any database
Driver name - i use postgres, oracle , db2
Do you use tunnels or proxies (SSH, SOCKS, etc)? none

Describe the problem you're observing: I cant use fetch all rows, but i ca use only next rows . its giving trouble for me. I tried changing shortcut key as well but no use.
What can fix this issue
Steps to reproduce, if exist:
Include any warning/errors/backtraces from the logs

Check confirmations settings:

Hey thank u.. This might help
On Sun, 26 May, 2019, 22:48 Serge Rider<EMAIL_ADDRESS>wrote:

Check confirmations settings:
[image: image]
https://user-images.githubusercontent.com/6398845/58385074-5e74bc80-7ff3-11e9-9f7f-55e85e779c69.png
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dbeaver/dbeaver/issues/5974?email_source=notifications&email_token=AGAUGKFLWAOO7TGJW5ITA3LPXLA6JA5CNFSM4HOSV24KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWIJ25I#issuecomment-496016757,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGAUGKGU73QKHBUC36US3G3PXLA6JANCNFSM4HOSV24A
.


Importing zeep package panics with error: PyErr { type: 0x10f60b2c0 }

🐛 Bug Reports
🌍 Environment

Your operating system and version: macOS Catalina Version 10.15.7 (19H2)
Your python version: 3.8.0
How did you install python (e.g. apt or pyenv)? Did you use a virtualenv?: I installed it with asdf-python and tried both with and without Poetry venv
Your Rust version (rustc --version): rustc 1.49.0-nightly (ffa2e7ae8 2020-10-24)
Your PyO3 version: 0.12.3
Have you tried using latest PyO3 master (replace version = "0.x.y" with git = "https://github.com/PyO3/pyo3")?: yes and I got the same error

💥 Reproducing
A fresh Cargo binary project:
Cargo.toml
[package]
name = "dummy"
version = "0.1.0"
authors = ["fusillicode<EMAIL_ADDRESS>edition = "2018"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[dependencies]
pyo3 = "0.12.3"

src/main.rs
use pyo3::Python;
use pyo3::types::PyModule;

fn main() {
    let gil = Python::acquire_gil();
    let py = gil.python();

    let _mod = PyModule::import(py, "zeep").unwrap();
}

Output:
 cargo run -p dummy
    Blocking waiting for file lock on build directory
   Compiling pyo3 v0.12.3
   Compiling dummy v0.1.0 (/Users/me/code/example/dummy)
    Finished dev [unoptimized + debuginfo] target(s) in 2m 07s
     Running `target/debug/dummy`
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: PyErr { type: 0x10f60b2c0 }', dummy/src/main.rs:8:45
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

No specific flags were used.
No problem were encountered when importing another library, lxml, a dependency of zeep.
However the error under discussion arose also while importing other apparently unrelated libraries, e.g. docxtpl.
For anything I remain obviously at your total disposal.
Thanks for all your incredible work 🙇

@fusillicode thanks for the report. I couldn't reproduce this on my local machine (Ubuntu 20.04, Python 3.9, latest zeep). I suspect environment misconfiguration, but hard to be sure without more diagnostics.
We just merged some improvements to pyo3 which should output more helping information on a panic. Can you please retry with the latest pyo3 master, which should give a more helpful error message?
Also, you could try replacing
let _mod = PyModule::import(py, "zeep").unwrap();

with
pyo3::py_run!(py, "import zeep");

Which will also print the python traceback, if needed.

Thank you for the quick support and again for all your work 🙇
I've tried using pyo3::py_run!(py, "import zeep"); with the latest master version Compiling pyo3 v0.12.3 (https://github.com/PyO3/pyo3#aa30163e) but unfortunately I get this compilation error:
error: no rules expected the token `"import zeep"`
 --> negative_events/src/main.rs:8:23
  |
8 |     pyo3::py_run!(py, "import zeep");
  |                       ^^^^^^^^^^^^^ no rules expected this token in macro call

However with let _mod = PyModule::import(py, "zeep").unwrap(); I now get a more descriptive error:
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: PyErr { type: <class 'ImportError'>, value: ImportError('dlopen(/Users/me/.asdf/installs/python/3.8.0/lib/python3.8/lib-dynload/_posixsubprocess.cpython-38-darwin.so, 2): Symbol not found: _PyOS_AfterFork_Child\n  Referenced from: /Users/me/.asdf/installs/python/3.8.0/lib/python3.8/lib-dynload/_posixsubprocess.cpython-38-darwin.so\n  Expected in: flat namespace\n in /Users/me/.asdf/installs/python/3.8.0/lib/python3.8/lib-dynload/_posixsubprocess.cpython-38-darwin.so'), traceback: Some(<traceback object at 0x10d87e180>) }', dummy/src/main.rs:9:45
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

If there is anything I can do to simplify the troubleshooting I remain at your total disposal.
Thanks again.

error: no rules expected the token "import zeep"

🤦 I forgot that macro requires at least one other argument, nvm!

However with let _mod = PyModule::import(py, "zeep").unwrap(); I now get a more descriptive error:

Aha perfect! It looks like your python interpreter is probably a statically-linked one, like pyenv on Mac by default. This has known issues that we haven't worked out quite the best way to resolve yet e.g. see #762 #742.
The notes at #763 might be applicable.
Out of curiosity - are you trying to create a runnable executable which embeds Python? I've just started looking at PyOxidizer the other day, which might also help you get a working program.

🤦 I forgot that macro requires at least one other argument, nvm!

Don't worry I figured it out but I still wasn't able to make it work 😅

Aha perfect! It looks like your python interpreter is probably a statically-linked one, like pyenv on Mac by default. This has known issues that we haven't worked out quite the best way to resolve yet e.g. see #762 #742.
The notes at #763 might be applicable.

Awesome! I'll go check that issues ASAP! Thanks a lot!

Out of curiosity - are you trying to create a runnable executable which embeds Python? I've just started looking at PyOxidizer the other day, which might also help you get a working program.

Actually what I'm trying to do is to to create a single standalone Python module that exposes some functions to interact with a SOAP Web Service.
The module itself would be something like this:
from zeep import Client

CLIENT = Client('http://www.webservicex.net/ConvertSpeed.asmx?WSDL')

def convert_speed(speed):
    result = client.service.ConvertSpeed(speed, 'kilometersPerhour', 'milesPerhour')

From Rust I would then invoke the convert_speed function to get the Web Service response.
I don't think that PyOxidizer is really what I want 🤔

Hi @davidhewitt sorry for the bother, just an update about the issue: what suggested here and here worked like a charm! 👌
I just needed to reinstall the Python version I was using by prefixing the install command with env PYTHON_CONFIGURE_OPTS="--enable-shared".
In my case the install command was asdf install python 3.8.
I'm gonna mark the issue as resolved!
Thanks again for the quick support and for all your incredible work! 🙇

Thanks for following up - glad the other notes were able to help!


ppk-expressing mechanosensory neurons in the female reproductive tract

I'm at a loss as to what these ought be called. The description suggests they're not multidendritic neurons (as most ppk-expressing neurons are). They're described in three papers: PMID: 19249273, PMID: 19249272, and PMID: 25373900. Scer\GAL4[ppk.PG] is a marker. From expression curation of that driver:
'Scer\GAL4[ppk.PG] drives expression in the adult peripheral neurons, including 2 neurons on each lateral oviduct and 15 neurons on each side of the uterus, organised in 3 clusters.' (PMID: 19249273)
'In the reproductive tract it (Scer\GAL4[ppk.PG]) isexpressed in 2-3 fruitless expressing neurons on either side of the uterus as well as a small number of neurons surrounding the oviduct. The reproductive tract neurons project fine processes between the muscle and epithelial layers that enter and arborize within the lumen of the uterus while other processes bifurcate close to the soma and innervate the lower regions of the common oviduct, both these aborizations run along the inner surface of the epithelial cell layer. Infrequently, expression is also seen in 1-2 neurons near the base of the antennal nerve and the the lateral horn. Afferents from all of the above neurons contribute to the abdominal nerve trunk, most terminating in the thoracico-abdominal ganglion but some extend further in an anterior direction, and a pair of bilateral fibers emerge from the network in the abdominal ganglion, traverse the entire length of the ventral side of the nerve cord, extend through the cervical connective before terminating in the posterior region of the adult gnathal ganglion. (PMID: 19249272)

The neurons described in Yang et al. (2009) (PMID:19249273; FBrf0207501) and Hasemeyer et al. (2009) (PMID:19249272; FBrf0207523) are the sex peptide sensory neurons (FBbt:00111303 + subclasses) - I think 15 neurons is a mistake in the expression curation, perhaps because authors use n=15 samples?
The fru-negative neurons described by Gou et al. (2014) are FBbt:00049944, currently 'adult oviduct mechanosensory neuron', but Damien has broadened this to 'adult female reproductive tract mechanosensory neuron' (change will be in next FBbt release).
All these neurons fall under FBbt:00049943 'sensory neuron of female reproductive system'

Aha! I was struggling to find a term mapping onto what seemed to be described in the newest paper of the three I listed. I'll revisit the '15 neurons' curation and correct it if it's indeed misleading (backstory is that I'm plowing through binary drivers with no expression attached, and have hit the lexA version of the ppk construct).
I'll close this ticket.


[WIP] Max spaces, user prompt, excess string

Work in progress
This is pr when I am working on it, will let you know if I make progress.

Closes #40


example sayhi seems not work

By using sayhi in the example, tried function computing , but failed with ""errorMessage": "rpc error: code = Unknown desc = Exception calling application","
checked every step i have done, not find any clues, please help , thanks

@tongtongxiaopeng1979
Hi, according to sayhi log, the problem is "Exception calling application: 'USER_ID'". The right way about variable "USER_ID" should be that:

firstly it shouble be defined in conf.yml(openedge_hub module config)
then it can be used in index.py

But, as the conf.yml(openedge_hub module config) you provide, it cannot be found.
Two methods to solve this problem:

add "USER_ID" config info in conf.yml(openedge_hub module config), it can be found here
add judgment logic at index.py.

That's all, many thanks for your problem feedback.

thanks, it works according to your guide. :)


Creating a visualization from a data file doesn't get the bounds in the initial map

Fixes #2527

FYI: to get bounds of a recently created table a faster way to it would be:
# select _postgis_stats('sigpac_47_valladolid_parfe', 'the_geom')::json->'extent';
                      ?column?
-----------------------------------------------------
 {"min":[-5.52764,41.0878],"max":[-3.97387,42.3147]}

Frontend tests were OK :+1: (details)

From what I see in the code all scenarios fall into "bounds calc from recently created tables". Filling a ticket to generally improve that.


Set "is_published" to false for overshadowed segments in sys.segments table

Description
sys.segments table retrieves published segments from coordinator (segments which are in metadata store with used=1), and marks all those segments with is_published=true. The published segments can include overshadowed segments if compaction is underway. Currently, sys.segments table gets all the segments from coordinator where used=1, there might be some segments which are overshadowed and still have used=1 in coordinator as there can be a lag before used=0 is set for overshadowed segments, at which point they will not be returned from coordinator. But, if those overshadowed segments are not handled properly, the sys.segments table may show dangling segments for a while.
Motivation
sys.segments table contains overshadowed segments with their is_published column is set to true, which may not be the correct behavior because those overshadowed segments are going to be marked used=0 once compaction finishes. And sys.segments queries would be showing phantom segments for sometime. A better behavior for sys.segments is to mark the overshadowed segments with is_published=false in the query results, until they are removed completely from the table.

Hmm, maybe is_published is not the best name because overshadowed segments should have been published. How about adding a new column indicating this like is_queryable (for non-overshadowed segments)? or is_overshadowed?

It might be fine to call them "not published" especially if we define it right (like, "any segments that have used = true in the MD store and are not overshadowed"). I'm thinking that is the most useful definition for what this column is likely to be used for: finding all segments active in the metadata store. (Overshadowed ones aren't really active since they don't do anything)

Do you mean adding a definition to doc? I'm afraid if ppl would check it before using the system schema.
Also, I'm not sure it's most useful. I think most ppl wouldn't care what are in metadata store, but would care what segments are currently being queried. Finally, it's not intuitive and I think it would highly likely mislead users. Why not just calling it is_used if you want to match it to used in metadata store?

Well, it shouldn't be called just is_used because it's used segments - overshadowed segments.

is_published is meant to mean "has bee published to the metadata store" according to the docs. And to my heart, in that I do think that's a useful thing for there to be a field for. I guess the question is what does that really mean?

All segments with used = true in the metadata store (what it means today)
All segments with used = true in the metadata store, that are also not overshadowed by any other segments with used = true in the metadata store (what this proposal is suggesting changing it to)

I think (2) makes sense, since as this proposal points out, (1) is unintuitive when doing an overwrite of a set of segments. The old set and new set will both have used = true for a while, but for all practical purposes the old set is considered overshadowed at that point.

Also, I'm not sure it's most useful. I think most ppl wouldn't care what are in metadata store, but would care what segments are currently being queried.

This is sorta like is_available. Except I think that one also includes some overshadowed segments, so it's not really what's "currently being queried". (I'm not 100% sure about that but maybe 80% sure)
Maybe what is happening here is that we want versions of both is_published and is_available that take into account whether the segments have been overshadowed or not.

Hmm, ok. It looks that there are some misunderstandings and confusions. First of all, I think it makes sense to keep is_published column as it is. But, I also want to add to a new column for non-overshadowed segments in system schema (regardless of their used value), like is_queryable, is_available, or is_overshadowed (this is opposite to first 2 names). To keep both columns, I think users can avoid confusions and query more flexibly.
I also have some questions for the meaning of "published segments".

is_published is meant to mean "has bee published to the metadata store" according to the docs.

I think this means any segments in the segments table of the metadata store regardless of their used flag. This also matches to the meaning of "publishing segments" in indexing tasks. But, you said,

All segments with used = true in the metadata store (what it means today)

This isn't exactly same with the meaning of is_published since overshadowed segments can still be in the metadata store with used = false. I'm not sure what you mean by "what it means today". Is there any document about this? I feel is_active or is_enabled is more appropriate for these segments.
is_available (or is_queryable) is a bit different. These segments would have mix of used if some historicals haven't unannounced them yet. Also, some segments with used = true in metadata store can be missing in these segments.

This is sorta like is_available. Except I think that one also includes some overshadowed segments, so it's not really what's "currently being queried". (I'm not 100% sure about that but maybe 80% sure)

Yeah, if you're thinking the lag in brokers until they refresh their cache, it might not be "currently" being queried.

Below statement is correct :

All segments with used = true in the metadata store (what it means today)

the is_published col in segments table represents "all segments in MD store with used=1".

is_published is meant to mean "has bee published to the metadata store" according to the docs.

The doc here says above, but I think it's incomplete, as it omits the part about used=1.
@jihoonson Did you mean to suggest that the is_published should include all segments from MD store (irrespective of their used flag value) ? I think we should keep the existing behavior where it only shows segments in MD store with used=1 as I don't see any use of showing segments with used=0. In addition, if we enhance the behavior to also exclude overshadowed segments from this column, then I'd be okay renaming it to is_active, is_queryable or some other name we can agree on. Then the definition of this to_be_named col becomes "All non-overshadowed segments in MD store with used=1".

@surekhasaharan could you please clarify the motivation "Showing overshadowed segments as part of published segments with is_published=true may not be correct behavior" - showing where and by whom?
@jihoonson

But, I also want to add to a new column for non-overshadowed segments in system schema (regardless of their used value), like is_queryable, is_available, or is_overshadowed (this is opposite to first 2 names).

There is already an is_available column, isn't it?

@surekhasaharan could you please clarify the motivation "Showing overshadowed segments as part of published segments with is_published=true may not be correct behavior" - showing where and by whom?

Sorry that it's not clear, will edit the issue to clarify. What I meant to say is sys.segments table stores metadata about segments, one of the column it has is is_published,  which stores the information about whether a segment is published in metadata store with used=1 or not. And it contains overshadowed segments and their is_published column is set to true, which may not be the correct behavior because those overshadowed segments are going to be marked used=0 once compaction finishes.

@leventov oh, I missed it's already there. Thanks.
I talked with @gianm and @surekhasaharan offline and now it's more clear to me. Here is the current behavior.

is_available means that a segment is served by historicals or a realtime task. Overshadowing is not considered. Updated whenever a historical or realtime task announces a new segment or unannounces an existing one.
is_published means that used is set to true for a segment in metadata store. Overshadowing is not considered. Updated in background (metadata store is polled every 60s).

Unpublishing segments can mean setting used to false and it sounds good to me.

The issue here is that both columns are not considering overshadowing such that it makes debugging harder.
Probably, in many use cases, we want to know what segments are not loaded yet and why. To figure this out, we need to know what segment is published and is not fully overshadowed only by other segments in metadata store. This information is not being served yet, but it looks worth to add a new column. We came up with a name of is_active for this property. Does this make sense?

This suggested terminology sounds reasonable to me - in summary, not changing the meaning of is_available or is_published, but adding a new is_active property that basically means is_published && is_not_overshadowed_by_any_other_published_segment.

Is this right that sys.segments table is a virtual table that Druid processes queries against for the SQL interface to Druid? It doesn't exist in the metadata store (or any other real SQL database Druid depends on)?
Or not, since this message

What I meant to say is sys.segments table stores metadata about segments, one of the column it has is is_published, which stores the information about whether a segment is published in metadata store with used=1 or not. And it contains overshadowed segments and their is_published column is set to true, which may not be the correct behavior because those overshadowed segments are going to be marked used=0 once compaction finishes.

Contains the verb "stores"?

I don't like is_active. Active is a very overloaded term, and it's not obvious what's the difference between "active" and "published". I would suggest is_overshadowed, and if somebody wants "active", they need to write is_published = true AND is_overshadowed = false. is_overshadowed is defined as "overshadowed by other published segments that are loaded in the cluster". I suggest to add it only in sys.segments, but not in metadata store. In the codebase, all occurrences of "overshadowed" should be aligned with this definition. "Overshadowed by published but not yet loaded segments" should be called somehow else (if it is used in the codebase), like "preOvershadowed".

Is this right that sys.segments table is a virtual table that Druid processes queries against for the SQL interface to Druid? It doesn't exist in the metadata store (or any other real SQL database Druid depends on)?

Yes this seems right, I guess "contains" conveys the meaning better than "stores" ? Not sure on which verb to use.

I would suggest is_overshadowed, and if somebody wants "active", they need to write is_published = true AND is_overshadowed = false.

We were trying to make it easier for the user to get active segments just by writing is_active=true and documenting what is_published vs is_active implies. Do you have any other suggested name instead of is_active ? Yeah we can always create a is_overshadowed col, and let user query the way you suggest, but thought the other approach might be more convenient for users.

I suggest to add it only in sys.segments, but not in metadata store.

That's the plan.

@leventov I agree that is_active is not the best term. That actually represents that the segment is supposed to be loaded or not, so that users can understand why some segments are not loaded, or notice that some segments should be loaded but they are not. Do you have a better suggestion?
Regarding is_overshadowed, I don't think it's a good idea to restrict its definition to such a narrow scope because it's being used in various situations in our code base as well as documents. So, for example, the coordinator searches for segments which are loaded by historicals and overshadowed by published segments to tidy up old segments. Brokers searches for non-overshadowed segments among available segments in tasks or historicals for query execution. Even in historicals, they searches for non-overshadowed segments among the segments loaded in itself (note that two segments of different versions but for the same interval can exist in the same historical before the coordinator cleans up the old one). I don't think it's worth to define different terms for various cases. It would make things more complicated.

is_overshadowed is defined as "overshadowed by other published segments that are loaded in the cluster"

Any particular reason you’re thinking it makes sense to define is_overshadowed as “overshadowed by other published segments that are loaded”? (I assume this would mean: segments with used = true and that are available on some server)
I’m thinking “overshadowed by some published segments” would be more useful in a debugging scenario. It allows you to write is_published && !is_overshadowed to mean “should be available”. In turn, comparing that to is_available helps narrow down where the current cluster state (what’s available) is different from the desired cluster state (what should be available).

Perhaps is_actual is better than is_active.
Regarding the semantics of is_overshadowed, you all are right, confusing it with the temporal state of being loaded on some servers is probably a wrong idea.
Maybe we need both:

is_actual for published and not overshadowed by loaded segments, in other words, "segments that can and should be queried now".
is_overshadowed to provide ability to introspect into is_published && !is_overshadowed and is_published && !is_overshadowed && !is_available views.

"segments that can and should be queried now".

I think this statement is a bit incorrect because segments which are currently being generated by stream ingestion tasks should also be able to be queried but is_actual doesn't include them.

Yes. Also, the part "can" is wrong, because is_available is responsible for "can". A segment may be "actual" (as per the definition above) and not available at the same time.

Thanks everyone for the discussion and your inputs on this. I am thinking of adding a column is_overshadowed to sys.segments at this time. Not adding any is_active or is_actual col to keep things clear and easy to understand and since you can get the is_actual by doing is_published && !is_overshadowed.

I have updated the issue with proposal components which talks about the way I am thinking of implementing is_overshadowed column addition to sys.segments.

@surekhasaharan Can you please add the definition of is_overshadowed to the proposal? (To the "Proposed changes" section.) It sounds like we are settling on something like 'published segments that are overshadowed by some other published segment'. I would be fine with it being false for unpublished segments, if that makes it easier to implement. If that's what you do, then just make sure to include it in the docs, please. Maybe document it as something like:

is_overshadowed is true for segments that are published and that are overshadowed by other published segments. Currently, is_overshadowed is always false for unpublished segments, although this may change in the future. You can filter for segments that "should be published" by filtering for is_published = 1 AND is_overshadowed = 0. Segments can briefly be both published and overshadowed if they were recently replaced, but have not been unpublished yet.

I am ok with leaving is_published and is_available unchanged, and adding an is_overshadowed defined as above. I'm also fine with leaving out active/actual at this time and potentially adding them in a later change. If this is what you're proposing @surekhasaharan then I am 👍  on it.

thanks @gianm for articulating the definition of is_overshadowed . Added the definition of is_published in the proposal. Yeah, the impression I got from the discussion is that is_overshadowed means "overshadowed by other published segments" and I am planing to leave is_overshadowed false for unpublished segments. Will add this definition to the sys.segments docs.

The current proposal (add is_overshadowed representing published segments that are overshadowed by other published segments, with overshadowing info provided by the coordinator when polling) looks good to me.

@surekhasaharan what do you think about "includeOvershadowedStatus", "SegmentWithOvershadowedStatus" instead of "overshadowInfo"?

@leventov includeOvershadowedStatus instead of includeOvershadowInfo seems fine to me for the query param in coordinator api. So the api would be GET /druid/coordinator/v1/metadata/segments?includeOvershadowedStatus.  Did you mean to name the class "SegmentWithOvershadowedStatus " instead of "SegmentWithOvershadowInfo"? Yeah that also sounds good.

@surekhasaharan then the proposal looks good to me too.
If you plan to rename "used segments" to "published segments" across the codebase, I think it would be easier to do this after #7306 is merged, see https://github.com/apache/incubator-druid/pull/7306#issuecomment-477783437.

@leventov I do not plan on renaming "used" to "published" with this issue, this is solely focused on adding the overshadowed support. Sure, it would be best to change that terminology as a follow up PR after #7306.

Looks like it is there now and in console also

Can this be closed?

Closed by #7425


forge.sh is not using mono on linux

After I followed the manual installation instructions for linux, I tried to run forge to create a new project.
I got this:
src/Forge/temp/Forge.exe: cannot execute binary file: Exec format error

Expected Behavior
I would expect forge to just work. Is there a reason that forge.sh is not using mono when executing Forge.exe?
Current Behavior
The current forge.sh script is not using mono when executing Forge.exe
Possible Solution
diff --git a/forge.sh b/forge.sh
index d98ace5..c9863d0 100644
--- a/forge.sh
+++ b/forge.sh
@@ -2,4 +2,4 @@
 # User just ran a symbolic link which points to real Forge.exe
 # $0 is an absolute path of this symboliklink
 # $* stands for all arguments passed to the command
-"$(dirname $(readlink $0))/Forge.exe" $*
+mono "$(dirname $(readlink $0))/Forge.exe" $*

Steps to Reproduce (for bugs)

Follow the manual installation instructions. (git clone and .build.sh)
Symlink forge.sh into the $PATH
Run forge
Get error

Context
This issue didn't affect me too much, I just added mono to forge.sh. It would still be nice to not having to do that.
Your Environment
$mono --version
Mono JIT compiler version <IP_ADDRESS> (tarball Wed Feb 21 04:20:57 UTC 2018)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
        TLS:           __thread
        SIGSEGV:       altstack
        Notifications: epoll
        Architecture:  amd64
        Disabled:      none
        Misc:          softdebug
        LLVM:          supported, not enabled.
        GC:            sgen (concurrent by default)

$ fsharpc
Microsoft (R) F# Compiler version 4.1
Copyright (c) Microsoft Corporation. All Rights Reserved.

Running on Fedora27 x64

Yeah, it's a bug. Please send a PR.

Done :-)


fix registries is http generate cert.d file name err

Description
when containerRuntime.containerd.registries addr is http then generate cert.d file name err
Related Issue
https://github.com/dragonflyoss/Dragonfly2/issues/2527

You should update Chart.yaml version:

https://github.com/dragonflyoss/helm-charts/blob/main/charts/dragonfly/Chart.yaml#L6
https://github.com/dragonflyoss/helm-charts/blob/main/charts/dragonfly/Chart.yaml#L7

Add changelog to Chart.yaml:
https://github.com/dragonflyoss/helm-charts/blob/main/charts/dragonfly/Chart.yaml#L28

@NatureLR
You should update Chart.yaml version:

https://github.com/dragonflyoss/helm-charts/blob/main/charts/dragonfly/Chart.yaml#L6
https://github.com/dragonflyoss/helm-charts/blob/main/charts/dragonfly/Chart.yaml#L7

Add changelog to Chart.yaml: https://github.com/dragonflyoss/helm-charts/blob/main/charts/dragonfly/Chart.yaml#L28

done

@NatureLR DCO is required

@NatureLR DCO is required

looks like it's done


[FEA] Support Databricks 8.1 ML Runtime

Is your feature request related to a problem? Please describe.
Databricks now has an 8.1 ML runtime that supports GPUs and runs Spark 3.1.1.
Describe the solution you'd like
The Spark plugin should support the Databricks 8.1 ML runtime
Describe alternatives you've considered
Databricks 8.0 ML does not appear to support GPUs.
Additional context
Ideally we will support an 8.x LTS version, but it appears to be too early in the 8.x line for a long term support version.  Let's start with 8.1 ML, we may need to change the target supported version later.

the 8.2 ML driver version is the same as 8.1:
NVIDIA-SMI 450.80.02    Driver Version: 450.80.02    CUDA Version: 11.0

Note it looks like for the flatMapGroupsInPandas we have to turn off adaptive otherwise we hit the stack overflow issues with the estimator.
spark.conf.set("spark.sql.adaptive.enabled", "false")


feat(Combinatorics/SimpleGraph): Add lemma about number of odd subcomponents

Added lemma that the number of odd components contained within a component
in a bigger graph is odd iff the bigger component is odd. In preparation for Tuttes.

Zulip thread

Just backmerged master. Originally I refactored odd_card_iff_odd_components, but it had been shown that it could do without [DecidableEq V], and I do think it's needed for the subcomponent variant, so I kept the old stronger result.


live server does not detect changes in files in subfolders of root directory, and does not live-reload in those cases

I'm submitting a...
[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report  <!-- Please search GitHub for a similar issue or PR before submitting -->
[ ] Feature request
[ ] Documentation issue or request
[x] Other: Could be a bug, or could be an issue with my configuration. I can't find any posts that reference my issue.

Current behavior
Files in subfolders, i.e. css files in a "style" subfolder, are not picked up by the live-server and the server does not live-reload when changes are made to these files. When these files are moved out of the subfolder into the root directory, the live-server functions as it should and detects changes to those files.
Expected behavior
I am looking for a way to configure the extension so that the live server picks up changes in subfolders and not just the root folder.
Environment
I am using Firefox and Edge/Chrome
For Tooling issues:

Live Server: 5.7.5
Platform:  Windows 10/WSL Ubuntu
Visual Studio Code: 1.67.1

Let me know if there is anything else I should add that might be relevant or helpful.

I am having the same issue as well. Wondering if there is a work around for this or if this will be added as a feature in the future.


OCR as a service

Added ocr.py and a few tesseract models for people to experiment with if desired while we develop the pickit config, etc. Will be extending other PR's from this.

I'd land this sooner rather than later. Even if it's not perfect since nothing would break as it's just a service. The only I'd do is go through API of the OCR and prefix methods that are supposed to be private with _.


Accessibility: order headers into a meaningful sequence

From the accessibility audit cited in rancher/dashboard#4324, we should ensure that the order of headings should always descend from H1 to H2 to H3, etc. We should not jump from H1 to H4, for example.
Suggested Solution: Often we find ourselves choosing between UI and a11y when it comes to selecting headings. A practice that we suggest is to always use the H tags in the appropriate order and, for aesthetic reasons, use classes to adjust text size. Having classes of type .h1, .h2, .h3, etc would allow to have a semantic HTML. It is important, however, that this trick is not overused as we should still consider the user experience for users without limited vision.
Example: /dashboard/account/create-key

Not sure what the status of this is, so I am taking it out of Review and moving it into the Backlog list.

How do we break this down into workable pieces?

Accessibility has had a few tickets redone so need to check if this is now a duplicate of a more recent ticket.


⚠ Bofrost.at has degraded performance

In 77f4c22, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1370 ms

Resolved: Bofrost.at performance has improved in f5394e9 after 6 minutes.


BackTracking

Can I create a backtracking package in Java Folder to add Sudoku Solver and Substring, Subset, Permutation problems?

yep

I have created a package for Backtracking Java and sent a pull request

merged!


updating title

resolves #54

I'll approve it. I don't know if there's a ticket already to update the README file and the package.json file to also update the project/app name in those places also.

Easy enough, will do.


Idempotency error on first-class module types

As of 48659c7, Topiary reaches an idempotency error on:
let peer_functor : (module Peer.F) =
  if !listening then (module Server) else (module Client)

The first pass produces:
let peer_functor :
    (module Peer.F) =
  if !listening then (module Server) else (module Client)

and the second:
let peer_functor
    :
    (module Peer.F)
  =
  if !listening then (module Server) else (module Client)

after which a fixpoint has been reached.

If we compare with non-module values, the two valid outputs should be:
let peer_functor : (module Peer.F) =
  if !listening then (module Server) else (module Client)

(single-line mode) and
let peer_functor
    : (module Peer.F)
  =
  if !listening then (module Server) else (module Client)

(multi-line mode).


Update Node healthckeck provider and example details

Signed-off-by: Roy Golan<EMAIL_ADDRESS>

/merge possible

/hold


Compiling issue Xcode 5.1

Into KVNProgress.m class, into rotationForStatusBarOrientation method, you defined:
case UIInterfaceOrientationUnknown:
But with Xcode 5.1 this will give me a compiler error. Take a look:

(CGFloat)rotationForStatusBarOrientation {
switch ([UIApplication sharedApplication].statusBarOrientation) {
case UIInterfaceOrientationLandscapeLeft:
return -M_PI_2;
case UIInterfaceOrientationLandscapeRight:
return M_PI_2;
case UIInterfaceOrientationPortraitUpsideDown:
return M_PI;
case UIInterfaceOrientationPortrait:
case UIInterfaceOrientationUnknown:
return 0;
}
}

Just remove "case UIInterfaceOrientationUnknown:", it has no sense. In my understanding.

What is the compiler error you got?
I put this case because it was part of the enum and I prefer handle all enum cases in a switch to avoid forgot about one.

Hello
Have a look at two pictures I attached. Moreover, storyboard you did complains about Xcode 5, it wants Xcode 6.
Hope this helps.

Why do you need Xcode 5.1?
I do not think I am going to make it compatible with Xcode 5 because we'll soon have to use Xcode 6 to use iOS 8 SDK. As Apple said:

As we announced in October, beginning February 1, 2015 new iOS apps submitted to the App Store must include 64-bit support and be built with the iOS 8 SDK. Beginning June 1, 2015 app updates will also need to follow the same requirements. To enable 64-bit in your project, we recommend using the default Xcode build setting of “Standard architectures” to build a single binary with both 32-bit and 64-bit code.

Ok I agree and I think I will shift to Xcode 6 soon. I thought you wanted
to have also this compatibility. If you do not, no problem.
2015-02-04 22:28 GMT+01:00 Kevin Hirsch<EMAIL_ADDRESS>
Why do you need Xcode 5.1?
I do not think I am going to make it compatible with Xcode 5 because we'll
soon have to use Xcode 6 to use iOS 8 SDK. As Apple said:
As we announced in October, beginning February 1, 2015 new iOS apps
submitted to the App Store must include 64-bit support and be built with
the iOS 8 SDK. Beginning June 1, 2015 app updates will also need to follow
the same requirements. To enable 64-bit in your project, we recommend using
the default Xcode build setting of “Standard architectures” to build a
single binary with both 32-bit and 64-bit code.
—
Reply to this email directly or view it on GitHub
https://github.com/kevin-hirsch/KVNProgress/issues/24#issuecomment-72943142
.

Yes I will stay with Xcode 6 compatibility but I will change my README.md which precise Xcode 5. Thanks!

Ok that information in readme file does not cost anything :-)
good job anyway
2015-02-05 9:06 GMT+01:00 Kevin Hirsch<EMAIL_ADDRESS>
Yes I will stay with Xcode 6 compatibility but I will change my README.md
which precise Xcode 5. Thanks!
—
Reply to this email directly or view it on GitHub
https://github.com/kevin-hirsch/KVNProgress/issues/24#issuecomment-73008724
.

Thank you! :)


Script masks and uninstalls firewalld and then enables iptables

Hello,
I've used your script on Fedora 28.  It works well - but afterwards I had noticed firewalld had been masked and disabled.  Iptables was enabled and running instead.
After the script was completed and everything was working correctly, I disabled iptables and then unmasked firewalld and re-enabled it.  Everything seems to still work correctly -- however I wanted to ask if there is anything I should be looking out for, any problems doing this may cause?
Thanks

Hello, thanks for the feedback!
I was wondering this when the support for fedora was added: https://github.com/Angristan/OpenVPN-install/pull/134#issuecomment-352185405
I will test on Fedora to see if firewalld causes issues.

Unmasking and enabling firewalld don't cause any issue, indeed. But when you start it (or reboot the server), the trafic is blocked.


ECMDERR Failed to execute "git ls-remote --tags --heads git://github.com/jtblin/angular-chart.js.git"

Hi,
can any one help me to solve this issue.
user: ~/Documents/_IBO/02_Travail/summer $ bower install angular-chart.js
bower angular-chart.js#*        cached git://github.com/jtblin/angular-chart.js.git#0.5.3
bower angular-chart.js#*      validate 0.5.3 against git://github.com/jtblin/angular-chart.js.git#*
bower angular-chart.js#*       ECMDERR Failed to execute "git ls-remote --tags --heads git://github.com/jtblin/angular-chart.js.git", exit code of #69   Agreeing to the Xcode/iOS license requires admin privileges, please re-run as root via sudo.
Additional error details:
Agreeing to the Xcode/iOS license requires admin privileges, please re-run as root via sudo.
user: ~/Documents/_IBO/02_Travail/summer $
Best regards
Ismael

Solved issue. With validate licence of xcode because I installed MacOSX EL Capitain. :)


No command name: Add The Office Club-40 gif to the collection of possible gifs

Complete the following REQUIRED checkboxes:

[X] I have thoroughly read and understand The Odin Project Contributing Guide

[X] The title of this issue follows the command name: brief description of request format, e.g. /help: add optional @user parameter

The following checkbox is OPTIONAL:

[ ] I would like to be assigned this issue to work on it

1. Description of the Feature Request:

I saw this sweet gif that does not seem to have an author pop up in Club-40 and it is not in collection of possible gifs. I think it should be added!
2. Acceptance Criteria:

[ ] Add the gif
[ ] Use the text "Gif by Unknown" (so hopefully they'll notice)

3. Additional Information:

Here is the page from Tenor: https://tenor.com/view/dundie-award-odin-club40-gif-20404923
The user is elrolamenton, but nobody on the server matches with that name.

Can I take this?

@rishikumars-in all yours

@rishikumars-in  reply here with your questions / concerns  :)

@JustWaveThings Thanks. I don't know where to start the work. Elaborate more & Guide me on how to add the specified GIF.

@rishikumars-in https://github.com/TheOdinProject/odin-bot-v2/blob/main/botCommands/club_40_gifs.json
I also updated the original issue to include that link. Does it help you sufficiently?

@zachmmeyer Thanks for your help. Added the gif and created pull request. Hope I did it in the right way. 😊

@rishikumars-in you did perfect.


Spam in the Server Console

I am not sure if this is intended, but I am curious why my server console is always spammed with this. I had this since I first added Harvest Festival and it is still present. If this is a bug, I would ask you to fix this if possible since it makes scanning the console really hard. Also sometimes there are two Yulifs. Both of this events happen when multiple villages are set up ( even when the required distance set in the config is respected this happens )

Already addressed in https://github.com/PenguinSquad/Harvest-Festival/issues/89 and a solution was found to it :)

This happens when vanilla persists an entity. Which version are you on.

One of the most recent ones. Will update tomorrow. If it still happens I will reply to this

Yeah since it's happening every 20 minutes aka when a new day starts, more than likely because it's doing the loading of chunks/unloading when placing/removing logs or rocks, which loads/unloads the entity. The message is an annoying vanilla one. I stopped the ticking of towns that are unloaded in latest, should just mean those blocks won't change unless something is loading the chunk.


Replace Spring config for CDX-server

By using Spring for configuration almost all non private methods inn all classes must be considered as part of the API. By replacing config with some other, more restricted mechanism, this is avoided. In the short term this is only doable for the CDX-server since the configuration options here are relatively few.

Although I'm sympathetic about pain with Spring-based configuration, but I'm not sure this is the right move. My thoughts are:

Spring does not allow for calling methods - just configuring properties (I'm assuming "methods" is just a slip of finger). Concern of "being considered as part of the API" can be addressed with careful class design and documentation.
With typesafe config, (apparently) we need to implement Settings object that does config validation, translation etc. While this sounds fine for configuring well-established set of parameters within particular deployment, It'd be painful to do for entire Wayback. Is typesafe language powerful enough to configure new type of index sources without much glue code? If we try to make typesafe config-based configuration powerful enough, we may find ourselves developing alternate syntax for Spring.
Some deployment (yes, IA :-) utilizes Spring goodies like bean factory, MVC, etc. Spring is more than configuration mechanism. Probably typesafe config should be considered as the replacement of properties file, and used alongside Spring, so that only advanced deployment would require modification to Spring config.
We're going to make a big change toward 3.0.0. It may be too early to work on a custom configuration syntax.


could not resolve dependency: npm ERR! peer redux@"^4" from<EMAIL_ADDRESS>

@8enSmith

This is not a Redux issue.

then what might be the reason behind this issue


excludeFields of pieces with joins ends up responding with the data from the piece without the _joins

Example:
https://gramadosummit.com/api/v1/lectures
Has a _speaker join.
But when getting thata from https://gramadosummit.com/api/v1/lectures?excludeFields=type,slug,createdAt,updatedAt,titleSortified,highSearchText,highSearchWords,lowSearchText,searchSummary,docPermissions,_originalWidgets,siteMapPriority,userId,tags
That join vanishes from the object.

Hi Pietro, we just published a new release that addresses this. In a way, it was not a bug. But it is confusing and not obvious that excluding type from the mongo query impacts joins for internal Apostrophe reasons. So we changed it so that type is deleted from the objects at the end but included in the initial query.


Prometheus metric configmap name is incorrect

[Enter feedback here]
After deploying the AKS cluster and from the portal adding the managed prometheus cluster with Azure Managed Grafana the ama-metrics pods don't use the config map 'ama-metrics-prometheus-config'. Apparently the name has changed to use anotherr configmap 'ama-metrics-prometheus-config**-node**'
see image

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 493904b0-19cf-d0ad-7731-d722bcbf5198
Version Independent ID: a1606fad-f481-9927-b4f4-1b0d3fb068e8
Content: Create, validate and troubleshoot custom configuration file for Prometheus metrics in Azure Monitor (preview) - Azure Monitor
Content Source: articles/azure-monitor/essentials/prometheus-metrics-scrape-validate.md
Service: azure-monitor
Sub-service: essentials
GitHub Login: @EdB-MSFT
Microsoft Alias: edbaynash

@emilverwoerd
Thanks for your feedback! We will investigate and update as appropriate.

@emilverwoerd Thanks for your feedback.
Assigning to content author @EdB-MSFT  for review.

Please refer this doc for details on the configmaps https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/prometheus-metrics-scrape-configuration#configmaps.
[ama-metrics-prometheus-config] is used for configuration of any cluster level services discovery and scrape.
[ama-metrics-prometheus-config-node] is used for node level target configuration for scraping on Linux nodes.
[ama-metrics-prometheus-config-node-windows] is used for node level target configuration for scraping on Windows nodes

Hi @emilverwoerd, I home this clarifies things for you. Thanks for point this out to us.
#please-close


Missing distinction between public and confidential clients

Currently there  is not distinction between confidential and public clients as it is needed by RFC6749
We should add an attribute "type" for the Client-Object.
In the Authorization Grant Flow Access Token is used, we need not only the client_id in the payload but also the client credentials in the authoriation header if it is a confidential client. see RFC 6749 4.1.3
Currently it is not really based on the Client but on the grant_type and the requireClientAuthentication option. As it lacks distinction theoretically a public client has to send client_secret.

So at the moment we assume all clients are private clients.
To implement this we should

keep assuming al clients are private
allow to pass a client type
public clients should not fail getClientCredentials in token-handler.js

https://github.com/node-oauth/node-oauth2-server/blob/aaf28b4c5479d7f406046d8e8da2fc505c3e3326/lib/handlers/token-handler.js#L173-L199
In conclusion, this would require some architectural changes since the validation is done before the client is fetched.


ROX-16899: change error type

Description
A detailed explanation of the changes in your PR.
Feel free to remove this section if it is overkill for your PR, and the title of your PR is sufficiently descriptive.
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
TODO(replace-me)
Use this space to explain how you tested your PR, or, if you didn't test it, why
you did not do so. Valid reasons include, for example, "CI is sufficient",
"No testable changes". Feel free to attach JSON snippets, curl commands,
screenshots.
In addition to reviewing your code, reviewers must also review your testing
instructions and make sure they are sufficient.

Current dependencies on/for this PR:

master

PR #5932   👈

This comment was auto-generated by Graphite.

/test e2e

/test gke-nongroovy-e2e-tests

/retest

/test gke-nongroovy-e2e-tests


Qualitative Results

Nice work on the repo.
Maybe there should be some (unranked) honorary mentions for non quantitative / semi-quantitative results?
e.g. for image completion/inpainting
http://hi.cs.waseda.ac.jp/~iizuka/projects/completion/data/completion_sig2017.pdf
image translation
https://arxiv.org/abs/1703.10593
generative models
http://research.nvidia.com/sites/default/files/publications/karras2017gan-paper-v2.pdf

That a nice idea. Sure will do it.


Minor issues

Some minor (GUI) items I noticed:

In the issue screen the 'user' field is labelled ' organization
In the admin page custom field 6 is shown when custom field 5 is enabled

Thanks so much. I fixed the two spots in the commit just now.  I reacted to the bugs without noticing you had created a fix. Thanks.

@tcplomp  - Are you actually going to be using Budoco for something? Did you used to use BugTracker.NET? What are the features missing from Budoco that you wish it had?


Draft: Child Deallocation

Planned for 2.1
Changelog:

Only add children after a transition is finished. This will hopefully reduce the likelihood of deallocation issues, but this needs extensive testing to make sure no other issues arise.

When will this be released?

@pauljohanneskraft any updates on this?


Allow users to check for an update

Put a button in the settings so that users can manually check for an update outside of just when the app opens.

This will be implemented in #17.


Wma/newdocs

fixes 113

Codecov Report
Patch coverage: 10.00% and project coverage change: +0.33 :tada:

Comparison is base (38350a9) 78.27% compared to head (2cc7c3d) 78.60%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #145      +/-   ##
==========================================
+ Coverage   78.27%   78.60%   +0.33%
==========================================
  Files          47       47
  Lines        4607     4627      +20
==========================================
+ Hits         3606     3637      +31
+ Misses       1001      990      -11

Impacted Files
Coverage Δ

src/levels/elementlevels.jl
86.20% <0.00%> (-3.08%)
:arrow_down:

src/levels/patternlevels.jl
50.00% <0.00%> (-2.39%)
:arrow_down:

src/util.jl
82.05% <0.00%> (-10.26%)
:arrow_down:

src/execute.jl
88.27% <100.00%> (+2.85%)
:arrow_up:

src/fibers.jl
68.11% <100.00%> (ø)

... and 2 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


How many times deliveries are retried?

Hi.
We are using a post in our company and we would like to know how many times a failed email delivery is retried.

According with postal.defaults.yml,
https://github.com/atech/postal/blob/634d3af59d392e84bdcd2b843b427f3a79d3ff4c/config/postal.defaults.yml#L14

Great!
Thanks a lot!


add string_to_object function and fix the ascii header

This is a first fix to the immediate problem. If we want the filter names, we need to define what these names are, and how we gather them.

in the ascii file it is a bit silly to repeat the number of filters on each line.....


Documentation on raspibrew.com needs updating

Hi Steve. Looks like the new directory structure needs to be reflected on the setup page:
http://raspibrew.com/setup/
It may also need re-writing since the setup script handles a lot of the content on that page. I'm liking the increased plug-and-play-ness!

Thanks for letting me know.  I'll fix it.
On February 8, 2015 8:30:09 PM EST, Josh<EMAIL_ADDRESS>wrote:

Hi Steve. Looks like the new directory structure needs to be reflected
on the setup page:
http://raspibrew.com/setup/

Reply to this email directly or view it on GitHub:
https://github.com/steve71/RasPiBrew/issues/14

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

I'm finding some weirdness which I think is related to the new setup. I'm not sure what the scaling governer stuff is, but I commented out the contents of raspi-config and raspi-config.dpkg-dist (which seem to be duplicates) and my SSRs don't seem to be getting the right signals. It's supposed to be at 100% but instead of a solid light it looks like it's about 30%-40%. I'm not sure what's going on, but it does seem that the setup script isn't backwards compatible.
Should I be opting for the contents of /etc/init.d/raspi-config?


netlify dev reload causes error: "Module did not self-register" with node-canvas

Describe the bug
This is the same as #2641.
To Reproduce
Steps to reproduce the behavior:

Run git clone git@github.com:joshuaellis/netlify-dev-canvas-bug.git
Navigate to the cloned repository
Run yarn to install the deps
Run netlify dev
Navigate to http://localhost:8888/.netlify/functions/generate-static?handle=123
It'll work!
Change something in the function e.g. the statusCode
Refresh http://localhost:8888/.netlify/functions/generate-static?handle=123
It'll fail saying Error: Module did not self-register: ...

Configuration
[build]
  functions = "netlify/functions"
  publish = "public"

[[redirects]]
  from = "/api/generate/dynamic"
  to = "/.netlify/functions/generate-dynamic"
  status = 200

^^^ this is included in the repo
  System:
    OS: macOS 12.2
    CPU: (10) arm64 Apple M1 Pro
    Memory: 128.91 MB / 32.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 17.6.0 - ~/.nvm/versions/node/v17.6.0/bin/node
    Yarn: 3.2.0 - ~/.nvm/versions/node/v17.6.0/bin/yarn
    npm: 8.5.1 - ~/.nvm/versions/node/v17.6.0/bin/npm
    Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
  npmGlobalPackages:
    netlify-cli: 9.10.0

Expected behavior
Not to unregister and require me to manually stop and start the dev server
CLI Output
If applicable, add the CLI output to help explain your problem.
Request from ::1: GET /.netlify/functions/generate-static?handle=123
{"level":"error","message":"End - Error:"}
{"errorMessage":"Module did not self-register: '/Users/josh/code/netlify-dev-canvas-bug/.netlify/functions-serve/generate-static/src/node_modules/canvas/build/Release/canvas.node'.","errorType":"Error","level":"error","stackTrace":["Object.Module._extensions..node (node:internal/modules/cjs/loader:1181:18)","Module.load (node:internal/modules/cjs/loader:975:32)","Function.Module._load (node:internal/modules/cjs/loader:822:12)","Module.require (node:internal/modules/cjs/loader:999:19)","require (node:internal/modules/cjs/helpers:102:18)","Object.<anonymous> (/Users/josh/code/netlify-dev-canvas-bug/.netlify/functions-serve/generate-static/src/node_modules/canvas/lib/bindings.js:3:18)","Module._compile (node:internal/modules/cjs/loader:1097:14)","Object.Module._extensions..js (node:internal/modules/cjs/loader:1151:10)","Module.load (node:internal/modules/cjs/loader:975:32)","Function.Module._load (node:internal/modules/cjs/loader:822:12)"]}

Closing as stale. Please re-open if needed

@sarahetter, are you able to explain how you think an issue is stale when no one has replied? :)

Hi @joshuaellis
I'm sorry you didn't get a response when you posted this. However, as we haven't had any other reports of this issue, and we are in the process of combing the backlog for priority issues in the netlify-cli, I have marked this as stale.
If this is still an outstanding issue for you, feel free to reopen or post in the Netlify Support Forums


reorganise presets and entries with providers subdirectories

Describe the feature
As we keep adding more presets, we should group them under provider sub-directories.
Additional information

[X] Would you be willing to help implement this feature?

Let's followup via #845. First step is to convert structure into a monorepo like one.


Added login page with UI

Built the login page and attach the link to the login button

enhance the page


fix: do not create unwanted record in history when redirecting after an invalidation

Closes https://github.com/sveltejs/kit/issues/11896

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[ ] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[ ] This message body should clearly illustrate what problems it solves.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

[ ] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[ ] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

Edits

[ ] Please ensure that 'Allow edits from maintainers' is checked. PRs without this option may be closed.

closing this as the issue https://github.com/sveltejs/kit/issues/11896#issuecomment-2413047820 has been closed as well


Update fossa link to point from contrib to dotnet

Thanks for opening this, I was just going in order on the pull requests and apparently Bernd's PR does the same thing right above it in the list #1105. I merged that one first so this one is redundant.


hide sensor?

hi
we've a problem (huston copy)
I installed the API for the nobis fire stove, my stove has 2 ducts, but as an entity in Home Assistant I only see 1 duct, the controls for the second duct are missing, then there would also be the room temperature sensors for both the first canalization and the second canalization.
integration is required
thanks!!

Hi, please provide a screenshot of the available entities and attach your diagnostic file.

the stove is  unica nobis fire

1 is the rear (second) sensor temerature
2.. it s the first.... I can choise 2 setting ... to use the external thermostat (now I use it) or use the sensor temeprature in the stove remote control wich i don't know 'casuse if i active it the temperatrue in the display is 99°.....always....I'll write to nobis fire service....

Is there also a temperature setting for the rear vent? Can you maybe also post a screenshot of the "Regolazioni" tab?

Is that?

Please try v0.2.9-beta3

how i can try? i must update?...or...?
I'm sorry I'm a beginner

very strange, because, for now I have only looked at the functions and have not tried them, but with the new beta release I see the temperature of the temperature probe of the second ducting and the temperature of its target

@merlino1975 Are things working for you now?
An external thermostat will only override the main temperature control, not of any ducts/canalizations. If you want to use the main temperature control in HA you have to switch to the stove's built-in thermostat.

I will try to be more precise in the description. I apologize for my poor English. The stove has the possibility of using 3 temperature sensors: 1) a sensor is present in the stove remote control 2) an external thermostat to which you can only give contact. Ton or T0ff (practically performs the task only as a switch for the stove: when the room temperature is lower than the set temperature then the stove has maximum power set, if the room temperature is higher than the one set then the stove has minimum power) 3) the temperature sensor for the secondary ducting in HA I would need the temperature sensor of the remote control but if you can't do it anyway. I should be able to create the routine using a temperature sensor from another device. For now I'm still testing, I'm trying to understand how to use the new entities, it's a bit difficult for me because I'm a beginner..

All the sensors you are talking about are currently implemented in the integration. But you need to select the correct temperature/thermostat for your stove to operate on in your stove’s app. If you do that Home Assistant will follow.
If you believe you are missing something, please make a screenshot of the corresponding control/sensor in your stove’s app.

Well...when term ext is attivate then in app

When sensor remote control are attive the in app

Both are implemented. But you need to reload the integration after switching thermostat mode in the stove app.

I must update?

okey..now I see 13 entities....and is all okey..but...I don't undestand.. I wold like to schedule the power of pellet about a determinate temperature in envyroment..but when I search device stufa.Salotto..I see wood parameters...but i wuold like to see pellet parameters...
he is a problem of my configuration or can you correct? in attach the pic.

in reality it is possible that it will have to program both types of fuel

The climate entity adjusts to the mode the stove currently is in. For a hybrid stove the individual stove and pellet power controls are also available as separate entities.

Okey...and I would like understand...what the entità of the power of pellet or wood...? Because I see only fan speed...but power and fan speed are tuo separate entity...you can have power four and fan speed two...for example...well..or i can use a Mode called "auto" wich set power and fan speed for to reach fast and in economy the scheduled temperature

So I can use that...

And Or that

For hybrid stove you have access to Wood power and Pellet power entities. It's number entities, not climate attributes.

okey!!!!


Delete after collapsed code fold

Delete next line of the collapsed code fold will move the row after uncollapsed line. It should move in the last line of the collapsed code.

Fixed but needs more testing and refactoring.


chore(master): release 2.8.0

:robot: I have created a release beep boop
2.8.0 (2024-09-11)
Features

add the unique identifier of the request's location in the code (e9eb95f)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/keq-request/keq/releases/tag/v2.8.0 :sunflower:


Add OSGi metadata

Fair point. I'm a bit busy this week but I will try to add in the maven bundle plugin and then do a release ASAP.

I propose adding the metadata without changing the packaging type from JAR using a combination of the maven-bundle-plugin and the jar plugin. When I do that, it generates a MANIFEST.MF with the following:
Manifest-Version: 1.0
Bnd-LastModified:<PHONE_NUMBER>655
Build-Jdk: 1.8.0_144
Built-By: patvanka
Bundle-Description: An RxJava API for handling MQTT messages with an imp
lementation using the Paho Java MQTT library.
Bundle-License: http://www.apache.org/licenses/LICENSE-2.0.txt
Bundle-ManifestVersion: 2
Bundle-Name: rxmqtt
Bundle-SymbolicName: net.eusashead.mqtt.rxmqtt
Bundle-Version: 1.2.0.SNAPSHOT
Created-By: Apache Maven Bundle Plugin
Export-Package: net.eusashead.iot.mqtt;uses:="io.reactivex";version="1.2
.0",net.eusashead.iot.mqtt.paho;uses:="io.reactivex,net.eusashead.iot.m
qtt,org.eclipse.paho.client.mqttv3";version="1.2.0"
Import-Package: io.reactivex;version="[2.1,3)",io.reactivex.functions;ve
rsion="[2.1,3)",net.eusashead.iot.mqtt,org.eclipse.paho.client.mqttv3;v
ersion="[1.1,2)",org.eclipse.paho.client.mqttv3.persist;version="[1.1,2
)"
Require-Capability: osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=1.8))"
Tool: Bnd-<IP_ADDRESS>609221906
Is that sufficient for your needs?

Yes, fine. Thanks

I've pushed a new release to Maven today (1.1.1.RELEASE) that features the OSGi metadata and upgrades to the Paho and RxJava2 dependencies. Can you let me know if that works for you and I will close this if so.


Fuse Input to Indicate HW Version/Stepping

Requirement: The FIPS module needs to version everything to help users match a version with a security policy to verify that the module is correctly validated.  HW must have a version indicated.  Any time a new mask is created for HW, a new version needs to be indicated.
Description: A fuse register will be created for inputing the HW version.  This value needs to be provided to FW for collecting of the versions and reporting on the versions on request.

Maybe have the major version embedded in the RTL? Then if there is an ECO-type change then the fuse can be used to indicate that.

CPTRA_HW_REV_ID can have a major/minor versions set to it.  The major will be specified by the IP, and the minor can be updated by the integrator at integration time.
This will need to be reved for each stepping.

This issue is trending to be an implementation guide update where the CPTRA_HW_REV_ID register will be updated to have major/minor values.  The major will be owned by Caliptra WG and the minor will be updated by the integrator based on HW tape-out.
The Integrator would be required to ensure that the minor version was distinct for each HW revision released.

@bharatpillilli was this implemented?

Updated reg to contain the following fields:
CPTRA_GENERATION
SOC_STEPPING_ID (written through a fuse upon reset)


Fix pattern search error message [Fixes #153970474]

Error message was messed up because of missing symbol.
Added symbol.

Coverage remained the same at 94.657% when pulling 3847e9c04a658df55c0b9515adcd8c9032b0a0d3 on JoeCohen:search-error-msg into 1d922b68e8062bef321309d45c6866436ef42f5c on MushroomObserver:master.


Unable to Generate Vue Source Code

So currently my browserify script looks like this
const browserify = require("browserify");
const babelify = require("babelify");
const vueify = require("vueify");
const fs = require("fs");

process.env.NODE_ENV = 'development';
const browserConfig = {
    entries: 'app/src/main.js',
    extension: ['.js', '.vue'],
    ignoreMissing: true,
    detectGlobals: false,
    bare: true
};
browserify(browserConfig)
    .transform(vueify, {babel: {presets: ["es2015"], plugins: ["transform-runtime"]}})
    .transform(babelify, {presets: ["es2015"], extensions: ['.js', '.vue']})
    .bundle()
    .pipe(fs.createWriteStream('build/bundle.js'));

and it appears that my vuejs modules are NOT being copied into the bundle.js, I can tell as when I command f for any of the core source code like strings it is empty. I am not sure what I am doing wrong but any help would be great. Also as a note I am using electron, vuejs and gulp. I am not sure if that helps but it does give a little context.
app/src/main.js
import Vue from 'vue';
import Electron from 'vue-electron';
import Resource from 'vue-resource';

import '../node_modules/materialize-css/dist/css/materialize.min.css';
import '../node_modules/materialize-css/dist/js/materialize.min.js';

Vue.use(Electron);
Vue.use(Resource);
Vue.config.debug = true;

import App from './app'

/* eslint-disable no-new */
new Vue({
    el: 'body',
    components: {App}
});

what versions of vue and vueify are you using?
how do you bundle the imported CSS? I don't see a transform for .css.

Besides the CSS thing I don't see an immediate problem. A reproduction would be helpful

I would like to apologize the problem ended up being a user error of having a file without the require without the .Vue in it leading to the tool being unable to find it. This issue can be closed. Thanks for the quick support

Hi I would like to open this issue backup @LinusBorg and @yyx990803 So after some more changes the code ended up failing again. It was working for a bit but ended up failing again and i realized that when it was building it wasn't importing everything. The link to the repository is here if you would like to take a look. The file I am using to test is test.js. And all I do is run node test.js and after it executes I look at the results in build/bundle.js and for some reason there appears to be an empty file and nothing else. Any insight would be great!
test.js
const browserify = require("browserify");
const babelify = require("babelify");
const vueify = require("vueify");
const fs = require("fs");
const debug = require("gulp-debug");

console.log("Starting");
process.env.NODE_ENV = 'development';
const browserConfig = {
    entries: 'app/src/main.js',
    extension: ['.js', '.vue'],
    debug: true
};
browserify(browserConfig)
    .ignore('electron')
    .transform(vueify, {babel: {presets: ["es2015"]}})
    .transform(babelify, {presets: ["es2015"]})
    .bundle()
    .pipe(fs.createWriteStream('build/bundle.js'));

console.log("Done");

Let me know if you guys need anything else.


Update libphonenumber metadata to v8.12.10

The new invalid GB test number was taken from here.

Hi,
I'm sorry, it's not that simple.
You have to include the changes that were made in the code too.

No problem! When all the tests passed, I thought that was easy :sweat_smile:
Thanks for clarifying that.


[PE-D][Tester C] Tag inputs are not case insensitive

Labels: severity.Low type.FeatureFlaw
original: matochichap/ped#11

Can make risk level case insensitive.


added docs for ubuntu setup of postgres, sdkman, java and sbt

docs added with the necessary instructions for newbies on ubuntu

@AlexITC


fix(ffe-form-react): Moved tooltip button id generation to constructo…

…r to avoid unnecessary DOM-updates.
Fixes @ivarni's comment on PR #689.

Coverage increased (+0.008%) to 81.995% when pulling 1c0136ced8a4e84e943da10bb32368061bcf8327 on fix/tooltip-id-generation into 957973bb5690ea160464c88828a03579d4dfa5d8 on develop.

The changes looks good, but the commit message is a bit weird.
The description should be a quick summary, and it's usually not started with a lower case. Then you may elaborate in the optional body.
How about something like this?
fix(ffe-form-react): move id generation to constructor

Moved tooltip button id generation to constructor to avoid unnecessary
DOM-updates.


Add contextual label for Param Handling ("Determine where...")

Similar to how the Labels in the message modification scope change based on which radio button is selected, we should consider doing this for the Match Options label also.

Done, and also linked the other label, "Insert/Replace existing value with this one..."
Tested that it works with quickload and import config.


Useless Code in "PostJobContractLine" in CU 80 "Sales-Post

I am not really sure, if this is the correct Spot for a suggestion like this. I stumbled upon this today and thought it might be considerable to change:
In the Microsoft_Base Application_18.1.24822.25874.app in the Sales-Post Codeunit (80), i found following Code in the local Procedure "PostJobContractLine"(SalesHeader: Record "Sales Header"; SalesLine: Record "Sales Line")
    if SalesLine."Job Contract Entry No." = 0 then
        exit;
    if (SalesHeader."Document Type" <> SalesHeader."Document Type"::Invoice) and
       (SalesHeader."Document Type" <> SalesHeader."Document Type"::"Credit Memo")
    then
        SalesLine.TestField("Job Contract Entry No.", 0);

    SalesLine.TestField("Job No.");
    SalesLine.TestField("Job Task No.");

    if SalesHeader."Document Type" = SalesHeader."Document Type"::Invoice then
        SalesLine."Document No." := SalesInvHeader."No.";
    if SalesHeader."Document Type" = SalesHeader."Document Type"::"Credit Memo" then
        SalesLine."Document No." := SalesCrMemoHeader."No.";
    JobContractLine := true;
    JobPostLine.PostInvoiceContractLine(SalesHeader, SalesLine);
end;

The Testfield on the "Job Contract Entry No." can´t be false, because the Condition directly before prevents SalesLine with "Job Contract Entry No." = 0 to enter this Conditional Statement.
So i would delete the second conditional Statement + useless Testfield on "Job Contract entry No." = 0
The other thing i found quite astonishing, was the assigning of the SalesCrMemoHeader."No."\SalesInvHeader."No." to the regular Sales Line."Document No." . I don´t know the whole process very well, but this is the first time i see something like this instead of just saving the Value in a variable/parameter or directly create a SalesCrMemoLine/SalesInvLine.
I´m looking forward to read your answer.
With kind regards,
Simon , MS-Partner

Does this code works incorrect? We are doing extensibility requests here, and technical support team working on bug fixes.

No, as far as i know is this Code working just fine. I honestly just thought about the optimization of saving a line of Code and was curious about the process of saving a Posted Sales Header "No." in an unposted SalesLine. I am sorry for any inconvenience i created if this is the wrong section for suggestions and questions like mine.


Fixes a syntax error in vehicle.rb with ruby 1.9.3

Fixes a syntax error in the command definition of vehicle.rb that I got with ruby 1.9.3p484 (2013-11-22 revision 43786) [i686-linux].
This was the error:
/usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': /var/lib/gems/1.9.1/gems/tesla_api-1.2.0/lib/tesla_api/vehicle.rb:145: syntax error, unexpected tLABEL (SyntaxError)
    def command(name, body: nil)
                           ^
/var/lib/gems/1.9.1/gems/tesla_api-1.2.0/lib/tesla_api/vehicle.rb:149: syntax error, unexpected keyword_end, expecting $end

Coverage remained the same at 90.598% when pulling f02e826bb8e1bfef445c1a49d85d173ce5a4990f on ErikDeBruijn:master into 3062a73faea3f60edea94fa1207d8f01d47132f9 on timdorr:master.

That's a keyword argument. We don't support Ruby<2


Deprecate the archives configuration

The archives configuration functions as a central point for controlling which tasks are executed when executing the assemble task. The assemble task depends on all task dependencies of the archives configuration. Instead, users should directly add task dependencies to the assemble task with dependsOn without using the archives configuration as a middle-man.
Further, artifacts that are registered with the DefaultArtifactPublicationSet are conditionally added to the archives configuration if they are determined to be a "default artifact", however this only works properly for jars, wars, and ears. This process can work in unintended ways in certain edge cases depending on the order that artifacts are registered.
To deprecate the archives configuration, we should first deprecate the configuration for consumption. Then, we should add a specialized deprecation warning to the archives artifact  set that directs users to instead directly declare their task dependencies on the assemble task. Finally, as a migration path, we should directly add artifacts registered with the DefaultArtifactPublicationSet directly to the archives configuration. In 9.0, we can update these artifact registrations as task dependencies to the assemble task.

If we say a lifecycle task always defines it dependencies directly via dependsOn, build should also do that. That is, all tasks  that want to wire into the build lifecycle should add an explicit dependsOn to the build task. (similarly as it is done e.g. for assemble).

We should attempt to fully deprecate the "archives" and "default" configurations by also deprecating them for consumption here:
https://github.com/gradle/gradle/blob/2d0225d7406122d7e345f90607438e2ddd85cc07/subprojects/plugins/src/main/java/org/gradle/api/plugins/BasePlugin.java#L91-L94

We should attempt to fully deprecate the "archives" and "default" configurations by also deprecating them for consumption here:
https://github.com/gradle/gradle/blob/2d0225d7406122d7e345f90607438e2ddd85cc07/subprojects/plugins/src/main/java/org/gradle/api/plugins/BasePlugin.java#L91-L94

blocked by #25810