Add logs to the crucial steps

name
title
about
labels
assignees

Transparency Request
Add logs to the crucial steps

Describe the area of code that needs more transparency:
Add logs to the crucial steps that give feasibility to the user to revert changes
Describe the solution you'd like:
Describe the alternatives you've considered:
Additional context or comments:
Add logs to the crucial steps(aggregation) which give the feasibility to the user to revert changes if something goes wrong.
Log storage options, recommend config options (at least) for both Mongo Atlas DB and local storage

Changes to capture logs for crucial functions in AI-Starter is completed. Changes are integrated with development branch.
Logging functionality is added for capturing

Pipeline
Experiment Design
Micro-service Design


Add a new example when one nsc connects to two nses with different services

Scenario

Deploy nsm infra
Deploy nse1 with ns1
Deploy nse2 with ns2
Deploy an external nse with annotation:  networkservicemesh.io: kernel://ns-1/nsm-1, kernel://ns-2/nsm-2
Make sure that pings works for both nses

Note: nse1 and nse2 should have uniq cidr

Seems like done


How to set up Watermode and Fan Speed levels

I'm very new to Homebridge and I don't really understand much of it. Where and how exactly do I have to set the fan speed and water level modes? I already have the basic configuration. Model is S5 Max.
"name": "Jarvis",
"ip": "xxx-xxx-xx-xx",
"token": "token",
"waterBox": true,
"silent": false,
"pause": false,
"pauseWord": "Pause",
"findMe": false,
"findMeWord": "Where is Jarvis?",
"dock": true,
"cleanword": "Start Jarvis",
"roomTimeout": 0,
"autoroom": false,
"accessory": "XiaomiRoborockVacuum"

I think https://github.com/homebridge-xiaomi-roborock-vacuum/homebridge-xiaomi-roborock-vacuum/issues/439#issuecomment-1073837452 answered this question 😇


error[E0658]: use of unstable library feature 'renamed_spin_loop'

When trying to set up a new machine (a VM) to run knix using the ansible scripts, i ran into the following error:
error[E0658]: use of unstable library feature 'renamed_spin_loop'
 --> /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/parking_lot_core-0.9.7/src/spinwait.rs:9:5
  |
9 | use core::hint::spin_loop;
  |     ^^^^^^^^^^^^^^^^^^^^^
  |
  = note: see issue #55002 <https://github.com/rust-lang/rust/issues/55002> for more information

error[E0658]: use of unstable library feature 'renamed_spin_loop'
  --> /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/parking_lot_core-0.9.7/src/spinwait.rs:16:9
   |
16 |         spin_loop()
   |         ^^^^^^^^^
   |
   = note: see issue #55002 <https://github.com/rust-lang/rust/issues/55002> for more information

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0658`.
error: could not compile `parking_lot_core`.

To learn more, run the command again with --verbose.
warning: build failed, waiting for other jobs to finish...
error: build failed
make[1]: *** [Makefile:26: target/release/TriggersFrontend] Error 101

Searching online led me to this issue on another project that suggested updating rust to 1.54, presumably a version that has integrated this feature into the stable branch. When i tried changing this in build_env.mk it seemed to cause other problems later on, so maybe this is a more complicated fix

looks like rust 1.49 was where spin_loop became stable
that seems to have much fewer errors during the build than 1.54

looks like theres a known issue where a breaking change (without a subsequent semver bump) was made to the library

Hello,
Thanks for looking into this issue. The triggers frontend is an
optional component, so if you want to check the remaining parts, feel free to skip installing that one.

Thanks for looking into this issue. The triggers frontend is an optional component, so if you want to check the remaining parts, feel free to skip installing that one.

Thanks for the info! I might give that a try, but it would be nice to fix the issue and be able to use the amazing-looking UI that you included screenshots for in the README (thank you for this BTW, not a lot of other maintainers do that and its super helpful).
Since I'm looking at this codebase for a class project, I have some limited time/interest to contribute to the project if that would help! I'd be interested in learning more about the rust components of this odebase in case that would help!

By all means, go ahead!
The rust component, TriggersFrontend, is really optional and is not required for the GUI to function (maybe a small portion of the GUI will not be available).

Oh i assumed Triggers Frontend was the frontend itself. Can you point me to what file i might look at modifying in order to disable it?

Nope.
Check out deploy/ folder. If using ansible, just don't make any host triggers frontend. If using helm, start from the Makefile.

If using ansible, just don't make any host triggers frontend.

as in remove all hosts from the [triggers_frontend] section of the inventory.cfg? Wouldnt that break something since the README says this:

At least one host should be in [management] and [triggers_frontend] group.

That should be fine.


"local.settings*.json" needs to be "local.settings.*.json"

[Enter feedback here]
"local.settings*.json" needs to be "local.settings.*.json". One dot is missing:).
Document details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 350f3c75-18da-fb00-48a0-c1da1fb4a894
Version Independent ID: d07bf94d-3523-9c5e-7eba-5774528d44ad
Content: Configure application settings for Azure Static Web Apps
Content Source: articles/static-web-apps/application-settings.md
Service: static-web-apps
GitHub Login: @burkeholland
Microsoft Alias: buhollan

@Joan-SHI Thanks for the feedback! We are currently investigating and will update you shortly.


[UI] Compose YAML action doesn't preserve logging driver configuration

Following YAML parts are getting lost when you click Compose YAML:
log_driver: gelf
log_opt:
  gelf-address: udp://logstash:12201

Not big deal until you blindly copy/paste generated YAML and end up with no logging at all :fearful:

Duplicate of #2388


WAP to print LowerHalf and UpperHald of a triangular matrix using cpp

@sachin-duhan26 I want to work on this issue.


Manual Require Added Till Merging Of Autoloading Fix #4420

BUGS:
Link: https://github.com/bagisto/bagisto/issues/4420
Manual requires added inside specific controller's method, I will remove it once my autoload issue pr got merge.

Sorry to be late, it has been merged now, the new version 5.5.2 with the required fix has been released. Thanks for your support in resolve this issue.

Sorry to be late, it has been merged now, the new version 5.5.2 with the required fix has been released. Thanks for your support in resolve this issue.


ES6 spread operator in ES5

What's the best (and shortest) way to translate this to ES5:
return [...state, {
  text: action.text,
  completed: false
}];

It looks to me that a (deep?) copy of the state array should be created, with the new state at the end. I had a look what Babel would do, but it generates a big function that is probably not necessary for this little use case.

In this example, all the array spread syntax is doing is copying all the existing elements into the new array.
return state.slice().push({
    text: action.text,
    completed: false
});

@hunterc Array.prototype.push returns the new length of the array. You need to split it up like this.
var myNewValue = state.slice(); // Make a copy of the state array
myNewValue.push({ text: action.text, completed: false });
return myNewValue;

return state.concat( [ { text: action.text, completed: false } ] );

state.concat(newStuff) is right as @danmartinez101 said.
state.slice().push() will work too because slice() copies the array, but it can be misleading to beginners who might think doing push()es is fine.

hey guys,
should the returned array should be the reducer itself or can i update an array which sits under an object, like so:
stories {
    isFetching: false,
    items: [...]
}

how can i push ri 'items' and return the new state?


Allow dragging editable children

Fixes #84144
Nodes from an instantiated scene was prevented from being dragged. This makes sense since editable children are not supposed to be rearrange. But it also prevents editable children from being dragged into other areas like the script editor and the Inspector.
This PR moves the "any node from an instantiated scene" check from when dragging to when dropping.

Thanks!

Cherry-picked for 4.2.1.


ci: remove nightly image build

We are not using this image anywhere, let's get rid of it.

test-nightly

Coverage decreased (-0.02%) to 36.861% when pulling cb612356fe41035d4b552b26784e4235822f9daa on pr/remove-nightly-image into 60786b613c8b7e89e312cb464c59ed105164b8f8 on master.

Nightly failed on unrelated issue, but at least the tests were run. Merging.


Is this a correct way to save/load params?

Hi simply saved the params from the trained model using jax.numpy.savez, and used np.load to load the model params. However, I get an error
...
[-0.03124027],
[-0.07023009],
[ 0.03014982]], dtype=float32)}}' with dtype object is not a valid JAX array type. Only arrays of numeric types are supported by JAX.

I am saving params, and state as follows:
# save model
def save_model(path, params, st):
  jnp.savez(path, params=params, st=st)
  print("Parameters saved to ", path)

I am loading params, and state as follows:
# load model
def load_model_params(path):

  with np.load(path, allow_pickle=True) as data:
    params = data["params"]
    st = data["st"]

  return params, st

I assume its cause we are np.savez saves params, and st as objects, and similarly returns as objects. Is there a workaround it? I have looked through this issue. However, I don't understand if I need to implement the function as indicated in the issue discussion. Does using pickle solve this problem? Also, I am trying to initialize the params, and st from previous training iteration as follows:
 # init params and st from trained model if iteration > 0
    if self_play_iter > 0:
        train_logger.info('Loading trained model parameters from iteration: ' + str(self_play_iter - 1))
        path = os.path.join(trained_model_params_path, 'mod_{}.npz'.format(self_play_iter - 1))
        params, st = utils.load_model_params(path)

I believe as long as model is getting updated params, and st, it should be fine?

Hi @bigyankarki , as Trevor mentioned in the issue you referenced, np.save is used to save arrays, but here you are trying to save a tree of arrays.
I would suggest that it would be simplest to use pickle to save and load your parameters:

Ah gotcha, thank you. I was wondering why jax.device_get(params) was used in the code you referenced to? Can't we just save params directly? I see in the documentation that If params is a pytree, then the individual buffers are copied in parallel when passing through jax.device_get. Is it only for performance reasons?

The device_get is mostly for performance (as you note this allows us to copy to host memory in parallel). I think you can avoid it, but personally I think it is better since it makes the data movement more explicit (e.g. jax.device_get: GPU -> host memory, pickle.dump: host memory -> disk).
The device_put is also for performance, this copies the NumPy arrays we load from the pickle file into GPU/TPU memory. I think this is more important, because it is quite easy to accidentally forget to do this and end up constantly copying numpy arrays to GPU memory when calling JAX functions. Again this just makes the data movement explicit (pickle.load: disk -> host memory, jax.device_put: host memory -> GPU memory).

Thank you so much for the explanation. I was essentially able to save and load parameters. I am closing the issue.


News360 is Unstable With MicroG

Install News360 (com.news360.news360app), give it the requested permissions and start it.  Navigate around the app and you will find that many buttons for navigation and features are unresponsive.  The app sticks and lags.  It doesn't seem to crash, but it acts unstable.  It is fine on a "normal" Android environment.
Android Version: 9
OS Version: LineageOS for MicroG 16.0-20200816 (reproduced on cheeseburger and gts210vewifi)
MicroG Services Core Version: <IP_ADDRESS>315
No Google account registered.
Google device registration ON.
App in question is registered with GCM.

Log attached.
News360Log.txt


High memory usage 0.12.2

Bug report
System info: [ version 0.12.2, rhel 7.2]
Steps to reproduce:

start system
wait for system started that's is about 4 minutes.
start pooler.
got

ps wavx | grep influx
 6940 ?        Sl    25:19 109030  5031 120035932 *74729508* 75.6 /usr/bin/influxd -config /etc/influxdb/influxdb.conf
Expected behavior:  memory usage under 20G
Actual behavior: memory usage above 75G
with
go tool pprof /bin/influxd http://localhost:8086/debug/pprof/heap
got result in file
usage.zip
my config is just like default one
config.zip
stats and others
stats.zip
logs.zip
free -m
              total        used        free      shared  buff/cache   available
Mem:          96507       82178       13470          96         858       13564
Swap:         54271       16075       38196

Please help to understand why memory usage so extremely high.

What does free -m show?

It looks like you have about 5M series.  Are you running any queries?  If so, what are they?

no. i just adding new metrics.
after several minutes of running pooler i start got such lines in logs
2016-04-29 21:14:14,939 [discovery] Failed to spool collected metrics to <IP_ADDRESS>:8086: HTTP 599: Failed connect to <IP_ADDRESS>:8086; Connection refused

Leaking connections possibly?  Are the your writes batched?    How many writers?

oh i see. in that moment i have a stacktrace in my influx logs
logs.txt

What is your writer process [discovery]?  If it's written in go and use the v2 client, there was a bug about leaked connections that was recently fixed.

no. Its written in python and i have lots of them.
4 servers with each with 18 process with 187 threads. not every thread works with metrics of cause.
i am unsure about batch size. but of cause it is batched.

discovery process uses libcurl to spool the metrics. Each discovery process (72 at all) spools all collected metrics every 250ms in a single batch.
At this time we collect ~100 metrics from 50k objects every 300 seconds and have the plans to increase amount of objects up to 250k

ok. looks like we found and fixed problem with our discovery process.
i am unsure weather i have to open another issue or not.
but problem looks the same. high memory usage.

but probably the reason is different.
the_log.txt
it looks like while compacting the database influx eats all the memory
then after restart. it begun to compact db again, at the moment influx is still not able to accept metrics. So

restart time is awful
compact db east all the memory.

i think the first problem is in architecture and can't be fixed in soon, but can i handle the second one somehow ?

The restart time is a known issue with some datasets.  Issue to follow is: #6250.  There is lock contention when reloading the in-memory index that slows some datasets down a lot.
For the compactions, are you overwriting points or writing to series in the past?   Can you provide some sample data that you're writing?

Possible duplicate of #6243?

@freeseacher When your heap starts to spike, would you be able to grab a snapshot of the heap and goroutines and attach the output here?
curl -o heap.txt http://localhost:8086/debug/pprof/heap?debug=1
curl -o goroutine.txt http://localhost:8086/debug/pprof/goroutine?debug=1

Not to hijack the issue, but I am also experiencing very high memory consumption. Influx will essentially eat all the RAM on the machine (CentOS 7.1) within ~ 1 minute after start. It also takes a long while to start -- it freezes up completely while loading the database index (some which take almost 3 minutes).
I have attached the heap and goroutine from my system.
goroutine.txt
heap.txt

#6618 should help start up time some.
@freeseacher Are you able to grab a heap and profile using the commands above when you heap starts to spike?

Should be fixed via #6653 and #6743.  If there are still issues, please let us know.


[Enhancement] [Reopen] - Installation via Docker / Docker Compose

Reopen of PR #183 - See for further details

Hi @dylanrhysscott,
Thanks for your work on this! It's really appreciated and awesome to see people contributing to BookStack.
Unfortunately I won't be merging this pull-request and here's why:

I don't want to add install-specific files into the core BookStack repo. This would add a few extra root-level files that don't really need to be in this repo. Ideally I'm trying to keep all dev-ops type of code separated from the BookStack app code.
There's already a pretty solid docker implementation of BookStack on the go.
I won't accept pull requests to the release branch since it's reserved for only versioned releases, No development.

Let me know if I've got the wrong end of the stick and your docker implementation works differently to the one mentioned above or adds to it. Sorry it's not clear that an implementation currently exists. I've been meaning to update the installation docs for a while.

Hi Dan @ssddanbrown,
Thanks for getting back to me - being a big fan of open source I do like to contribute where I can. Really appreciate the feedback - wanted to address the points as we could open a discussion about it:

Fair enough on this point I have added some extra files for the docker build and I could probably abstract this further / clean this up. However with regards to install specific files I'd argue that due to the interoperable and immutable nature of docker containers they aren't quite install specific as in theory the container will run on any platform. I probably should abstract the apache confs for example into the container away from the source repo to keep it clean and not tied to a given web server / DevOps tools.
My approach to dockerising Bookstack appears to deliver the same level of the repo you mentioned. However that one is a lot cleaner and I could add the git clone as part of the build process to slim things down. I'll take a look at this for some inspiration.
I chose the release branch as the install would not complete successfully without a build manifest.json and doing the above with Git would likely solve this issue.

As an extra thought it would be brilliant to have a Docker install baked into your official repo for coherence and giving more options through the official repo. Also by including the Docker stuff directly into your repo and linking this with automated builds it would streamline the update process a lot more and allow easier upgrades with the added bonus of when you push a new version a self contained build is handled for you. I'd love to help make it happen directly in the official repo and would gladly take your advice on how to meet the standard for you to merge it. That is of course if it's something your interested in!
Thanks
Dylan


GetAsync does not work with in-memory database

In version 1.5.231, the GetAsync method throws a SQLiteException: no such table
To reproduce, create a simple model class:
public class MyTable
{
    [PrimaryKey, AutoIncrement]
    public int Id { get; set; }

    public string Column1 { get; set; }
}

...and insert a line into the DB, then try to read it:
var conn = new SQLiteAsyncConnection(":memory:", true);
await conn.CreateTableAsync<MyTable>();
await conn.InsertAsync(new MyTable { Id = 1, Column1 = "a" });
var x = await conn.GetAsync<MyTable>(1);

The last line fails (SQLiteException: no such table: MyTable), but works when passing a DB path on disk instead of ":memory:". Happens for me both in a .NET 4.6 console application and in a .NET Core 2.1 console application.
Am I using everything correctly? Can somebody confirm this behavior?

Same here for me when using FindAsync and in memory db.
Fails:
var customer = await this.database.FindAsync<Customer>(x => x.Name == name).ConfigureAwait(false);
Succeeds:
var customer= await this.database.Table<Customer>().Where(x => x.Name == name).FirstOrDefaultAsync().ConfigureAwait(false);

FYI: Downgrading to v1.4.118 resolved the problem. However, only a temporary solution obviously...

I already use the 1.6.292 version, but the issue exist exist.


support parsing EML into triples

We're still working on mappings in #21 but I have got a work-in-progress version of this going. It's got a number of issues but I think it's a good start. The following command triplifies an entire DataONE Data Package using the latest state of the code in https://github.com/DataONEorg/slinky/tree/feature_update_graph_pattern.
$ slinky get doi:10.5063/F1QR4VCB

@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .

<https://dataone.org/datasets/doi%3A10.5063%2FF1QR4VCB>
    <http://spdx.org/rdf/terms#Checksum> "5ed8a1a35e943bc3cd99180189f07293e3186ca4" ;
    <http://spdx.org/rdf/terms#ChecksumAlgorithm> "SHA1" ;
    a <https://schema.org/Dataset> ;
    <https://schema.org/award> """State of Alaska's Salmon and People (Gordon and Betty Moore Foundation Award 5124)
         Data Task Forces for Better Synthesis Studies (Gordon and Betty Moore Foundation Award 5451)""" ;
    <https://schema.org/byteSize> 12273388 ;
    <https://schema.org/creator> <https://dataone.org/organizations/urn%3Auuid%3Ac436ba14-64fb-4cbc-83a3-1d4349614860> ;
    <https://schema.org/dateModified> "2019-03-19T21:06:38.869000Z" ;
    <https://schema.org/datePublished> "2018", "2019-03-19T21:06:37.466000Z" ;
    <https://schema.org/description> """The Well Log Tracking System (WELTS) contains lithologic information submitted to the Division of Mining,
Land and Water, Alaska Hydrologic Survey by water well contractors as required per Alaska State Statute 41.08.020(b4) authority delegated to the Alaska Hydrologic Survey per Department Order 115, Ârequire of water well contractors, the filing with it of basic water and aquifer data normally obtained, including but not limited to well location, estimated elevation, well driller's logs, pumping tests and flow measurements, and water quality determinations.Â Additionally, per Alaska Administrative Code, Title 11 Natural Resources, Part 6 Lands, Chapter 93 Water Management, Article 2 Appropriation and Use of Water 11 AAC 93.140
(a):For a drilled, driven, jetted, or augered well constructed, the water well contractor or a person who constructs
the well shall file a report within 45 days after completion with both the property owner and the department.
The report must contain the following information as applicable:
(1) the method of construction;
(2) the type of fluids used for drilling;
(3) the location of the well;
(4) an accurate log of the soil and rock formations encountered and the depths at which the formations occur;
(5) the depth of the casing;
(6) the height of the casing above ground;
(7) the depth and type of grouting;
(8) the depth of any screens;
(9) the casing diameter;
(10) the casing material;
(11) the depth of perforation or opening in the casing;
(12) the well development method;
(13) the total depth of the well;
(14) the depth of the static water level;
(15) the anticipated use of the well;
(16) the maximum well yield;
(17) the results of any well yield, aquifer, or drawdown test that was conducted;
(18) if the water well contractor or person who constructs the well installs a pump at the time of construction,
the depth of the pump intake and the rated pump capacity at that depth.

(b) When the drill rig is removed from the well site, the well must be sealed with a sanitary seal and a readily accessible means provided to allow for monitoring of the static water level in the well.

(c) A hand-dug well that is permanently decommissioned shall be filled by the land owner to a point 12 inches above the existing ground level with well-compacted impermeable material.

(d) A well, other than a hand-dug well, that is permanently decommissioned by the owner of the well must comply with the requirements of 18 AAC 80.015(e) .

(e) If the department believes that an encounter of oil, gas, or other hazardous substance is likely to result from well drilling, the department will notify the Alaska Oil and Gas Conservation Commission, and the provisions of AS 31.05.030 (g) may apply.

(f) The department will notify the Department of Environmental Conservation of any permanently abandoned well that may contaminate water of the state under the provisions of 18 AAC 80.

(g) Information required by (a) of this section is required for any water well that has been deepened, modified, or abandoned, and for any water supply well or water well that is used for monitoring, observation, or aquifer testing, including a dry or low-yield water well that is not used.

This shape  file characterizes the geographic representation of well logs within the State of Alaska contained in the Well Log Tracking System.
The shape file was developed using well location information submitted with well logs.

Well locations represented by a gold star symbol, represent the approximate (centroid) location, and may represent a cluster of wells.

Well locations represented by a blue circle symbol, represent wells submitted with latitude and longitude coordinates.

Each feature has an associated attribute record, including a  Well Log Tracking System identification number which serves as an index to case-file information. Those requiring more information regarding WELTS should contact the Alaska Department of Natural Resources Alaska Hydrologic Survey directly.""" ;
    <https://schema.org/identifier> [
        a <https://schema.org/PropertyValue> ;
        <https://schema.org/propertyID> "https://registry.identifiers.org/registry/doi" ;
        <https://schema.org/url> "https://doi.org/doi%3A10.5063%2FF1QR4VCB" ;
        <https://schema.org/value> "10.5063/F1QR4VCB"
    ] ;
    <https://schema.org/isAccessibleForFree> "true" ;
    <https://schema.org/keyword> "land use" ;
    <https://schema.org/name> "Locations of Wells in Alaska using the Well Log Tracking System, 2016" ;
    <https://schema.org/sameAs> "https://doi.org/10.5063%2FF1QR4VCB" ;
    <https://schema.org/schemaVersion> "eml://ecoinformatics.org/eml-2.1.1" ;
    <https://schema.org/spatialCoverage> [
        a <https://schema.org/Place> ;
        <https://schema.org/additionalProperty> [
            a <https://schema.org/PropertyValue> ;
            <https://schema.org/name> "Spatial Reference System" ;
            <https://schema.org/propertyID> <http://www.wikidata.org/entity/Q4018860> ;
            <https://schema.org/value> "http://www.opengis.net/def/crs/OGC/1.3/CRS84"
        ], [
            a <https://schema.org/PropertyValue> ;
            <https://schema.org/name> "Well-Known Text (WKT) representation of geometry" ;
            <https://schema.org/propertyID> <http://www.wikidata.org/entity/Q4018860> ;
            <https://schema.org/value> "POLYGON ((170.375 73.875, -125.5 73.875, -125.5 47.375, 170.375 47.375, 170.375 73.875))"
        ] ;
        <https://schema.org/description> "Alaska" ;
        <https://schema.org/geo> [
            a <https://schema.org/GeoShape> ;
            <https://schema.org/box> "73.875,-125.5 47.375,170.375"
        ]
    ] ;
    <https://schema.org/temporalCoverage> "2017-02-15" ;
    <https://schema.org/url> "https://dataone.org/datasets/doi%3A10.5063%2FF1QR4VCB" ;
    <https://schema.org/variableMeasured> "BEDROCK_DEPTH", "BLOCK", "CASING_DEPTH", "CASING_DIA", "CASING_NOTE", "CASING_STICKUP", "CASING_THICK", "CASING_TYPE", "CITY", "COMPANY_NAME", "DATE_COMPLETE", "DATE_START", "DEV_DURATION", "DEV_METHOD", "DISINFECT", "DISINF_METHOD", "DOE", "DRILLERS_COMMENTS", "DRILL_METHOD", "FULL_NAME", "GRAVEL", "GRAVEL_START", "GRAVEL_STOP", "GROUT_FROM", "GROUT_TO", "GROUT_VOL", "HOLE_DEPTH", "INTAKE_TYPE", "LAT", "LINER_DIA", "LINER_TYPE", "LL_SOURCE", "LOCATION_NOTE", "LOG_ID", "LON", "LOT", "Log_ID", "MAPNUM", "MERID", "MODDATE", "MODUSER", "OWNER", "PDESC", "PERF1_START", "PERF1_STOP", "PERF2_START", "PERF2_STOP", "PUMP_FT", "PUMP_GPM", "PUMP_HP", "PUMP_HR", "PUMP_INTAKE_FT", "QTR_SEC", "RECOV_RATE", "REGION", "SCREEN_NOTE", "SCREEN_SIZE", "SCREEN_START", "SCREEN_STOP", "SCREEN_TYPE", "SECTION", "STATIC_WATER_FROM", "STATIC_WATER_LEVEL", "STATUS", "SUBDIVISION", "SW_DATE", "TEST_METHOD", "TRACT", "TWNSHP", "WELL_USE" ;
    <https://schema.org/wasRevisionOf> "https://dataone.org/datasets/doi%3A10.5063%2FF1CJ8BQZ" .

<https://dataone.org/datasets/urn%3Auuid%3A2e4adb4b-2e57-476a-aba7-db1c72723375>
    <http://spdx.org/rdf/terms#Checksum> "afc17730924910ee1653e0889f54130658dbe9c3" ;
    <http://spdx.org/rdf/terms#ChecksumAlgorithm> "SHA-1" ;
    a <https://schema.org/DataDownload> ;
    <https://schema.org/byteSize> 11166729 ;
    <https://schema.org/contentUrl> "https://search.dataone.org/cn/v2/resolve/urn%3Auuid%3A2e4adb4b-2e57-476a-aba7-db1c72723375" ;
    <https://schema.org/dateModified> "2018-07-25T00:32:56.245000Z" ;
    <https://schema.org/datePublished> "2017-03-03T22:32:04.602000Z" ;
    <https://schema.org/encodingFormat> "text/csv" ;
    <https://schema.org/identifier> "https://dataone.org/datasets/urn%3Auuid%3A2e4adb4b-2e57-476a-aba7-db1c72723375" ;
    <https://schema.org/name> "WELTS_flatfile.csv" .

<https://dataone.org/datasets/urn%3Auuid%3A83bf45de-1db2-43cb-9ac4-2ed2e564312f>
    <http://spdx.org/rdf/terms#Checksum> "91de80c44927c196e862c803aa86e221433a45a8" ;
    <http://spdx.org/rdf/terms#ChecksumAlgorithm> "SHA-1" ;
    a <https://schema.org/DataDownload> ;
    <https://schema.org/byteSize> 963049 ;
    <https://schema.org/contentUrl> "https://search.dataone.org/cn/v2/resolve/urn%3Auuid%3A83bf45de-1db2-43cb-9ac4-2ed2e564312f" ;
    <https://schema.org/dateModified> "2018-07-25T00:33:00.360000Z" ;
    <https://schema.org/datePublished> "2017-03-03T22:32:08.792000Z" ;
    <https://schema.org/encodingFormat> "application/zip" ;
    <https://schema.org/identifier> "https://dataone.org/datasets/urn%3Auuid%3A83bf45de-1db2-43cb-9ac4-2ed2e564312f" ;
    <https://schema.org/name> "WELTS.zip" .

<https://dataone.org/organizations/urn%3Auuid%3Ac436ba14-64fb-4cbc-83a3-1d4349614860>
    a <https://schema.org/Organization> ;
    <https://schema.org/name> "Alaska Department of Natural Resources, Support Services Division, Information Resource Management" .

I added an alignment graphic for OBOE/SSN-EXT/schema.org in order to facilitate thinking about how we do this mapping to schema.org:


Docker build fails with update to 2.2.0

Our docker builds now fail with the update to 2.2.0.  The GitHub Action log is at https://github.com/sillsdev/TheCombine/actions/runs/4234817715
Notice in particular the build for the maintenance component (it was the first failure and canceled the others).  The logs state:
The command '/bin/sh -c apt-get update &&   apt-get install -y python3 python3-pip nano &&   apt-get autoremove &&   apt-get clean &&   rm -rf /var/lib/apt/lists/*' returned a non-zero code: 100
Error: Process completed with exit code 100.

I believe this is due to what was logged in the Post Harden Runner section:
Error: StepSecurity Harden Runner: Traffic to IP Address <IP_ADDRESS> was blocked
Error: StepSecurity Harden Runner: Traffic to IP Address <IP_ADDRESS> was blocked

However, the endpoints were set to match what was recommended (this is a super-set to cover all 4 builds):
          allowed-endpoints: >
            ${{ secrets.AWS_ACCOUNT }}.dkr.ecr.${{ secrets.AWS_DEFAULT_REGION }}.amazonaws.com
            api.ecr.${{ secrets.AWS_DEFAULT_REGION }}.amazonaws.com:443
            sts.${{ secrets.AWS_DEFAULT_REGION }}.amazonaws.com:443
            api.github.com:443
            api.nuget.org:443
            archive.ubuntu.com:443
            auth.docker.io:443
            codecov.io:443
            dc.services.visualstudio.com:443
            deb.debian.org:443
            docker.io:443
            dotnetcli.azureedge.net:443
            files.pythonhosted.org:443
            github.com:443
            pipelines.actions.githubusercontent.com:443
            production.cloudflare.docker.com:443
            pypi.org:443
            registry.npmjs.org:443
            registry-1.docker.io:443
            security.debian.org:443
            security.ubuntu.com:443
            storage.googleapis.com:443
            uploader.codecov.io:443

Note that according to a previous build that was successful:
Wed, 22 Feb 2023 14:21:07 GMT:domain resolved: archive.ubuntu.com., ip address: <IP_ADDRESS>, TTL: 30
Wed, 22 Feb 2023 14:21:07 GMT:domain resolved: security.ubuntu.com., ip address: <IP_ADDRESS>, TTL: 30

It appears that traffic is being blocked to allowed endpoints.

Hi @jmgrady I believe this is because the calls are being made to port 80, but the allowed endpoints only mention port 443.
If you see the insights link, it has these details (screenshot)

Can you please add these two allowed endpoints?
archive.ubuntu.com:80
security.ubuntu.com:80

That fixes the problem.  Thank you for your help.


python3Packages.pyads: 3.2.2 -> 3.3.7

Motivation for this change
Update to latest upstream release 3.3.7
Change log: https://github.com/stlehmann/pyads/releases/tag/3.3.7
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 125932 at e7dfc3b4 run on aarch64-linux 1

2 packages built successfully:

python38Packages.pyads
python39Packages.pyads

This package is another case where the tests pass on macos as long as they're not run at the same time as another instance, exposing the weakness of sandboxing there. If e.g. the 3.8 and 3.9 packages are built in parallel they compete for the same port number and fail with:
>       self.server.bind((self.ip_address, self.port))
E       OSError: [Errno 48] Address already in use

One solution might be to fix it to choose a random port number in the tests.

Result of nixpkgs-review pr 125932 run on x86_64-linux 1

2 packages built:

python38Packages.pyads
python39Packages.pyads

Result of nixpkgs-review pr 125932 run on x86_64-linux 1

2 packages built:

python38Packages.pyads
python39Packages.pyads

Going to ignore the darwin parallel failure for now because it would probably require bigger code changes.


Add custom token extractor

This enables uses cases like checking whether a user is authenticated using a session cookie.

Codecov Report

Merging #7 (4f274e0) into master (5ca55d8) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master        #7   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            5         5
  Lines          166       184   +18
=========================================
+ Hits           166       184   +18

Impacted Files
Coverage Δ

authorization.go
100.00% <ø> (ø)

client.go
100.00% <ø> (ø)

clientprovider.go
100.00% <100.00%> (ø)

gate.go
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Add @JsonProperty for field layout getter/setter

Problem:
Dropwizard allows customized object mapper. If the customization happens to disable AUTO_DETECT_SETTERS (https://fasterxml.github.io/jackson-databind/javadoc/2.7/com/fasterxml/jackson/databind/MapperFeature.html#AUTO_DETECT_SETTERS), it will only consider methods explicitly annotated as setters. Thus layout field cannot be recognized.
Also, it is not consistent with other properties in the same file. The other setters/getters are all annotated.
Solution:
Add @JsonProperty annotation for layout property getter and setter
Result:

@egginbag Thanks for your contribution!
The layout field is not supposed to be settable via the configuration file.
The implementations of DiscoverableLayoutFactory are not serializable/deserializable.


Verify ocs and spoke sync

verify in ocs step
verify for registry sync into spokes: verify, verify_ocp_sync and verify_olm_sync

LGTM

:tada: This PR is included in version 0.0.5 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


I am not able to add og:image tag for facebook share functionality.

I have checked the https://blog.kissmetrics.com/open-graph-meta-tags/ url but it will suggest we are not able to add og:image into cms application. Is it right?
So please suggest how can I able to add og:image dynamically into this CMS application.

Closing out old issues. Note: this repository is for a demo application using the KeystoneJS Framework.
For questions about using Keystone, I suggest asking on Stack Overflow with the keystonejs tag.
For general discussion or feedback, you can also join the KeystoneJS Slack.
Regards,
Stennie


enableSeparateBuildPerCPUArchitecture:true after this build failed please check below error

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:packageRelease'.

2 exceptions were raised by workers:
java.lang.RuntimeException: java.lang.RuntimeException: java.io.IOException: Failed to create 'C:\Users\rahu4\OneDrive\Documents\TheFoodiee\react-native-easy-starter-master\react-native-easy-starter-master\android\app\build\outputs\apk\release..........\release\easy-boiler-1.0.8.apk'
java.lang.RuntimeException: java.lang.RuntimeException: java.io.IOException: Failed to create 'C:\Users\rahu4\OneDrive\Documents\TheFoodiee\react-native-easy-starter-master\react-native-easy-starter-master\android\app\build\outputs\apk\release..........\release\easy-boiler-1.0.8.apk'

You can use app bundle.
using this npm script

worked bro thanks


S2 bootstrapping times out when PIN entry takes "too long"

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?
NO, my problem is NOT within Home Assistant or the ZWave JS integration
Is your problem within ZWaveJS2MQTT?
NO, my problem is NOT within ZWaveJS2MQTT
Checklist

[X] I have checked the troubleshooting section and my problem is not described there.

[X] I have read the changelog and my problem was not mentioned there.

Describe the bug
When including with S2, if the PIN is not entered within a ~10 second time interval, the S2 bootstrapping will fail after a long timeout. Anecdotally, reports from HA users and elsewhere seem to indicate that this failure is common across a variety of devices. The solution is usually "enter the PIN as fast as possible". I think the same problem occurs if you take to long to select the security classes, but I didn't investigate that one much.
Out of curiosity, I repeated the inclusion with the same device using the Silicon Labs PC-Controller software and had quite a different experience. Even after waiting 2 minutes to input the PIN, it successfully includes the device with S2. I've repeated this successfully multiple times waiting 1+ minutes.
Steps to reproduce the behavior:

Include a device with Default inclusion strategy
Select the default security class grant
Wait for PIN prompt
After PIN prompt is shown for 1 or more minutes, enter the correct pin
Watch as zwave-js times out and fails the bootstrapping

Repeat the above with PC Controller, and it succeeds.
Device information
I used this device for my testing, but it seems to be a problem for many devices and many users.
Manufacturer: HomeSeer Technologies
Model name: HS-FC200+
How are you using node-zwave-js?

[X] zwavejs2mqtt Docker image (latest)
[ ] zwavejs2mqtt Docker image (dev)
[ ] zwavejs2mqtt Docker manually built (please specify branches)
[ ] ioBroker.zwave2 adapter (please specify version)
[ ] HomeAssistant zwave_js integration  (please specify version)
[ ] pkg
[ ] node-red-contrib-zwave-js (please specify version, double click node to find out)
[ ] Manually built from GitHub (please specify branch)
[ ] Other (please describe)

Which branches or versions?
version:
node-zwave-js branch: 8.6.1
zwavejs2mqtt branch: 5.10.1
Did you change anything?
no
If yes, what did you change?
No response
Did this work before?
No, it never worked anywhere
If yes, where did it work?
No response
Attach Driver Logfile
Attached are zniffer traces for the inclusion process. I'll email the S2 keys.
For PC Controller, included is a zniffer trace and the pc-controller trace file.
For Z-Wave JS, a zniffer trace and driver debug logs.
trace.zip
One thing I noticed in the pc controller trace is that after the PIN is prompted, it seems to periodically "ping" the node every ~10 seconds with an S2 encapsulated message. Z-Wave JS does not do this, it's just silent until the bootstrapping times out and fails.

I sent the keys via email, however none of them let me decrypt these messages. I assume these are using the temporary key.

Despite my total luck of understanding of this topic, at the risk of looking silly I'm going to suggest that zwave-js is not properly replying to the Public Key Report from the node. In the PC Controller trace, the controller sends the Report milliseconds after receiving the report from the node. In Z-Wave JS, the report is not sent until the PIN is entered. The anecdotally observed ~8-12 seconds time allowance seems to follow a 10-second timeout specification.

According to the diagram, timeout TB3 starts after the node sends its public key report.

Meanwhile, in zwave-js, no Report until 1 minute later, about the time I entered the PIN. I'm assuming that since the node doesn't get the report within 8-12 seconds, it cancels its bootstrapping.

I believe you have just solved the mystery of failed S2 inclusion.


[TEVA-3299] Include line breaks in personal statement when displaying it

Jira ticket URL
https://dfedigital.atlassian.net/browse/TEVA-3299
Changes in this PR:
Include line breaks in personal statement when displaying it. Currently this file is the only place where we display the personal statement; if we did it across multiple files I might make a job application presenter.
Screenshots of UI changes:
Input

Before

After

Has approval from UX now


Ignoring specified requests to fix auto sync issues for using server sent events

PROBLEM:
I am using rn-eventsource for using server side events on the react-native.  My tests timeouts because "Detox monitors in-flight requests over the network" But server send events request never ends
SUGGESTED SOLUTION:
An option can be defined to ignore some url patterns in detox.config.js
Example:
ignoreNetworkRequestsPattern: /connections/sse-callbacks/*/**

https://github.com/wix/Detox/blob/master/docs/APIRef.DeviceObjectAPI.md#11-detoxurlblacklistregexinitialize-the-url-blacklist-at-app-launch
?

https://github.com/wix/Detox/blob/master/docs/APIRef.DeviceObjectAPI.md#11-detoxurlblacklistregexinitialize-the-url-blacklist-at-app-launch
?

Thanks @LeoNatan

Thanks @LeoNatan

👍
Cheers

👍
Cheers


1.days - 1.hours results in (-1.days, -1.hours) components

We are using SwiftDate to do offset certain dates. Recently I got a strange problem that this code:
(1.days - 1.hours).fromNow() does not equal to 23.hours.fromNow(). I looked into it more and the problem is that (1.days - 1.hours) returns NSDateComponents with Day: -1 and Hour: -1, instead of Day: 1 and Hour: -1. So I dug into the SwiftDate code a probably found the root cause.
In file DateInRegion on line 872, there is this code:
let finalValue =  ((leftValue + rightValue) * (sum == true ? 1 : -1))
Instead it should be this:
let finalValue =  leftValue + (rightValue * (sum == true ? 1 : -1))

Good find! I will include this in the current develop branch.
Thx!

Although... In the development branch there is no sum function... :-)=)
I will include this particular circumstance in the unit tests and investigate.

Damn, I didn't check the development branch, sorry :/

But it is still there. Just in a different file: https://github.com/malcommac/SwiftDate/blob/develop/SwiftDate/NSDateComponents%2BSwiftDate.swift#L143

I looked in the wrong place. Working on it!

Awesome, thanks!

Fixed this one and included test code (see commit above). Can you confirm that this works @TadeasKriz?

Yes I will test it and let you know.

Seems to work properly now, thanks!


cmake remove PX4 special handling

This can be built with standard cmake. https://github.com/PX4/Firmware/pull/13810

Looks good! Sorry I didn't see this earlier, haven't been checking this project regularly since joining ModalAI.


Edit direction

Hi, Thanks for your great work!
Here I get one question, when you fine-tune the parameters of the pre-trained StyleGAN model and use InterFaceGAN methods to edit the image, do we need to find a new semantic direction based on the current parameter model? Intuitively, changing the model parameters will change the semantic direction found by InterFaceGAN.
In general, after you fine-tune the pre-trained StyleGAN model, do you retrain the semantic direction found by InterFaceGAN?
Thanks

Hi
No need to find new semantic directions. All the editing methods such as InterfaceGAN, GANSpace, StyleCLIP and more are working the same.
The editing directions that I have uploaded were trained on the pretrained StyleGAN, without PTI.
The key idea is that the fine-tuning happens on the already similar image to the input image.
As it turns out, this enables the fine-tuning to make small changes in its weights. Thus altering only appearance-related weights.
Furtheremore, the regularizaion forces the weight change to happen only in local region not affecting other identities.
To summarize, PTI is orthogonal to any editing method. If an editing method works on the pretrained StyleGAN, it will work on the personalized StyleGAN after PTI.

Got it.
Thanks!


run wl-copy even if wtype is missing

These two commands are two different ways of getting the output and we want to always try both.

We are already running both commands.

We're not, actually:
set -e
echo "one"
false
echo "two"

will print one but will never print two since the -e makes it stop at the first failure (triggered by false returning 1 here).
More specifically, for us here:
set -euo pipefail

EMOJI="$(sed '1,/^### DATA ###$/d' $0 | wofi -p "emoji" --show dmenu -i | cut -d ' ' -f 1 | tr -d '\n')"
wtype "$EMOJI"; wl-copy "$EMOJI"
exit

if wtype fails (for instance because it doesn't exist), wl-copy will never be executed.
We need || true instead of a simple ;/newline to ignore errors with one command and continue trying the next :)

@Zeioth did you get a chance to read my explanation above?

@1ace sorry for the slow response. I've reviewed it again and you are absolutely correct. Thank you for providing the explanation.

No wait. It WAS working as expected. If the first command fails, we don't want to silence errors.
We want the user to get the error wtype do not exist so he knows what's going on.
Even then, this is kinda meaningless because the AUR package already satisfy the dependencies, and it should never fail unless the user manually uninstall them (in which case, yes we want to show a error).
A pipe ; will

Run both commands, assumming both are present on the system.
If one of the two commands is not present, it will show a error message.

That is what set -euo pipefail is for.

Ok the confusion seemed to be in the README description not being true anymore. changed in https://github.com/Zeioth/wofi-emoji/commit/e5148d334e6fc09b89c99b1065a233d3e64b0d2b


Explore: better ways to distribute new blocks

Current situation:
When a new block is added, this procedure is followed:

every connected peer will receive the block directly from the node publishing it

Problems with this:

it doesn't scale well
if a node is not connected directly to the build node, e.g. connected to another (build)node, it won't receive the new block (see diagram below)
it might flood the network too much, why do all nodes need to be up-to-date all the time?
if a node is offline/unreachable during a publication, it will miss out.

Proposed solution:

Explore better ways to broadcast new blocks
Maybe only build nodes should receive all the blocks immediately, regular nodes could simply work trigger based
this trigger could be something periodic and/or when a user interacts with the node e.g. when pulling an artifact or when inspecting the log

One recommendation from the libp2p team was implementing the ping protocol. Which is more of a heartbeat in libp2p. From here,
"The ping protocol is a simple liveness check that peers can use to quickly see if another peer is online."

Sorry, for this ticket, I meant graphsync should be investigated.

Moving this to 0.2.2 since this is not going to be releasable in 2 weeks.

It was discussed and decided to do this in several iterations:

one authorized node - many regular nodes: Replace the current block broadcast in the Blockchain Service with gossipsub
one authorized node - many regular nodes: Keep blocks/logs up-to-date even if node missed out on new block messages
a few authorized nodes - many regular nodes: Make sure this mechanism also works when there are multiple authorized nodes (simple consensus)
Multiple authorized/multiple regular nodes: Add real consensus mechanism

Is this exploration done now? @efrisch


Project files leak user identity / developer system information

Describe the bug
It may be hazardous for individuals to share Ghidra project files due to their containing usernames and whole paths.
To Reproduce
Examine the project.prp file and see the OWNER property contains the creating user's username.
Examine the projectState file and potentially see one or more LOCATION_x properties containing whole pathnames that may include e.g. the user's home directory path (revealing their username), parent directory paths that may leak e.g. organisational affiliation or other information outside the scope of the project.
Expected behavior
Project files should only contain information pertinent to the project.
Environment (please complete the following information):

OS: macOS 14.5
Java Version: 21.0.2
Ghidra Version: 11.0.3
Ghidra Origin: via Homebrew

The project files you mentioned are not intended to be shared.  Since the local project is tied to the project creator it is unclear why you would share them.  Project archive and ghidra file archives (*.gzf) are the preferred sharing mechanism separate from a shared online repository.


[ci] Re-enable Daint for running production tests

Codecov Report

Merging #1042 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1042   +/-   ##
=======================================
  Coverage   91.97%   91.97%
=======================================
  Files          81       81
  Lines       10937    10937
=======================================
  Hits        10059    10059
  Misses        878      878

Continue to review full report at Codecov.

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


ENH: where for Panel

example of impl. I think this is pretty straightforward; what is hard is align (well not that hard but needs to accept a lot of different cases)
http://stackoverflow.com/questions/14650341/boolean-mask-in-pandas-panel

closed by #3482.


SFDX creating huge log files

Summary
SFDX seem to be logging excessively
Steps To Reproduce:

Start working on VS Code.
Deploy anything into an org

Expected result
Log files should be handled properly.
  If not the CLI, do you get the sam behavior without vscode involved?

Neither,... I deleted the files, killed VS Code and stopped working on this laptop yesterday, right after posting the screenshot.
Now (almost 24 hours later), I see this node job still running  AND keeping 140 GB in logs.

If you or someone you know is experiencing logger problems, SF_DISABLE_LOG_FILE might be right for you.

Having the same issue. Only been using SFDX wth VSC for < 1 week and my log file already ballooned to 33GB. Was wondering why I was randomly running out of storage space...

Does anyone see this happen without vscode being involved?

vscode is def in involved in my case.  After hearing about this issue yesterday I started paying attention and am seeing the issue currently.
My log file when from around 20Gb around 16 hours ago to 91Gb now ~/github/PDT/salesforcedx-vscode (gbockus/revert-node-bump-2) » du -h ~/.sf/| sort -h                                                                                130 ↵ gbockus@gbockus-ltm  91G	/Users/gbockus/.sf/
Same odd error message in the log file
{"name":"sf","hostname":"*****.salesforce.com","pid":97200,"level":60,"errno":-32,"code":"EPIPE","syscall":"write","msg":"","time":"2023-02-21T15:29:32.900Z","v":0}

Tracking the pid of the process down I see the following:
~/github/PDT/salesforcedx-vscode (gbockus/revert-node-bump-2) » ps -ef | grep 97200                                                                                gbockus@gbockus-ltm
  502 17156  1204   0  9:30AM ttys000    0:00.01 grep --color=auto --exclude-dir=.bzr --exclude-dir=CVS --exclude-dir=.git --exclude-dir=.hg --exclude-dir=.svn --exclude-dir=.idea --exclude-dir=.tox 97200
  502 97200 97159   0  3:50PM ttys003  953:10.19 /Users/gbockus/.local/share/sfdx/client/7.185.0-9390167/bin/node /Users/gbockus/.local/share/sfdx/client/7.185.0-9390167/bin/run force --help
ansible|----

pstree
-+- 97083 gbockus bash /usr/local/bin/sfdx force --help
 \-+- 97137 gbockus bash /Users/gbockus/.local/share/sfdx/client/bin/sfdx force --help
   \-+- 97159 gbockus bash /Users/gbockus/.local/share/sfdx/client/bin/../7.185.0-9390167/bin/sfdx force --help
     \--- 97200 gbockus /Users/gbockus/.local/share/sfdx/client/7.185.0-9390167/bin/node /Users/gbockus/.local/share/sfdx/client/7.185.0-9390167/bin/run force --help
ansible|------------------------------------------------------------

I can run sfdx force --help from the command line and it completes without issue.

I went from 8 GB 14 hs ago to 73 GB now:  73G	/Users/cristina.canizales/.sf/
502 60489     1   0  8Feb23 ??         0:00.22 /Users/cristina.canizales/.local/share/sfdx/client/7.185.0-9390167/bin/node /Users/cristina.canizales/.local/share/sfdx/client/7.185.0-9390167/node_modules/@salesforce/plugin-telemetry/processes/upload /Users/cristina.canizales/Library/Caches/sfdx /var/folders/yw/x__kzfd10lnbykhglftch4xw0000gp/T/sfdx-telemetry/telemetry-7906fcbef2237b802770b9c8f056ee6ade7504b3.log   502 95230     1   0 10Feb23 ??         0:00.02 bash /usr/local/bin/sfdx force:data:record:delete --sobjecttype TraceFlag --sobjectid 7tf8B0000005nnUQAQ --usetoolingapi   502 95241 95230   0 10Feb23 ??         0:00.02 bash /Users/cristina.canizales/.local/share/sfdx/client/bin/sfdx force:data:record:delete --sobjecttype TraceFlag --sobjectid 7tf8B0000005nnUQAQ --usetoolingapi   502 95246 95241   0 10Feb23 ??         0:00.02 bash /Users/cristina.canizales/.local/share/sfdx/client/bin/../7.185.0-9390167/bin/sfdx force:data:record:delete --sobjecttype TraceFlag --sobjectid 7tf8B0000005nnUQAQ --usetoolingapi   502 95254 95246   0 10Feb23 ??       14864:37.44 /Users/cristina.canizales/.local/share/sfdx/client/7.185.0-9390167/bin/node /Users/cristina.canizales/.local/share/sfdx/client/7.185.0-9390167/bin/run force:data:record:delete --sobjecttype TraceFlag --sobjectid 7tf8B0000005nnUQAQ --usetoolingapi   502 92595 85457   0 12:36PM ttys007    0:00.01 grep --color=auto --exclude-dir=.bzr --exclude-dir=CVS --exclude-dir=.git --exclude-dir=.hg --exclude-dir=.svn --exclude-dir=.idea --exclude-dir=.tox sfdx
and I get the same message:
{"name":"sf","hostname":"cristin-ltm6uv7.internal.salesforce.com","pid":95254,"level":60,"errno":-32,"code":"EPIPE","syscall":"write","msg":"","time":"2023-02-21T15:44:00.780Z","v":0}

If you or someone you know is experiencing logger problems, SF_DISABLE_LOG_FILE might be right for you.

This workaround did the trick. More information here: https://github.com/forcedotcom/sfdx-core/pull/637

I am seeing this on my machine. Will be digging into this now that we finally have a CLI team member seeing it.


Detect part delivery issues

Currently, redcall sends SMS and do not check their delivery status. But sometimes, some parts of the message is not delivered and thus, SMS is never received by its recipient.
Here is an example from Nexmo :

2 of the 3 parts of the message have been successfully delivered, but not the last one. As a consequence, the person wasn't aware of the event.
In those cases, we should retry (only once) to send the message again (or only the message part if that's possible, check on the Nexmo API).
Use the delivery status webhook in order to follow up after sending messages.

will be done in #147


fixfix array funcs which ret can be nullable

What problem does this PR solve?

Issue Number: close #xxx

Related PR: #xxx
Problem Summary:
before this pr, we has some array funcs which ret sign is nullable(uint8) , if we got null , we just fill with nullmap but without filling with true/false ret data, then we my has wrong answer like:

mysql> SELECT pk, array_contains(col_array_string__undef_signed, col_varchar_1024__undef_signed_index_inverted_p_e) or col_boolean_undef_signed  FROM table_30_un_pa_ke_pr_di3 where  pk = 150;
+------+---------------------------------------------------------------------------------------------------------------------------------+
| pk   | (array_contains(col_array_string__undef_signed, col_varchar_1024__undef_signed_index_inverted_p_e) OR col_boolean_undef_signed) |
+------+---------------------------------------------------------------------------------------------------------------------------------+
|  150 |                                                                                -65 |
+------+---------------------------------------------------------------------------------------------------------------------------------+

Check List (For Committer)

Test

[x] Regression test
[ ] Unit Test
[ ] Manual test (add detailed scripts or steps below)
[ ] No need to test or manual test. Explain why:

[ ] This is a refactor/code format and no logic has been changed.
[ ] Previous test can cover this change.
[ ] No colde files have been changed.
[ ] Other reason

Behavior changed:

[x] No.
[ ] Yes.

Does this need documentation?

[x] No.
[ ] Yes.

Release note

None

Check List (For Reviewer who merge this PR)

[ ] Confirm the release note
[ ] Confirm test cases
[ ] Confirm document
[ ] Add branch pick label

run buildall

run buildall


drivers: voltage_divider_scale_dt does not handle negative voltages

Describe the bug
In the file: include/zephyr/drivers/adc/voltage_divider.h
voltage_divider_scale_dt() fails when the measured voltage is negative, because of the uint32_t types of the full_ohms and output_ohms. Instead of outputting a negative number, the output is a large positive number.
To Reproduce
In tests/drivers/adc/adc_rescale/scr/main.c
Add a negative value for the input_mv, such as -1
This was discovered while grounding a Nordic nrf52840 ADC pin and seeing occasional max voltage values pop up instead of the expected near zero readings.
Expected behavior
Voltage is kept negative
Impact
None, it's easy to copy the conversion and typecast to int32_t to keep the sign
Logs and console output
N/A
Environment (please complete the following information):
Commit SHA or Version used:  a6eef0b
Additional context
N/A

@goodsireric thanks for the report! Maybe you'd be interested in submitting a pull request? :)

Yes, I will do that!


Consider Device / Container Size

We may want to consider using the @api flexipageRegionWidth and SLDS Layout concept to make the component responsive to its container / device size.
See Resources:

https://developer.salesforce.com/docs/component-library/documentation/en/lwc/use_width_aware
https://developer.salesforce.com/docs/component-library/bundle/lightning-layout-item/example
https://developer.salesforce.com/docs/component-library/bundle/lightning-layout/example
https://www.lightningdesignsystem.com/utilities/layout/
https://www.lightningdesignsystem.com/utilities/sizing/

Yes, this will be great. It may be an option on the component to have it display as a Card (with heading / Icon) or a Layout (plain). This fits in with #27 and #73.

See work done in PR #172 as a starting point for this one.


Fix 1755

Thank you for helping make the Dapr documentation better!
Please follow this checklist before submitting:

[X] Read the contribution guide
[X] Commands include options for Linux, MacOS, and Windows within codetabs
[X] New file and folder names are globally unique
[X] Page references use shortcodes instead of markdown or URL links
[ ] N/A Images use HTML style and have alternative text
[X] Places where multiple code/command options are given have codetabs

Description
This PR addresses #1755.
As of writing, this is still a WIP:

[X] Create a page that explains how to authenticate with Azure AD
[X] Update the Azure Key Vault page
[X] Deprecate the old Azure Key Vault w/ MSI page
[ ] Update the page for Azure Storage as state store

Issue reference
#1755

@orizohar @berndverst  Here's the first work on the docs as discussed in #1755
It's my first contribution to the Dapr docs and it's a fairly large one, so even before I write the docs for the last component, your help as reviewers would be highly appreciated, to ensure that I've followed the right style.
Some of these things aren't super easy to explain, including all of the Azure AD parts... I've tried to clean up the AKV docs which were mixing concepts related to AKV and some related to AAD.
The result is less like a straightforward "do 1, 2, 3 and you're done", but it offers better security (using az ad sp create-for-rbac as was recommended before creates a SP that has access to manage EVERY resource in the Azure subscription - and that's even useless for Dapr since we need data plane access) and more flexibility because the same SP can be used for multiple Azure components.
Also, cc @cmatskas to keep me accountable and make sure I've documented AAD topics correctly

@orizohar @berndverst Here's the first work on the docs as discussed in #1755
It's my first contribution to the Dapr docs and it's a fairly large one, so even before I write the docs for the last component, your help as reviewers would be highly appreciated, to ensure that I've followed the right style.
Some of these things aren't super easy to explain, including all of the Azure AD parts... I've tried to clean up the AKV docs which were mixing concepts related to AKV and some related to AAD.
The result is less like a straightforward "do 1, 2, 3 and you're done", but it offers better security (using az ad sp create-for-rbac as was recommended before creates a SP that has access to manage EVERY resource in the Azure subscription - and that's even useless for Dapr since we need data plane access) and more flexibility because the same SP can be used for multiple Azure components.
Also, cc @cmatskas to keep me accountable and make sure I've documented AAD topics correctly

Thanks for working on this. If you haven't yet you can see the docs contribution guidelines here. Also, where it makes sense it is okay to not go too deep with explaining Azure and just linking to Azure docs

I've updated the Azure Blob Storage doc too. PR is complete and ready for your review.


proposal: x/image/webp: add animation support to the decoder

I did search for this, as I expected someone to have raised this issue before.
I tried to decode a webp image with animation and got:
webp: invalid format

The behaviour of gif.Decode in this situation is to decode the first frame. And then there is gif.DecodeAll which gives you a struct with all frames and the timing etc. information. It would be nice to have a webp.DecodeAll or similar.

Animated WebP has depressingly poor support, even on Android, despite being vastly superior to GIF in many, many different ways. It would be fantastic if Go could add it.

CC @nigeltao
I doubt that anybody is opposed to doing this, but somebody has to do the work.  I'm not sure that this needs to be a proposal at this stage.  Accepting a proposal won't cause the work to be done.

Yeah, I agree with what @ianlancetaylor said. I certainly don't have the spare time myself to work on this.

A sample image can be found here: https://mathiasbynens.be/demo/animated-webp

I have a working implementation of this, I just need to clean it up and submit a PR.

https://go-review.googlesource.com/c/image/+/513295


Adding Standard Connections to the WDC Simulator

This pull request adds support for Standard Connections to the WDC Simulator. It appears when you select the advanced UI. It creates tabs for each connection as well as the validation results and an interactive visualization of the standard connection.

@jagreene can you have a look at this PR?

I'll look at it as soon as I get back in the States on Monday
On Fri, Aug 5, 2016, 1:30 PM brandoconnor<EMAIL_ADDRESS>wrote:

@jagreene https://github.com/jagreene can you have a look at this PR?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tableau/webdataconnector/pull/100#issuecomment-237941764,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGRDVMblnIBw1DdrbF2aetK1YPV5SoWKks5qc482gaJpZM4JdMwy
.

We should figure out testing duties, now that people besides me are adding features. If you want to add the unit tests, I can add the end to end? Also, now I know that nyc doesn't check for coverage in files that don't have tests :P I'll fix that.

Just committed some changes to address the comments from Austin (thanks for going through it!)

looks like there are merge conflicts, would you mind rebasing off of the current dev, after that, and we figure out tests, I'd say it LGTM

Maybe we should wait on resolving the current conflicts until shortly before this is added to the dev branch? The exact timing on that hasn't been decided yet so we might have to rebase it a second time if other things are added before then. In the meantime we can decide on how to do the tests for this and get that ready.

Yeah, good point. Somebody is going to have to rebase it before they can run the tests though because I merged in some test fixes to dev in the interim.

Ah I see, so we won't be able to test the test code without rebasing the new test fixes first?

I mean you could but there will be extra failings and some of the failures were silent on GH

Well, in that case we should probably rebase it for the test case and again for the actual release if needed. Do you want to take some time tomorrow and talk about how we should test it?

Sounds good!

Probably want to get rid of the yep.png file :P

Coverage increased (+1.8%) to 100.0% when pulling 0f24466d995e5b401cb11c9739cbe04b9d2e649f on standard-connections into 42740e8928876c279627cac48fa2a8624051e055 on dev.

Coverage increased (+1.8%) to 100.0% when pulling 103bc3b20008ef26c8b05fcc84f757091b85b6f3 on standard-connections into 42740e8928876c279627cac48fa2a8624051e055 on dev.

100% coverage! Gold stars for @jimmy-jia and @jagreene !


refactoring project

Related to Issue: #63

I guess let's update the readme in ext to call them "Extensions" now?

need to change the package name pixelgl -> opengl


add a message to CancellationExceptions in order to not loose informa…

…tion upon streaming, this also fixes flaky kill tests

ack


Split Duration and NICT milliseconds consideration in Financial Metri…

…cs graph

Overall duration is not correctly mapped before. Now its correctly mapped as well as milliseconds consideration in Financial Metrics Graph has included


New address model

The working group will have a model to present at the March 14 meeting. After approval we'll submit a PR.

Dan has all files ready, but ontology changes need to be integrated into current develop branch. Michael and Dan will work on the PR.
Where should document reside?
Jamie: In gist-doc repo. Add link to the file in the Release Notes.
Ideally we need two documents:

Description of changes - add to migration folder in gistCore.
Description of model and how to implement - add to gist-doc.


chore(main): release 1.1.0

:robot: I have created a release beep boop
1.1.0 (2023-11-23)
Features

add FileLoggerStrategy (2c35468)

Tests

add FileLoggerStrategy tests (9a61214)
improvement BasaltLogger tests (4af8112)
improvement ConsoleLoggerStrategy tests (7d2a52f)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/Basalt-Lab/basalt-logger/releases/tag/v1.1.0 :sunflower:


Tiny docs updates

A typo, one thing that was not obvious for me, and an example of using http_method and body. Feel free to cherry-pick or edit :)

Current coverage is 90.41%

Merging #57 into master will not affect coverage as of fd5f572

@@            master     #57   diff @@
======================================
  Files            9       9
  Stmts          407     407
  Branches        76      76
  Methods          0       0
======================================
  Hit            368     368
  Partial         20      20
  Missed          19      19

Review entire Coverage Diff as of fd5f572

Powered by Codecov. Updated on successful CI builds.


⚠ Bofrost.lu has degraded performance

In 078769d, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1117 ms

Resolved: Bofrost.lu performance has improved in 54fd0d3.


Is pynt used to create an executable file from a Python script?

No, but pynt could be used to setup a build script to run cx_Freeze, which DOES make an executable file from a python script
Think of pynt as a MAKE/automake/MSBUILD equivalent for python. You'd need a compiler (which pynt isn't) to do what you suggest


TextYankPost receives visual = true for treesitter objects

Describe the bug
When executing regular yanking operations such as yaf, yaa, yif, yia etc. TextYankPost event payload receives an incorrect visual=true as opposed to visual = false, which is what is received for regular built in text objects (yiw, yap etc). Therefore when yanking the function body, the highlight is not observed, as compared to yanking the word, which does correctly highlight it. Obviously happening since the auto command configures visual = false, but the even data receives visual = true. The following observations were made - The event received by vim.highlight is as if it was done in visual mode. Excerpt from vim.highlight which demonstrates why yaf highlight does not work with the above auto command.
opts = opts or {}
  local event = opts.event or vim.v.event
  local on_macro = opts.on_macro or false
  **local on_visual = (opts.on_visual ~= false)**

  if not on_macro and vim.fn.reg_executing() ~= '' then
    return
  end
  if event.operator ~= 'y' or event.regtype == '' then
    return
  end
  **if not on_visual and event.visual then
    return
  end**

To Reproduce
Having installed and configured treesitter and treesitter text objects plugins only
local status_ok, configs = pcall(require, "nvim-treesitter.configs")
if not status_ok then
    vim.notify("Unable to load of find plugin nvim-treesitter", vim.log.levels.ERROR)
    return
end

vim.cmd [[
      augroup GENERAL
        autocmd!
        autocmd TextYankPost * lua require('vim.highlight').on_yank({timeout = 250, on_visual = false})
      augroup END
]]

configs.setup({
    textobjects = {
        select = {
            enable = true,
            keymaps = {
                ["aa"] =<EMAIL_ADDRESS>                ["ia"] =<EMAIL_ADDRESS>                ["af"] =<EMAIL_ADDRESS>                ["if"] =<EMAIL_ADDRESS>                ["ac"] =<EMAIL_ADDRESS>                ["ic"] =<EMAIL_ADDRESS>            },
        },
    }
})

Having the following (dummy) piece of code
int main(int argc, char **argv) {
  int k = 12;
  k++;
  printf("Hello, World!\n");
  printf("Hello, kval! %d\n", k);
  printf("Hello, argc! %d\n", argc);
  for (size_t i = 0; i < argc; i++) {
    printf("%s\n", argv[i]);
  }
  fflush(stdout);
  return 0;
}

Executing yaw, this is what vim.highlight reports for vim.v.event
{
  inclusive = true,
  operator = "y",
  regcontents = { " main" },
  regname = "",
  regtype = "v",
  visual = false
}

Executing yaf, this is what vim.highlight reports for vim.v.event
{
  inclusive = true,
  operator = "y",
  regcontents = { "int main(int argc, char **argv) {", "  int k = 12;", "  k++;", '  printf("Hello, World!\\n");', '  pr
intf("Hello, kval! %d\\n", k);', '  printf("Hello, argc! %d\\n", argc);', "  for (size_t i = 0; i < argc; i++) {", '
printf("%s\\n", argv[i]);', "  }", "  fflush(stdout);", "  return 0;", "}" },
  regname = "",
  regtype = "v",
  visual = true
}

Expected behavior
When yanking a custom object, the event will not mark the action/operation as if it was being done in visual mode
Output of :checkhealth nvim_treesitter
========================================================================

INFO: Runtime ABI version : 14
OK: Loaded parser for bash: ABI version 13
OK: Loaded parser for c: ABI version 13
OK: Loaded parser for cmake: ABI version 13
OK: Loaded parser for commonlisp: ABI version 13
OK: Loaded parser for dockerfile: ABI version 13
OK: Loaded parser for json: ABI version 13
OK: Loaded parser for latex: ABI version 13
OK: Loaded parser for lua: ABI version 13
OK: Loaded parser for markdown: ABI version 13
OK: Loaded parser for markdown_inline: ABI version 13
OK: Loaded parser for toml: ABI version 13
OK: Loaded parser for vim: ABI version 14
OK: Loaded parser for yaml: ABI version 13

Output of nvim --version
NVIM v0.7.2
Build type: Release
LuaJIT 2.1.0-beta3
Compiled by runner@fv-az164-457

Features: +acl +iconv +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/share/nvim"

Bug was initially reported in neovim repo, but was redirected to here instead - https://github.com/neovim/neovim/issues/19687

The same problem. vim.highlight.on_yank with on_visual set to true works as expected.

I did some digging to see what is going on and found some more information:
Under the hood, the plugin has to enter visual mode to make our precise selection to be yanked, this is why vim sets visual to true in the TextYankPost event.
I then looked for other plugins that add textobjects and found mini.ai and targets.vim. Both also enter visual mode and also have the issue with highlight.on_yank described here.
The source for highlight.on_yank is pretty closed off as wel, there is no way to override the option as it is given in the user created auto command. And there is no way of editing vim.v.event from outside of the same auto command, see https://neovim.io/doc/user/eval.html#v:event.
So the only possible solution/workaround I can come up with is adding to the plugin's configuration, something like:
{
    textobjects = {
        highlight_on_yank = {
            enabled = true,
            higroup = 'Search',
            timeout = 100,
        },
    },
}

And after doing our selection, manually calling vim.highlight.range() with the configured settings.
@theHamsta sorry if mentioning is wrong, but I think you are the lead maintainer: do you have any thoughts on this and would a PR from me be welcome that adds this configuration and calling of vim.highlight.range()?


Refactor Perceptron Tagger

cf @honnibal's feedback at https://github.com/nltk/nltk/pull/1143#issuecomment-143524107

Closing #1149 should have resolved this and there's only one averaged_perceptron_tagger.pickle file in nltk_data/taggers/averaged_perceptron_tagger/ now.


OAuth2 registered apps not visible for other users in organization

We've followed the documentation for adding OAuth2 integration for our applications and successfully configured the integration.
However, the apps registered via https://app.vsaex.visualstudio.com/app/register are visible only on the account of the developer that has configured the integration. That is suboptimal as we should have this configuration on the organization level or at least have a way to share access to these configurations among developer accounts.
So my question: Is there a way to share registered apps among accounts (I mean access to their configuration)? Is it a missing feature or a lack of documentation?

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

ID: ac47cbcf-45ed-81aa-b532-e7ad0046658e
Version Independent ID: 7aa1f60e-069f-3d62-5cac-b65e4b1116ef
Content: Authorization using OAuth 2.0 - Azure DevOps
Content Source: docs/integrate/get-started/authentication/oauth.md
Product: devops
Technology: devops-ecosystem
GitHub Login: @chcomley
Microsoft Alias: chcomley

@gat-bryszard  Thank you for the feedback.
This is likely an issue with the product opposed to documentation. All new features are currently tracked with the timeline.
To solicit feedback from the product team, please use Report a problem or Suggest a feature in the Azure DevOps community and provide a link back to this issue.
Assigning this to the author for confirmation.

Hi @gat-bryszard, Thanks for reaching out. As stated previously, This is likely an issue with the product opposed to documentation. All new features are currently tracked with the timeline.
To solicit feedback from the product team, please use Report a problem or Suggest a feature in the Azure DevOps community and provide a link back to this issue.
Closing for now, however you can @mention me at any time. Thanks so much!


TWI / i2c stops communicating after deep sleep (IDFGH-10238)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
v4.4.4
Operating System used.
Windows
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
CMD
Development Kit.
esp32c3
Power Supply used.
USB
What is the expected behavior?
I am using ESP32C3 in one of my projects to read the sensor data from SHT3x sensor. After reading the data, I publish this data on the TWAI (CAN) bus as well as on the terminal (idf.py monitor) and then put the unit to deep sleep with timer set for 10-30 seconds wake up time. Every time unit wakes up, it initializes everything, reads data, publishes it on the CAN bus and goes to sleep. And this loop just goes on. For debugging reasons, I keep the USB connected and I can see the data coming out every 10-30 seconds.

What is the actual behavior?
After a couple of loops, the unit fails to read the data from SHT3x sensor. No matter what I do with the SHT3x sensor, as long as ESP32C3 module is powered up, it always fails to read sensor data, as if the conversion is still under process. And the only way to fix the problem is to hard reset the ESP32C3 module. Check the SHT3x response after requesting for the data.

Update:
I have tested the code even without going into deep sleep. Just a simple loop, reading the data from SHT3x and after some time, say 1 - 2 hours, the ESP32C3 fails to read the data. And I know for sure that the sensor SHT3x has nothing to do with the error. Because, even if I reset the SHT3x sensor or restart the ESP32C3 module from software, it doesn't help. Only way to make it work is to hard reset the ESP32C3. In my solution, I have put a jumper between EN pin and GPIO9 to reset itself.

Steps to reproduce.
Use any ESP32C3 based dev board, connect SHT3x sensor I2C pins to GPIO5 as SDA and GPIO6 as SCL pin. I am using the following library from github for SHT3x.
https://github.com/gschorcht/sht3x-esp-idf
Or use any sensor that communicates over I2C with any ESP32C3 devkit and start fetching data from the sensor. Let it run for some time and keep monitoring the logs on the terminal. Eventually ESP32C3 would end up failing to fetch data. In your code, you can use any gpio to reset the ESP32C3 using "esp_restart()" function in the code. Remember, only the hard reset via reset pin can or will fix the problem and nothing else. Try it.
Debug Logs.
No response
More Information.
I have tried my code with both the variants i.e. ESP32-C3-MINI-1 and ESP32-C3-WROOM-02. The problem is persistent. And highly likely the problem lies within the chip and not the framework.

@embenix  Excuse me, but have you found the cause of this error?
I also used the same sht3x library, ESP32-S3 also got this error.

@embenix Excuse me, but have you found the cause of this error? I also used the same sht3x library, ESP32-S3 also got this error.

@Sotatek-TuHoang, unfortunately Not!
I have used a free gpio pin to reset the ESP module if such a condition is detected. My application is not very sensitive and so reseting the ESP module works just fine.


hides CLI profile list label flag

Summary
At the moment, there are some labels that minder uses internally, but we don't expose label managements to the end user. Therefore the --label flag in profile list is confusing. We should make the flag hidden. We should use cobra's hidden attribute to hide the flag.
Fixes #3300
Change Type
Mark the type of change your PR introduces:

[x] Bug fix (resolves an issue without affecting existing features)
[ ] Feature (adds new functionality without breaking changes)
[ ] Breaking change (may impact existing functionalities or require documentation updates)
[ ] Documentation (updates or additions to documentation)
[ ] Refactoring or test improvements (no bug fixes or new functionality)

Testing
Run make test, there are failures but not entirely sure they are related to the change made in the PR, and may be due to a local setup issue.
When building the CLI, the label flag does not appear anymore in the help information

Review Checklist:

[x] Reviewed my own code for quality and clarity.
[ ] Added comments to complex or tricky code sections.
[ ] Updated any affected documentation.
[ ] Included tests that validate the fix or feature.
[ ] Checked that related changes are merged.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Out of date install instructions

Should the readme and readthedocs install instructions be changed now that pip install tella is an option?

yes

Ah, getting ahead of myself. This isn't on pypi yet is it? But when it is, the install instructions should match!

working on pushing to PyPI

PyPI won't take it:
Invalid value for requires_dist. Error: Can't have direct dependency: 'gym @ git+https://github.com/openai/gym.git@778d3c2473a12ae229190f84404f3e2b0739ee35#egg=gym'

gym has had another release on pypi (v0.23.1) that contains the fix we needed. Update dependency to that version?

yes, creating a PR for that

Just noticed that SB3 requires gym<0.20 😵


v4 Migration docs still refer to .has-danger

From docs/4.0/migration.md
Forms

Moved element resets to the _reboot.scss file.
Renamed .control-label to .form-control-label.
Renamed .input-lg and .input-sm to .form-control-lg and .form-control-sm, respectively.
Dropped .form-group-* classes for simplicity's sake. Use .form-control-* classes instead now.
Dropped .help-block and replaced it with .form-text for block-level help text. For inline help text and other flexible options, use utility classes like .text-muted.
Dropped .radio-inline and .checkbox-inline.
Horizontal forms overhauled:

Dropped the .form-horizontal class requirement.
.form-group no longer applies styles from the .row via mixin, so .row is now required for horizontal grid layouts (e.g., <div class="form-group row">).
Added new .form-control-label class to vertically center labels with .form-controls.
Added new .form-row for compact form layouts with the grid classes (swap your .row for a .form-row and go).

Added custom forms support (for checkboxes, radios, selects, and file inputs).
Added HTML5 form validation support via CSS's :invalid and :valid pseudo-classes.
- Renamed .has-error to .has-danger.
Renamed .form-control-static to .form-control-plaintext.

This was replaced by .is-invalid

Hi @exige81, Do you want to send a PR with this? I can help you if you need a hand 👍

PR to fix this here: https://github.com/twbs/bootstrap/pull/23842


Fix repository issues pagination bug when there are more than one label filter

Fix #9500

If we want to exclude some label, we can use -1,2.

Codecov Report

Merging #9512 into master will decrease coverage by <.01%.
The diff coverage is 50%.

@@            Coverage Diff            @@
##           master   #9512      +/-   ##
=========================================
- Coverage    41.6%   41.6%   -0.01%
=========================================
  Files         573     573
  Lines       75679   75686       +7
=========================================
+ Hits        31489   31491       +2
- Misses      40277   40279       +2
- Partials     3913    3916       +3

Impacted Files
Coverage Δ

routers/repo/issue.go
37.66% <100%> (+0.04%)
:arrow_up:

modules/templates/helper.go
40.24% <33.33%> (-0.09%)
:arrow_down:

models/unit.go
62.16% <0%> (-5.41%)
:arrow_down:

services/pull/temp_repo.go
31.62% <0%> (-2.57%)
:arrow_down:

modules/repository/repo.go
33.55% <0%> (-1.98%)
:arrow_down:

modules/migrations/migrate.go
24.21% <0%> (-1.58%)
:arrow_down:

modules/migrations/gitea.go
9.03% <0%> (-0.64%)
:arrow_down:

models/repo.go
48.08% <0%> (+0.1%)
:arrow_up:

models/repo_list.go
74.07% <0%> (+0.92%)
:arrow_up:

models/error.go
34.14% <0%> (+1.11%)
:arrow_up:

... and 1 more

Continue to review full report at Codecov.

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

ping lgtm


Add skipOnFileExists maven property for skipping plugin execution when a file exists

Impact

[ ] Bug fix (non-breaking change which fixes expected existing functionality)
[x] Enhancement/New feature (adds functionality without impacting existing logic)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description
This PR adds a new property for the liquibase-maven-plugin to skip the plugin execution if the specified file exists. This feature is useful for certain edge cases, where the already existing skip property is not enough.
Things to be aware of

Impacts on the codebase: Minimal (just one more property and minimal logic)

Things to worry about
None
Additional Context

Thanks for the feature PR.
Could you explain your use case a little bit? I'm curious how you are using this. Largely because we are soon going to better unify the maven, the CLI, and other integrations to have as much of a common set of functionality as possible, and so wondering if it's something that really just need so to remain in maven or would apply well everywhere.

We basically need it to work around maven limitations.
Specifically, we have a company wide parent POM where we use the liquibase plugin for automatically generating test H2 DBs in the target dir. However, we don't want to do that every mvn verify run, so we also generate a test.NO_REGEN.db file. As long as this file exists, we don't want to regenerate the test DB. We already use the existing skip property for something else, so we also can't use hacks like this:
        <profile>
            <id>create-local-it-test-lq_cl-db-DISABLER</id>
            <activation>
                <file>
                    <exists>${basedir}/target/test.NO_REGEN.db</exists>
                </file>
            </activation>
            <properties>
                <skip-liquibase-test-db>true</skip-liquibase-test-db>
            </properties>
        </profile>

        <profile>
            <id>create-local-it-test-lq_cl-db-ENABLER</id>
            <activation>
                <file>
                    <missing>${basedir}/target/test.NO_REGEN.db</missing>
                </file>
            </activation>
            <properties>
                <skip-liquibase-test-db>false</skip-liquibase-test-db>
            </properties>
        </profile>

For the CLI this can be solved with a trivial if [ ! -f "<file path here>" ] in bash, but good luck trying to do complex conditional plugin activation in maven. Thus, this would be something maven specific IMHO.

Hi, is there a chance for this change to be merged? Would a more general solution be preferred? Is something missing?

Sorry for the delay, @mensinda. I was holding the PR for a bit as some possibly related refactoring work was being considered. Moving it along in the review process now.
Mostly what I was wondering was whether it should be a more generic fix across both the CLI and maven (and other integrations) or good to keep just in maven. We're working on bringing functionality to be identical between maven and the CLI, but there will always be at least some difference. As part of the full review process, we can think more on that and how it fits into the overall maven refactoring

No problem. Reading CLI, I (personally) don't really see the point for adding skip functionality, since thats what if is for in bash, etc. (see my comment from above). As for making it more generic:

Add support for a ! prefix for inverting the condition
Add support for multiple files with && and || evaluation + brackets

However, with each added feature, the skip expression will more and more resemble a scripting language, which probably wouldn't be desirable :)
My questions would thus be:

Should I make it more generic?

If yes, what features do you want (or rather how complex)?

Do you want it in the CLI regardles?

Is there a way to see why the "Run Functional Tests" CI is failing (so that I can try to fix it)? I get a 404 error when trying to view the details.

Is there a way to see why the "Run Functional Tests" CI is failing (so that I can try to fix it)? I get a 404 error when trying to view the details.

@mensinda, hello - No, the functional tests are internal Liquibase-access only. The tests are passing last time they ran. My guess is there were environmental or "expected" test validation failures that needed to be updated to match the latest core code.


Uncaught ReferenceError: videojs is not defined

Hi,
after building the plugin and importing in my project, trying to run the project gives me the following error :
videojs-http-source-selector.es.js:57 Uncaught ReferenceError: videojs is not defined
at eval (videojs-http-source-selector.es.js:57)
at Module../node_modules/videojs-http-source-selector/dist/videojs-http-source-selector.es.js (bundle.js:704)
at __webpack_require__ (bundle.js:20)
at eval (index.js:6)
at Module../index.js (bundle.js:97)
at __webpack_require__ (bundle.js:20)
at bundle.js:84
at bundle.js:87

after some digging, seems like this is a problem related to this generator-videojs-plugin issue, which happened because of something funky with rollup.
How to resolve this? Any help is much appreciated.

Hi @blumonn, I've the same error, did you find a solution?

I think the dist is broken in ES :
https://github.com/pivotshare/videojs-http-source-selector/blob/master/dist/videojs-http-source-selector.es.js#L1
Should it be videojs instead of videojs$1 ?

@bricesanchez I imported videojs in the components and built the plugin again. that seemed to work for me.

Until this is fixed via PR, I've been importing this library as
import videojs from 'video.js';
window.videojs = videojs;
require('videojs-http-source-selector');


Won't state passed to handlers change?

I thought the state passed to handlers will be the new state returned by handler/init/2 based on the API
init(Req, State) ->
    {ok, Req, State}.

and the description The last value of the tuple is a state that will be used in every subsequent callbacks to this handler in this doc https://ninenines.eu/docs/en/cowboy/2.0/guide/handlers/
But it doesn't work as I expected if it returns a new State. Do I misunderstand something?

Maybe the phrasing is not very good? State returned is used on the next call, which returns a new State used for the next call, etc.

@essen But from this code(https://github.com/ninenines/cowboy/blob/master/src/cowboy_handler.erl#L38), I didn't see where State is used.

I don't see a problem there. Just that in that function HandlerOpts is passed as second init/2 argument, State. Hasn't been renamed to InitialState yet is all.

But the returning result is {ok, Req2, [{result, Result}|Env]}, which doesn't change the new state. In the next call, State in init/2 is still the beginning value(HandlerOpts or InitialState).
Well, I changed an example to describe what I thought: https://github.com/tony612/cowboy/commit/e924525347b366e4ee6fc50f72fa588a024cb0ba

Yes because that's a different request. Handler processes and state are only per request.

Got it. But the code example and doc is still a little confusing to me. Opts will be a better word for me than State. Or maybe it's better to mention it's in one request.

It's State because it's the same as the State in other callbacks. It's not options; these became unnecessary now that we have maps. So the router will say InitialState, and everywhere else will say State.


cronjob should have escape signs for %

OS: Ubuntu 14.04
The curator jobs are created by the puppet module are like this.
/usr/local/bin/curator --master-only --host <removed> --port 9200 --logfile /var/log/curator.log --loglevel INFO --logformat default delete indices --prefix '<removed>' --time-unit days --older-than 5 --timestring '%Y.%m.%d'
The cronjob is not working. The % should be escaped like this: --timestring '\%Y.\%m.\%d'
more info:
https://github.com/elastic/curator/issues/151#issuecomment-130949428

i see that this is fixed in the master branch but there is no tag attached to this change.
We generaly only use tagged checkouts of modules since this is the only way to ensure unwanted code changes. Is it possible to release a 2.0.2 for this?

+1 I was scratching my head until I read this.

I believe this is the same as #56.  I'll be honest - I'm not quite sure which is correct. :)

It think the timestring should be '\%Y.\%m.\%d' to make sure that the escape character appears in cron.
I have set this up in hiera and applied for tomorrow mornings jobs and will report back.

Just confirm, this is my working hiera for the timestring:
timestring: "\%Y.\%m.\%d"
The cron jobs ran without issues this morning (I was supposed to have double backslashes to turn off the escape character)


chore: updated jest config, fix: semantic-release vuln

fixes #4

:tada: This PR is included in version 1.1.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add SingleBox::leak to provide access to a &'static mut

The use case for the added function is to provide a &'static mut.
So this
    static mut BUFFER: [u8; 1024] = [0u8; 1024];
    let buf: &mut [u8; 1024] = unsafe { &mut BUFFER };

can be replaced by
   static BUFFER: AllocSingle<[u8; 1024]> = AllocSingle::new();
   let buf: &mut [u8; 1024] = BUFFER.alloc([0u8; 1024]).unwrap().leak();

This avoids using unsafe in user code. In case the second line is accidentally run twice, it'll cause a panic instead of UB. (And even the panic could be avoided by replacing unwrap by appropriate error handling.)
Actual situation where this would be useful: https://github.com/rp-rs/rp-hal/issues/864
Please let me know if there's an easier way to do the same!

Won't your example stack allocate the array in order to move it into the 'heap' allocation?

Yes, of course. Could be avoided by using alloc_const_val.