Added Gitter social icon

Fixes #64
Checklist

[x] I have read the Contribution & Best practices Guide and my PR follows them.
[x] My branch is up-to-date with the Upstream branch.
[x] I have added necessary documentation (if appropriate)

Changes proposed in this pull request:

Added Gitter social icon for fossasia org channel both for chrome and firefox

Screenshots for the change

@0x48piraj @mariobehling please review this


Failed to pull image "azds/devhostagent:0.1.5" when trying to run a devspace (from VS)

Hi.
I am trying to run one service deployment in DevSpaces. After building Dockerfile.Develop I see the following error:
Successfully built b515369330da
Built container image in 1m 49s
Waiting for container...
pods/catalogapi-69bc6c679-9ndw9: Failed: Failed to pull image "azds/devhostagent:0.1.5": rpc error: code = Unknown desc = Error response from daemon: manifest for azds/devhostagent:0.1.5 not found
pods/catalogapi-69bc6c679-9ndw9: Failed: Error: ErrImagePull
pods/catalogapi-69bc6c679-9ndw9: Failed: Error: ImagePullBackOff

I checked in dockerhub and this image (azds/devhostagent) do not have tag 0.1.5.
Note: Using the command line (azds up) deploys succesfully with no issues.
I am using:

Azure CLI 2.0.42
Devspaces extension: dev-spaces-preview (0.1.6)
Azure Devspaces CLI 0.1.1918.5
Visual Studio Tools for Kubernetes 0.20.20180725.1

Thanks for reporting this issue. Our dev team is looking into it.

@eiximenis This issue should be resolved now, please try running the service again.


find a scalable solution for mountpoints

Currently changing the globablmountpoint list requires a rebuild of all containers - this is not scalable in the long term. Can anyone look into ways of not requiring the directories pre-created in the image? Do we know which HPC setups require this at the moment and can we convince the admins to change this?
Here a list of directories that users would like to have in addition to the ones we have:
/data for all data directories,
/media for external drives
/autofs for automounts
/scratch for scratch data
/tmp for temp outside docker
(but adding these right now would trigger a full rebuild, which I am hoping to avoid in the longterm)

tested and works: our containers on cvmfs will mount through any mountpoint defined in SINGULARITY_BINDPOINTS without having to create them inside the container


oblast: Avoid compilation error in scalar multiplication.

I was playing around with oblast and hit this compilation error...
Seems like blst has changed the interface of blst_p1_mult and this
compilation error has spawned.
error[E0308]: mismatched types
   --> oblast/src/lib.rs:279:25
    |
279 |                         &self.value,
    |                         ^^^^^^^^^^^ expected `u8`, found struct `blst_scalar`
...
298 | define_curve_struct!(P1, p1, G1, 48);
    | ------------------------------------- in this macro invocation
    |
    = note: expected raw pointer `*const u8`
                 found reference `&blst_scalar`
    = note: this error originates in the macro `define_curve_struct` (in Nightly bui

Dig into the internals of blst_scalar and get a raw pointer out of it...

There was a change in the blst_p1_mult function after blst version 0.3.2 which does break the code in oblast.
However, oblast does pin its version of blst at 0.3.2 here: https://github.com/ralexstokes/kzg/blob/main/oblast/Cargo.toml#L11
So I'll go ahead and close this for now. If we update the version of blst used in this crate then we will need to also adjust the interface like in this PR.
Thanks for the find @asn-d6 !


Persistent error: [ERROR] Gulpfile not found: .\gulpfile.js

This tracker is for bug reports only.
What were you expecting to happen?
I only get this:
[ERROR] Gulpfile not found: .\gulpfile.js
You can set the gulpFile attribute in ionic.config.json for custom Gulpfile locations, otherwise the default
Ionic Gulpfile can be downloaded from https://github.com/ionic-team/ionic-app-base/blob/master/gulpfile.js
    Or, if you no longer use gulp, you can remove the CLI Gulp Plugin:

    npm uninstall --save-dev --save-exact @ionic/cli-plugin-gulp@latest

but, i already tried many solutions, and I don't get run my app with ionic cordova.
Can Anybody help me please?

--> https://forum.ionicframework.com/ <--
This doesn't look like a gulp issue to me :)


feat(osko) Too many changes to summarize

basic mimirtool implementation
move apis from apis folder to the api folder, since it is more
kubebuilder compliant
add MimirRule type and controller
create helpers package
move fuctions responsible for creating the mimir rules and some
Prometheus rules into helpers package
add somehow updated high level dependency graph to DESIGN document
remove obsolete and unused crds
change Dockerfile API path

There are so many changes that it will be best to walk them through online with the reviewer.

Since I'm the only one who knows what this code does anyway, I will go YOLO on this PR.


CR-8211

Codecov Report

Merging #187 (b8545e8) into main (c8504f4) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #187   +/-   ##
=======================================
  Coverage   24.86%   24.86%
=======================================
  Files           1        1
  Lines         189      189
=======================================
  Hits           47       47
  Misses        136      136
  Partials        6        6

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 c8504f4...b8545e8. Read the comment docs.

/e2e

/e2e

/e2e

/e2e

/e2e

/e2e

/e2e

/e2e

/e2e

/e2e

/e2e


Move GemFire configuration to inner class

Added builder and moved config class as an inner class of GemFireVectorStore to match other vector store projects
Thank you for taking time to contribute this pull request!
You might have already read the [contributor guide][1], but as a reminder, please make sure to:

Sign the contributor license agreement
Rebase your changes on the latest main branch and squash your commits
Add/Update unit tests as needed
Run a build and make sure all tests pass prior to submission

@jhuynh1 As a general comment, please add your name as an author to all the classes you modified.


Mermaid 로 다이어그램 그리기

I am plan to add the existing markdown documentation to the uftrace.github.io homepage as read the docs. (Like the Linux kernel documentation)
Resources for reference are as follows.
Read the Docs's Markdown Tutorial Project
docs.readthedocs.io/en/stable/intro/getting-started-with-sphinx.html#using-markdown-with-sphinx
readthedocs/tutorial-sphinx-markdown
youtu.be/qRSb299awB0?t=3381
When drawing diagrams, We try to use mermaid supported by markdown as much as possible.

https://mermaid.live/edit
https://mermaid-js.github.io/mermaid/#/gantt

Markdowned mermaid source code interpreted like this.

flowchart LR
     p_client[FaaSnap \n Python Client];
    daemon[FaaSnap \n Daemon];
    firecracker[FaaSnap \n Firecracker VMM];

    p_client --> |request| daemon;
    daemon --> |request| firecracker;

flowchart LR
  subgraph FaaSnap FIrecracker VMM
    subgraph microVM1
	      subgraph FaaSnap Kernel1
	          direction TB
	          rootfs1 --> Flask1
	      end
    end
    subgraph microVM2
	      subgraph FaaSnap Kernel2
	          direction TB
	          rootfs2 --> Flask2
	      end
    end
  end


stage1: remove OnFailureJobMode=isolate

It was causing systemd in stage1 to block on shutdown.
When systemd starts the shutdown process it will broadcast SIGTERM to
every process. That will make exit-watcher.service and the app service
stop.
exit-watcher.service has the property
ExecStopPost=/usr/bin/systemctl isolate reaper.service

and the app service has the property
OnFailureJobMode=isolate

That means both will try to run in isolate mode and sometimes that was
getting systemd to a state where it's not executing any job:
-bash-4.3# systemctl --no-pager list-jobs
JOB UNIT                        TYPE  STATE
 30 halt.target                 stop  waiting
 18 exit-watcher.service        stop  waiting
 17 default.target              stop  waiting
 19 systemd-journald.service    stop  waiting
 16 system-prepare\x2dapp.slice stop  waiting
 13 reaper.service              start waiting

So it will stay blocked until something kills it (e.g. the unit that started
rkt on the host).
Removing OnFailureJobMode=isolate is fine because the app unit has the option
OnFailure=reaper.service

and reaper.service will save the apps' statuses and trigger a shutdown via
"systemctl halt --force".
The TestServiceFile functional test was failing sometimes with
RUN TestServiceFile
--- FAIL: TestServiceFile (10.02s)
        rkt_service_file_test.go:105: Test unit found in list, should be stopped

and with this commit I can't reproduce it anymore.
To validate my theory, I also tried without this commit but catching
SIGTERM in the test program and exiting with status 0 so the unit
doesn't fail and OnFailureJobMode doesn't get triggered and I couldn't
reproduce the failure either.

@vcaputo @poettering

Nice! LGTM.

Getting systemd into a mode were all jobs are waiting and none is executing is a real bug in systemd, and we should fix that in systemd. Any chance you can reduce this to a minimal producer for me that I can try in a container without having to pull in rkt?

@iaguis what's happening with this one?

If everything works without the OnFailureJobMode=isolate then lgtm, but I have a vague recollection of that being necessary for things to exit properly at the time.  Perhaps enough other stuff has evolved such that it's no longer the case.
But since both of the paths are isolating reaper.service shouldn't it just work?

My memory of this is also rather vague but I believe that OnFailureJobMode pre-dated the existence of reaper.service

I've been trying to understand this issue better but I didn't learn much about it.

I can reproduce with a service that just runs systemd-nspawn on a stage1 rootfs with the inspect binary and the PrintMsg loop option.
It only happens when using --keep-unit
I can't reproduce it anymore with this PR

I also tried with the unit file mentioned in #1096, I could reproduce it without this patch and I can't if I apply it...

But since both of the paths are isolating reaper.service shouldn't it just work?

I agree it should work but there seems to be some nasty systemd bug and this PR appears to be a workaround.
I don't really like merging things I don't fully understand but everything seems to work fine with this patch...
@poettering I'll keep trying to reduce it to a minimal producer and then I'll send it to you.

Any luck with a minimal repro?

@iaguis if this works, then I suggest to merge this and try to get a minimal producer for the systemd bug in a follow-up issue for milestone v0.8.0.

@jonboulle Didn't have time to create a minimal repro yet.
@alban ok, I'll merge it and create the follow-up issue. Thanks!

#1103


Generalize Primary Keys

Still working on this, but the branch is stable for the time being.

This branch is now more or less unusable, and is more of a personal sandbox.  I think something useful may come out of it.
Master should be functional now -- pushed some minor bugfixes this morning.  Those mostly stemmed from incompatibilities with the backend added when the label API changed.

Sounds good.  I left this as a TODO in the code because I suspected it would be a minefield.  Sounds like I was right. :)
I may try to implement a reduced version of this early next week... That is, just allowing the user to change the column containing the row keys.

Alright, it took some doing, but I think I this meets my goal.
I wanted to be able to properly process a file that looks like this:
This one is just empty,This is a comment,,,,,,
,Something else,,,,,,
,Sample,Label,"1,6-Anhydro-beta-D-glucose",1-Methylnicotinamide,2-Aminobutyrate,2-Hydroxyisobutyrate,2-Oxoglutarate
,,,META1,MET2,META3,META4,META5
,PIF_178,cachexic,40.85,65.37,18.73,26.05,71.52
,PIF_087,cachexic,62.18,340.36,24.29,41.68,67.36
,PIF_090,cachexic,270.43,64.72,12.18,65.37,23.81
,NETL_005_V1,cachexic,154.47,52.98,172.43,74.44,1199.91
,PIF_115,cachexic,22.2,73.7,15.64,83.93,33.12
,PIF_110,cachexic,212.72,31.82,18.36,80.64,47.94
,,,,,,,
,NETCR_014_V1,cachexic,31.5,6.82,4.18,12.94,25.03
,NETCR_014_V2,cachexic,51.42,30.27,7.54,34.81,80.64

This branch makes guesses about what rows and columns should be data, metadata, keys, and which rows are invalid and should be masked.
Without input, it should reduce the above to:
40.85,65.37,18.73,26.05,71.52
62.18,340.36,24.29,41.68,67.36
270.43,64.72,12.18,65.37,23.81
154.47,52.98,172.43,74.44,1199.91
22.2,73.7,15.64,83.93,33.12
212.72,31.82,18.36,80.64,47.94
151.41,36.6,8.67,42.52,223.63
31.5,6.82,4.18,12.94,25.03
51.42,30.27,7.54,34.81,80.64

...with the key and header rows you would expect.
There are a few breaking changes in the API to get here (only really related to row/col label PUT).  I'm not going to fix the UI until other folks have had a chance to provied feedback and Jon also gets a chance to try his ideas.
There are several types of edge cases in the input to handle, and I feel that they are in scope now (or would eventually be).

Did you intend to remove the composite keys for rows and columns or was that a mistake?

I like the idea of making the column and row names computed properties.  We can probably do that as a smaller change independent of the rest.
I'm not ready to get rid of the pandas indices.  If we really need to do that, we should just use python csv parser.  This is how I envision it working.

On ingest read the raw table (header=None, undex_col=None)
Do some heuristic guessing of the row/column types
Pass the raw table and guesses to the user for modification
Reparse the tables using the now assumed correct row/column types

The last step could work as follows:
def reparse_csv(table, rows, columns):
    return pandas.read_csv(
        BytesIO(table.iloc[rows, columns].to_csv(header=False, index=False).encode()),
        index_col=0
    )

def read_tables(raw_table, index_row, index_column, data_rows, data_columns,
                metadata_rows, metadata_columns):
    data_table = reparse_csv(raw_table, [index_row] + data_rows, [index_column] + data_columns)
    measurement_metadata = reparse_csv(
        raw_table, [index_row] + metadata_rows, [index_column] + data_columns)
    sample_metadata = reparse_csv(
        raw_table, [index_row] + data_rows, [index_column] + metadata_columns)
    return data_table, measurement_metadata, sample_metadata

Using your example csv file, I get
read_tables('index_test.csv', 2, 1, [4, 5, 6, 7, 8, 9, 11, 12], [3, 4, 5, 6, 7], [3], [2])

              1,6-Anhydro-beta-D-glucose  1-Methylnicotinamide  2-Aminobutyrate  2-Hydroxyisobutyrate  2-Oxoglutarate
Sample
PIF_178                            40.85                 65.37            18.73                 26.05           71.52
PIF_087                            62.18                340.36            24.29                 41.68           67.36
PIF_090                           270.43                 64.72            12.18                 65.37           23.81
NETL_005_V1                       154.47                 52.98           172.43                 74.44         1199.91
PIF_115                            22.20                 73.70            15.64                 83.93           33.12
PIF_110                           212.72                 31.82            18.36                 80.64           47.94
NETCR_014_V1                       31.50                  6.82             4.18                 12.94           25.03
NETCR_014_V2                       51.42                 30.27             7.54                 34.81           80.64

       1,6-Anhydro-beta-D-glucose 1-Methylnicotinamide 2-Aminobutyrate 2-Hydroxyisobutyrate 2-Oxoglutarate
Sample
NaN                         META1                 MET2           META3                META4          META5

                 Label
Sample
PIF_178       cachexic
PIF_087       cachexic
PIF_090       cachexic
NETL_005_V1   cachexic
PIF_115       cachexic
PIF_110       cachexic
NETCR_014_V1  cachexic
NETCR_014_V2  cachexi

These tables all have the correct headers and sample names.  These become the normalized versions of the tables passed to the analysis/visualization functions.

Thanks for that example.  I think I understand what you're suggesting.

On ingest read the raw table (header=None, undex_col=None)

You've helped me realize that the case I'm making against Pandas is only about this step.  I don't think Pandas provides any value on ingest, so the normal csv parser may be better suited here.

Do some heuristic guessing of the row/column types

This step will be easier with the simple iterables that come out of python csv.  for cell in table.iloc[:,col_half].fillna('').astype(str): makes my head hurt.

Pass the raw table and guesses to the user for modification

:+1:

Reparse the tables using the now assumed correct row/column types

So the input is 1) a raw CSV on disk and 2) the data models for CSVFile, TableRow, and TableColumn, and these 3 data tables are a derived product rather than a source of truth?  I'm totally in favor of this approach.
As derived products, we could totally cache them on disk but would need some way to invalidate the cache if a user changes the Row/Column labels or primary keys.  Seems premature.  Are you just doing that Pandas parsing for every API query?

Did you intend to remove the composite keys for rows and columns or was that a mistake?

That was intended.  The composite key will error for collisions in the following cases:

metadata columns have no headers in primary key row.  Example:

,,"1,6-Anhydro-beta-D-glucose",1-Methylnicotinamide
PIF_178,cachexic,40.85,65.37
PIF_087,cachexic,62.18,340.36

string duplicates in primary key row, because something in metadata differentiates them.  Example:

,,"1,6-Anhydro-beta-D-glucose","1,6-Anhydro-beta-D-glucose"
,Source,Spectrorama 9000,Thing in the basement from 1973
PIF_178,cachexic,40.85,65.37
PIF_087,cachexic,62.18,340.36

The first case definitely needs to be handled.  There's no reason in my mind why the second case shouldn't also work.  The fewer unnecessary errors we can show users, the better.  We could raise this as a warning on data validation on the cleanup page, but I believe the user should have the option to ignore that warning.

I don't think Pandas provides any value on ingest, so the normal csv parser may be better suited here.

I think it still does.  There is better handling of comments, empty lines, character encoding, missing columns/invalid rows.  Plus, using different parsers could result in different tables... e.g. raw csv parser creates an empty row and pandas automatically removes it.  Unless there is something specific that pandas can't handle, I think it's better to use it everywhere.

This step will be easier with the simple iterables that come out of python csv. for cell in table.iloc[:,col_half].fillna('').astype(str): makes my head hurt.

I think you're just biased against pandas :).  The primary benefit is the read -> write loop generates a normalized version of a csv file that is consistent with what R expects.  Pandas was design to mimic R after all.

As derived products, we could totally cache them on disk but would need some way to invalidate the cache if a user changes the Row/Column labels or primary keys. Seems premature. Are you just doing that Pandas parsing for every API query, then passing all 3 to transformations and visualizations?

I'm not worrying about performance until we have a better idea where the bottle necks actually are.  There are clearly repeated computations that we can optimize.  When we get there, I might try to use memcached.

That was intended. The composite key will error for collisions in the following cases:

I don't see the problem with composite keys.  The unique constraint was removed when I made the the names derived.  The composite keys are (csv_file_id, row/column_index).  The index in this case is just a 0-based integer describing the row/column number; that can't be duplicated.

Pandas

Those are all fair points.

The unique constraint was removed when I made the the names derived.

I admittedly hadn't read that PR yet.  That takes care of my concerns.  Thanks.
With those issues settled, there's nothing really in this PR of value aside from a suggestion for 2: Do some heuristic guessing of the row/column types.  I just iterate through the middle row and middle column and label based on what data types are found there.
I'll leave the branch for reference and close this PR.
Thanks for the discussion, Jon!

I still need to handle mutation of index rows/columns, but this work was helpful to clarify some of the issues.

Agreed @jbeezley. Other benefits of using pandas parsing:

It is probably the most resilient code path, because people worldwide are doing pandas csv reading lots more often than using the builtin Python csv parser.
We ideally want to "test ingest" using the same libraries that will be doing the stats processing. We don't want the csv read to succeed during data cleanup then have it fail during stats processing (or have it prematurely fail if it would have succeeded in stats processing). We will probably want to continue to support pandas algorithms, and may even want to eventually do a "test ingest" in R to ensure downstream stats algorithms will work as expected.


Add benchmarking script

This PR will add a bench.sh script which will run the benchmarking tests
for base, sse, and avx implementations.
Also, the dep package manager is used to resolve dependencies.

@chewxy If you merge this in, will you also add a release tag? I am using this and would like to lock the version.

Coverage remained the same at 92.388% when pulling 7e15d3b2bda206d5c6be68cd39afae354f9801de on NDari:master into 1f59516136c1a7f1c19871d3dc5f0d9928ffbd7c on chewxy:master.

Coverage remained the same at 92.388% when pulling 7e15d3b2bda206d5c6be68cd39afae354f9801de on NDari:master into 1f59516136c1a7f1c19871d3dc5f0d9928ffbd7c on chewxy:master.

Coverage remained the same at 92.388% when pulling 7e15d3b2bda206d5c6be68cd39afae354f9801de on NDari:master into 1f59516136c1a7f1c19871d3dc5f0d9928ffbd7c on chewxy:master.

Coverage remained the same at 92.388% when pulling 32c28d777988642d83fb697e3402064d9f85c748 on NDari:master into 1f59516136c1a7f1c19871d3dc5f0d9928ffbd7c on chewxy:master.

Coverage remained the same at 92.388% when pulling 5bd0436884503537f1d37b8aa2d8d5e03ea4ce03 on NDari:master into 1f59516136c1a7f1c19871d3dc5f0d9928ffbd7c on chewxy:master.


sbt should issue a warning about ignoring javaOptions when fork is set to false in build.sbt

The following is not being honored when fork is set to false.
javaOptions in Test += "-Dconfig.file=conf/application_test.conf"
It works fine when the fork parameter is removed from build.sbt
sbt version 0.13.5.

From SBT itself:
> help javaOptions
Options passed to a new JVM when forking.

javaOptions is only used when forking new JVMs.

the fork is set to false not to true. what is the default value for fork in sbt?

Again, from SBT itself :
> show test:fork
[info] false

SBT does not fork new JVMs by default.

show test:fork
[info] true

Getting it as true by default on version 0.13.5

It must have been overriden someplace else in your build, possibly from a plugin, as false is indeed the default value : https://github.com/sbt/sbt/blob/0.13.5/main/src/main/scala/sbt/Defaults.scala#L152

seems like you are correct, but why is it not honoring my javaOptions when fork is set to false.

See my previous comment. javaOptions is only used when forking new JVMs. If fork in Test is set to false, javaOptions in Test is simply not used, since you're not forking new JVMs.

It would have been great if it takes java options when fork is set to false. I don't need to supply it from the command line. I can simply say "sbt clean test".
Can this be an enhancement?

@stammana Not really.   By the time sbt has read your build file, the JVM is already instantiated and we can't send javaOptions to it.  The only way to send java options is to fork a new JVM where you can pass them in, you cannot set them after it's been started.
So, you can either set javaOptions to true, or you can use one of the startup script tricks of creating a .sbtopts file and putting your java options in there.
At a maximum, we'll just issue a warning when people do this.

Closed with #2103


c166 audit

Hopefully this fixes more than breaks, feel free take lines of code from this
branch if the PR is too much, no problem about attribution if this is the case
Looks like a rewrite, but mostly due to variable re-naming to get
a better idea of how things align with the manual
Added comments for the instruction display and byte sequence
Added ESPR and SPR registers to pspec and better handled in slaspec
which cleaned up the 8-bit addressing code
Added DWARF mapping just cause I had that document out reading up on (E)SPR
Still need to add to the ldef if it looks good and you want to include it
Minor bug fixes in display section (shouldnt affect analysis, just readability)
Minor bug fixes in a few table constructors ('mem' change should be noticeable)
Cleaned up access to IP, previously the high byte could get cut off
Cleaned up SP access, previously used 'Stack' variable instead of SP
This might need revisiting (how are all the different stacks setup?)
ATTN  I did probably break signed a lot since the 2's complement description
vs the supplied data didn't make sense to me (how #dataN work)
but since you have flag tracking so well, it should/might pick up that
detail in the decompiler

Great job, thanks!
Sorry for delay. Right now I only have access to small laptop, which makes harder to work with ghidra. And I dont know, how long it will be last...
Looks like memory access works much better, thanks!
I will record found errors to issues page of this repo, if you dont mind.

ATTN I did probably break signed a lot

please explain in more detail, what do you means

No problem on the delay, hope all is well.  That's unfortunate about only having a tiny laptop.
You had previously used tokens that were signed for some of the #dataX.  I did not have them signed as the description of the #dataX made them sound like zero-extended only.  I might have misunderstood this part.
But then (since it makes sense to use signed in them) the instructions describe themselves as doing 2's complement math.  This may still be the case currently since you are calculating flags.  I guess I need to go through the binary to find a couple of good use cases of negative numbers before this merge and see how my changes have effected them


{Revert} az network nat gateway: Validate attaching public IPs

Description

Service Team would like to withdraw this feature:

https://github.com/Azure/azure-cli/pull/21483

This reverts commit 625f0306bcf016853c67747733d1808c24972c2c.
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

/azp run

Revert


Various run_interop_tests.py fixes

-- after starting the interop server, we can't expect docker port to immediately return the exposed port, we need to add retries
-- use "cxx" instead of "c++" when generating docker container names, plus character is not legal
-- start running empty_stream interop test
-- stop polluting output with output of subprocesses (this should also prevent prevents breaking terminal echo when running from terminal locally)

Looks straightforward (thanks for summarizing the changes in the CL description). LGTM

This does not influence any of the run_tests.py tests, so I will just merge without waiting for jenkins.

sounds good.


⚠ AsianCinema has degraded performance

In c0ac42e, AsianCinema ($ACM) experienced degraded performance:

HTTP code: 200
Response time: 6420 ms

Resolved: AsianCinema performance has improved in f3aa536 after 9 minutes.


[Event Request] Page 55 "Purch. Invoice Subform" - procedure InsertExtendedText()

    procedure InsertExtendedText(Unconditionally: Boolean)
    begin

----------------------- MODIFY EVENT ----------------------
        IsHandled := false;
        OnBeforeInsertExtendedText(Rec, IsHandled);
        if IsHandled then
            exit;
----------------------------------------------------------

        if TransferExtendedText.PurchCheckIfAnyExtText(Rec, Unconditionally) then begin
            CurrPage.SaveRecord();
            TransferExtendedText.InsertPurchExtText(Rec);
        end;
        if TransferExtendedText.MakeUpdate then
            UpdateForm(true);
    end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Darrielle was here

Thanks for the cool stickers

Thanks for the cool stickers

https://github.com/GH-Event-Demos/random-name-picker/issues/35


fleece build command has no documentation

fleece run has a pretty good overview about how it works, and what it expects in order to work. It would be nice to have the same level of detail about fleece build, because I couldn't really get it working without reading the source code.

Fixed by #56


Stability improvements and enhancements (simplified read op)

All tests pass so far, but there's still a number of things that need to be done.
I'll highlight remaining work using the code review features of github.
One thing I haven't figured out is how to simplify writes to a data object.

I need to add a test for the simplified read op too.
There may be other things, but I'll catch them as this PR approaches completion.

Reorganized commits. All tests except one pass (I tweaked a thing).
Just need to handle that failing test, a few more review comments, and make sure there's tests for all issues.

All tests pass. Confirmed the validation code works with the docker image.
Remaining items include:

Resolving review comments
Updating docs to use "Optional" more (may happen in a separate PR)

Am I missing anything?

Taking out of draft as I think the main things are handled.

For those doing the review, you may want to look at each commit individually so the work is easier to consume/understand.

Preparing to squash and run tests.

Squashed and all tests pass.

agreed

Added #'s.


Add framework in standstill state to account page

Depends on:

[x] https://github.com/alphagov/digitalmarketplace-api/pull/275
[x] alphagov/digitalmarketplace-api#282
[x] https://github.com/alphagov/digitalmarketplace-utils/pull/204
[x] https://github.com/alphagov/digitalmarketplace-frontend-toolkit/pull/177
[x] https://github.com/alphagov/digitalmarketplace-supplier-frontend/pull/327

--
The aim of this is to encourage any suppliers that have logged in to either:

download and sign their framework agreements (if they're on G-Cloud 7)
look at their result letter (if they failed)

This meant a lot of refactoring to get the account page to be framework agnostic. There’s still some hard-coded stuff around the dates because I didn’t know where to put it.
The approach is as follows:
Step 1

take all the frameworks
take all the frameworks a supplier has interacted with (from alphagov/digitalmarketplace-api#282)
munge them together

Step 2

sprinkle some extra properties on each framework, eg made_application is derived from declaration status and complete drafts

Step 3

flip reverse the frameworks so they are in a dict keyed by status
send this dict to the templates
for each framework state, loop through all the frameworks in that state and
render the appropriate template (ie live frameworks show different information
from open frameworks)

--
Sorry for the mega commit :(
--
The four possible states you can be in when a framework in standstill are:

you haven't made an application
you've made an application but failed
you've made an application but not returned your framework agreement
everything is :+1:

When G-Cloud 7 is in standstill
You failed to get on G-Cloud 7

You’re on G-Cloud 7

You’ve signed the agreement

--
When G-Cloud 7 is live
You still haven’t signed the agreement

You’ve signed the agreement

--
Reviewed by @cathrooney and @ralph-hawkins

dmutils needs to be bumped to 13.1.0

@robyoung aaf8fe0

Some of the tests could use the function for mocking supplier frameworks but that's introduced in my PR so I can do it there :+1:


Python idioms in the API

The README mentions that:

So far this extension has been written by folks who are primarily Rust programmers, so it's highly likely that there's some faux pas in terms of Python idioms. Feel free to send a PR to help make things more idiomatic if you see something!

Indeed, after using the API for a while I noticed a few aspects that aren't quite in line with Python conventions, though some of them are harder to ignore than others.

Nullary getter methods like ExportType.name that always succeed and always return the same value are a pretty clear-cut case for using Python properties instead. This is, by far, the least idiomatic aspect of the library, and it's very easy to miss a () that feels like it shouldn't be there.
There are lots of unary setter methods like Config.debug_info named after the property they're changing, and there is a good case for using Python setter-only properties instead. (As a bonus, if wasi-c-api ever adds getters for them, they could be made readable in a backwards compatible way.) This doesn't change much for e.g. Config, but for Linker for example allow_shadowing works like a simple setter with no side effects, but define_wasi, while similarly imperatively named and used, irreversibly changes its state.
Nullary casting methods like ExternType.func_type feel very odd overall.
1. They're named like accessors, but they work like dynamic_cast.
2. The naming is inconsistent for conversion in different directions—FuncType→ExternType conversion is done by as_extern, but ExternType→FuncType conversion is performed by func_type.
3. My impression so far is that most uses of these casting methods are in contexts where a specific type is expected, in which case it would be more convenient if they raised TypeError instead of returning None. (If they did, another method would be necessary to dispatch on an unknown type.)
Val.get_* introduces a third naming scheme for type conversion functions, one that clashes in meaning with e.g. Instance.get_export.
*.get_export() methods seem like they would only fail in truly exceptional conditions and so also appear good candidates for raising an exception instead of returning None.

To summarize:

I would change simple getters and setters to be properties.
I would rename all casting methods to as_*().
I would change *.get_export() to raise if the export is not found (this is particularly important for Caller.get_export(), since currently it looks like there is no way to distinguish the cases of "export does not exist" and "the caller is gone" at all, even for debugging, and the exception message would allow that).
I would probably change the dynamic casting methods to raise if the type is wrong, and add a matching is_* method for the cases where dynamic dispatch is indeed necessary. I'm not completely certain about this one, but it seems that currently, dynamic dispatch would look something like:

if extern.memory():
    do_something_with_memory(extern.memory())
elif extern.table():
    do_something_with_table(extern.table())

so changing it to:
if extern.is_memory():
    do_something_with_memory(extern.as_memory())
elif extern.is_table():
    do_something_with_table(extern.as_table())

doesn't really make it any worse.
What do you think? All of these changes are likely to break most existing code, so I'd rather discuss them before working on a PR.
Also, I should mention that "do nothing" is an option. In general Python libraries are a lot looser with conventions than libraries in many other languages; I'd rather see the API improved, personally, but the current one isn't drastically more inconsistent than what one would expect in general.

I'm working on the Perl bindings for wasmtime which is based heavenly on wasmtime-py, and I'm not a Python programmer, but my unsolicited thoughts:

I like the idea of renaming the casting functions to have a consistent as_ prefix, in fact this is mostly how I implemented for my Perl bindings.  It also more closely resembles the c-api, so familiarity with one is helpful for the other.

I also like having the is_ methods, I think that helps the reader understand the intent of what you are doing.  In Perl I have kind and kind_num methods that wrap around the c-api, which gets you this same information, but the cost there is either converting to a string, or exporting constants.

I'm not as sure about get_export raising an exception, to me it makes sense for None (or undef in my case) to be returned when you ask for something that doesn't exist.  It would make chaining more sensible though .get_export("foo").as_func().call() doesn't try to call as_func on None.  I'm uneasy about this one though because again, I'm not a Python programmer, and I haven't even tried to build wasmtime-py, just my opinion based on implementing get_export in Perl.

It's cool to have a similar project in another scripting language to crib off of.

3. I'm not as sure about get_export raising an exception, to me it makes sense for None (or undef in my case) to be returned when you ask for something that doesn't exist.

This is actually an established and widespread Python idiom called EAFP. Personally, I follow it very cautiously; for example, dictionary indexing raising KeyError that you are supposed to catch is a source of subtle bugs because the try: except: construct is unwieldy and it is tempting to put something besides the index operation itself in the try: expression, but of course now you may have caught an exception raised by third party code that should have bubbled up.
In this case however, assuming my intuition about the use of .get_export() is correct--that the vast majority of invocations are likely to succeed, and failures indicate logic errors--it seems like a solid case for that idiom. Consider that it would work much like the built-in dictionaries.

These all sound like great ideas to me, I think a PR would be great!
It's probably possible to simply remove all casts entirely, we can probably do dynamic type checks to figure everything out at the API layer.
@whitequark did you want to work on a PR for this? If not I can try to whip something up myself.

did you want to work on a PR for this? If not I can try to whip something up myself.

Please feel free to do so, my hands are quite full :)

Ah, maybe this will save you a bit of time--the way you can make a setter-only property in Python is not obvious. This works:
setter_property = lambda fset: property(fset=fset)
class foo:
    @setter_property
    def bar(self, value):
        print(value)
foo().bar = 1 # 1
foo().bar # AttributeError: unreadable attribute

Ok I've opened up https://github.com/bytecodealliance/wasmtime-py/pull/5 which covers points 1/2/4 from your summary above.
Like @plicease though I'm a little hesitant to raise an exception from get_export (on both Instance and Caller). Is there perhaps a way to have both though? Is it possible to do something like:
instance.exports.foo # raises if invalid
instance.get_export("foo") # returns None if invalid

Is there perhaps a way to have both though?

There are a few ways. Regarding your suggestion,

instance.exports.foo # raises if invalid

in my opinion this is not an appropriate place to override __getattr__. There are a number of issues with such an override, chiefly, name clashes (adding another method to that class becomes a breaking change), the need to use getattr or __getattr__ if the identifier is non-alnum or has interpolations, and the ambiguity in an expression like instance.exports.memory--can you say whether the name "memory" reserved and provided by wasmtime, or available for use and provided by the instance?
I have two proposals. The first is to remove get_export entirely and provide an exports object that behaves like a normal Python dict:
instance.exports["foo"] # KeyError: "foo" if invalid
instance.exports.get("foo") # is None if invalid

For Instance this would require replacing the existing exports property that returns a list with one that returns a proxy object indexable by either an int or a str, and iterable in the same way it currently is. One additional benefit of this approach is that doing something like instance.exports[n] in a loop becomes much cheaper than it is now.
For Caller this would require adding a new exports property that returns another proxy object, this time indexable only with a str.
The second proposal is adding an optional default value to get_export. (The dict.get() method has one.)
instance.get_export("foo") # raises if invalid
instance.get_export("foo", default=None) # returns None if invalid

I think either solution is fine, but I somewhat prefer the first one. It is more involved to implement though.

That sounds like a great suggestion to me! -- #6

Thanks for the fix!


Document title in studio is displayed as JSON

After installing the plugin and creating a schema with one field of type localizedString as follows
export default {
    title: "Product Tag",
    name: "product_tag",
    type: "document",
    fields: [
      {
        title: "Name",
        name: "name",
        type: "localizedString",
      }
    ]
}

Studio displays the product tag document title in JSON for example name: {ar: عزل, en: isolation}

It would be better if Studio displays only the value of the default language automatically to look normal

You can customise the preview key of your schema to use the default language name like so:
  preview: {
    select: {
      title: 'name.ar',
    },
  }


⚠ BCR Bot has degraded performance

In 029440e, BCR Bot (https://bcr.alternativasinteligentes.com/BCRApi/web/chatbot) experienced degraded performance:

HTTP code: 200
Response time: 881 ms

Resolved: BCR Bot performance has improved in 340850e.


wb: line 14: Segmentation fault (on wd config)

Running a couple of simple commands (wd config) returns Segmentation fault.
No such problem with eg wd summary (though that runs quote slow and shows no color, I'll investigate).
I'm running Windows 10, Cygwin<EMAIL_ADDRESS>wd config
/cygdrive/c/Users/vladimir.alexiev.000/AppData/Roaming/npm/wb: line 14:  7324 Segmentation fault      node "$basedir/node_modules/wikibase-cli/bin/wb" "$@"

  Usage: wd-config [options] <key> [value]

  get and set configuration parameters

  Options:

    -h, --help                   output usage information

wd config -h
/cygdrive/c/Users/vladimir.alexiev.000/AppData/Roaming/npm/wb: line 14: 16584 Segmentation fault      node "$basedir/node_modules/wikibase-cli/bin/wb" "$@"

  Usage: wd-config [options] <key> [value]

  get and set configuration parameters

  Options:

    -h, --help                   output usage information

(the number after line 14 is always different)

do you get the same results running wb config? could you copy the error stack trace if any?

No stack trace

Another example:
wd data Q1496 | jd labels.pt
/cygdrive/c/Users/vladimir.alexiev.000/AppData/Roaming/npm/wb: line 14:  2488 Segmentation fault      node "$basedir/node_modules/wikibase-cli/bin/wb" "$@"
{ language: 'pt', value: 'Fernão de Magalhães' }

@maxlath I don't get the segfault with wb config, only with wd config

@VladimirAlexiev so this is very likely to be an issue with the wd bash script

The implementation of wd is much simpler now (f575320), so I would expect this error to have disappeared. But the new implementation relies on environment variable, and I don't know how does behave on windows, please open a new issue if that's problematic

The implementation of wd is much simpler now (f575320), so I would expect this error to have disappeared. But the new implementation relies on environment variable, and I don't know how does behave on windows, please open a new issue if that's problematic


Correct Syntactical Errors in home.dart file

There are some syntactical errors in home.dart file due to which the project cannot be compiled.

I would like to work on this issue

Sorry , but i have corrected that in my latest PR along with the Issue i was working on. As i was not able to run the app


added register testing with 3 black box testing

Description
Fixes # (issue)
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] PEP8
[x] Test Model
[x] Commend Line Testing

Test Configuration:

System: windows10:
Python Environment: Python 3.9

Checklist:

[x] My code follows the style guidelines of this project which is PEP8 of python
[x] I have performed a self-review of my own code
[x] I have commented my code in every newly-added methods and classes, also in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings or error when it runs
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Great work on testing register function


offset replication factor based on desired brokers

What changes were proposed in this pull request?

Allow starting a 1 or 2 node Kafka Cluster without setting configurationOverrides.offsets.topic.replication.factor explicitely
confluent metrics topic is created successfully, when running with less than 3 brokers
Relates to #236

How was this patch tested?

Install with 1 broker: helm install --name cp . --set cp-zookeeper.servers=1 --set cp-kafka-rest.enabled=false --set cp-ksql-server.enabled=false --set cp-control-center.enabled=false --set cp-kafka.brokers=1  --set cp-kafka-connect.enabled=false --set cp-schema-registry.enabled=false
Check logs, that errors are gone

Just encountered this problem. Really important for dev and test environments.


Enable DIKSHA data sources for Jharkhand

To enable Diksha ETB and TPD For Jharkhand
Below are the required details :

Diksha API URL
API token
TPD encryption key
x_channel_id
TPD dataset name

We have successfully enabled the Jharkhand Diksha data source.we need to emit the batch_ids to the emission directory

Still Diksha URL is not accessible need to whitelisted

Completed issue is fixed


feat(python): add read_consistency_interval argument

This PR refactors how we handle read consistency: does the LanceTable class always pick up modifications to the table made by other instance or processes. Users have three options they can set at the connection level:

(Default) read_consistency_interval=None means it will not check at all. Users can call table.checkout_latest() to manually check for updates.
read_consistency_interval=timedelta(0) means always check for updates, giving strong read consistency.
read_consistency_interval=timedelta(seconds=20) means check for updates every 20 seconds. This is eventual consistency, a compromise between the two options above.

Table reference state
There is now an explicit difference between a LanceTable that tracks the current version and one that is fixed at a historical version. We now enforce that users cannot write if they have checked out an old version. They are instructed to call checkout_latest() before calling the write methods.
Since conn.open_table() doesn't have a parameter for version, users will only get fixed references if they call table.checkout().
The difference between these two can be seen in the repr: Table that are fixed at a particular version will have a version displayed in the repr. Otherwise, the version will not be shown.
>>> table
LanceTable(connection=..., name="my_table")
>>> table.checkout(1)
>>> table
LanceTable(connection=..., name="my_table", version=1)

I decided to not create different classes for these states, because I think we already have enough complexity with the Cloud vs OSS table references.
Based on #812

@wjones127 any more changes you're planning? Should we get this merged in?

@changhiskhan I think this is ready to go. I will merge this and then put up a PR to add Rust/Node changes as well as an entry in the docs about consistency.


Adopt SettingsNavItem UI component

Depends on https://github.com/containers/podman-desktop/issues/6908
See also https://github.com/containers/podman-desktop/issues/5757

Depends on https://github.com/containers/podman-desktop-extension-ai-lab/issues/1165

This component is not available on 1.10.3, we need to migrate to a more recent version (next) but this is probably subject to change


The theory behind the ML model isn’t covered in the docs

I’ve spent a bit of time today looking at SageMaker and trying to understand what model, where it came from, why its used, how data is fed, how it outputs results etc. Maybe a section in the docs on the ML model would help?

Issue is stale, closing


Adds async search API request and response examples

Overview
Related to https://github.com/elastic/elasticsearch-specification/issues/2482.
This PR adds request and response examples to the async search API.

I added a commit that appends overlays for the async_search.submit operation. I ran make overlay-docs then linted the output and it has the following warnings:

62541:27      warning  oas3-schema                 Property "method_request" is not expected to be here.                               components.examples.AsyncSearchSubmitRequestExample1.method_request
62543:17      warning  oas3-schema                 Property "type" is not expected to be here.                                         components.examples.AsyncSearchSubmitRequestExample1.type
62549:17      warning  oas3-schema                 Property "type" is not expected to be here.                                         components.examples.AsyncSearchSubmitResponseExample1.type
62550:26      warning  oas3-schema                 Property "response_code" is not expected to be here.                                components.examples.AsyncSearchSubmitResponseExample1.response_code

However when I preview the output in Bump.sh, the example showed up fine.


Add tests for server.ts

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

npm package (@latest dist-tag)
Visual Studio Marketplace
GitHub release

Your semantic-release bot :package::rocket:


Filter parsing for "or"'d filters

Retina compilation fails if a user specifies a filter with multiple application-layer protocols that have different L4 encapsulation (e.g., "quic or tls").
The check for valid layering using the protocol graph is meant to validate encapsulation (e.g., prevent the user from specifying "quic AND tls"), but it also blocks valid "or" conditions. Ideally the check would be fixed so that the former behavior is kept while the latter is fixed.

Fixed by multi-subscription


Fix definition of IMAGE_DYNAMIC_RELOCATION64

Fixes #261

That nightly failure is worrying, I'll dive deeper into it next week.
More info on STATUS_STACK_BUFFER_OVERRUN on The Old New Thing.


[Play] Web App name: Right On!

The name of the web app right now is displayed as Right On! on the iPhone Home Screen. This should be changed into RightOn!

Hi @cindyqquach, I've resolved this via: https://github.com/rightoneducation/righton-app/pull/657. The most recent version of the app will show this behaviour.


Better documentation

Subissues in comments

Improve README to have better summaries of all modules.

Consider adding screenshots of everything to README

Add a quick sumamry explanation "somewhere". Either in Bot or BBN server, as part of "How to use BBN and all assumptions we make" quick-learning

Related #38 : Read the docs for auto ReadME or sumamry or so


Mark messages as read on scroll, configurably

This Zulip feature: https://zulip.com/help/marking-messages-as-read#configure-whether-messages-are-automatically-marked-as-read
That means:

When scrolling through messages that are unread, by default mark them as read with a request to the server.
Control that behavior with a local setting "Mark messages as read on scroll", with three values: https://zulip.com/help/marking-messages-as-read#configure-whether-messages-are-automatically-marked-as-read
Unlike most everything else in the Zulip data model, apply "latency compensation" when marking messages as read on scroll, meaning eagerly apply the change to the local UI rather than wait for the server to acknowledge it with an event.

Specifically, eagerly fade out the unread-message markers in the message list.

That local setting should go in the app's database on the device, from #13.
This should come after:

#79
#80

Specifically, eagerly fade out the unread-message markers in the message list.

We might go further and eagerly update the model itself.

The zulip-mobile RN app doesn't do this; the consequence is that it looks kind of glitchy as the "N unreads" banner at the top of the message list doesn't update or disappear in sync with the unread markers.
I'm not actually sure what the web app does.
The downside is that if we eagerly update the model, then it's no longer part of a coherent snapshot together with the rest of our model — we'd be giving up some of the consistency provided by the Zulip event system.

There are a couple of approaches we could take to that consistency question, but we should think through the consequences. So, leaving that out of scope for this issue.

We've had a request for this as beta feedback: https://chat.zulip.org/#narrow/channel/48-mobile/topic/mobile.20beta.20feedback/near/2000430

And some more requests:

here's another vote for prioritizing "Mark messages as read on scroll" support in the Flutter app.

[…] FWIW this is the main reason why I have not switched to the beta app. I'm subscribed to all channels here, and the fact that I have to continually mark messages as read manually makes the beta app very tedious for me to use -- I am manually marking hundreds if not thousands of messages as read every day.


IDF-v4.4.5 build warning in esp_ptr_in_drom (IDFGH-10398)

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.

General issue report
a small bug has sneaked into the IDF v4.4.5, which leads to ugly warnings when building:
/esp-idf/components/soc/include/soc/soc_memory_types.h:140:25: warning: comparison of integer expressions of different signedness: 'intptr_t' {aka 'int'} and 'uint32_t' {aka 'unsigned int'} [-Wsign-compare]
     return ((intptr_t)p >= drom_start_addr && (intptr_t)p < SOC_DROM_HIGH);
             ~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~

Hello, @Andste82!
Thank you for sending the issue report. I was investigating this issue but unfortunately could not reproduce it on the ESP-IDF v4.4.5 tag.
We have suppressed all Wsign-compare warnings here - are you using any special C/CXX flags while compiling your example?

Hi @laukik-hase
thanks for you're response.
i use "vanilla" cmake in my projects because i don't like the "component magic" when using idf.py very well.
since the file with the warning is a header file, it is possible that my libs, with unsuppressed warnings, includes it.
i usually build my libs as follows:
target_compile_options(fancylib
	PRIVATE -Wall -Wextra -Wno-unused-parameter
)

the warning is not too bad, but since i want to handle every warning, and the headerfile is often included, the waning pops up very often during the build process.


[json] support $schema on descendant objects of root

I am working on an application with user created plugins. These plugins define their configuration as additional properties on the root object.
For example:
{
    "$schema": "./app-schema-v1.json",
    "some root schema properties": "and values here",
    "my-plugin": {
        "$schema": "./my-plugin-schema-v1.6.json",
        "some plugin specific properties": "and values here"
    }
}

It would be nice if VSCode supported this scenario rather than only supporting "$schema" on the root object.

@aeschli could we move this to https://github.com/microsoft/vscode-json-languageservice ? I have one day to go and don't want to spend it campaigning for upvotes (as I will likely implement this once I have the time).


sonoff ifan turns off and on by itself

sonoff-9285498fe27a57139f691eba6b56add1-iFan04 Study-0d4900d1628f5eea2aaecb9d5798dac6.json.txt
Hello. I have an ifan 03 and an ifan 04. Both in HA through HACS repository. I also have blocked internet access to them though Unifi router.
From time to time, when the light is on, it turns off and back on again immediately. This happens to both devices. Is it bcs I don't give them access to internet? All other Sonoff devices I have, don't do something like that.
Thank you!

I have the exact same problem with iFan04-H, but I’m using it with Homebridge and this plugin:
https://github.com/bwp91/homebridge-ewelink

This could be a problem with the RF433. Your neighbors probably have a device that sends similar commands to control the device. Terrible protocol. Terrible protocol. You could try resetting the binding to RF433 or solder out the singal receiver or flash custom firmware.


[RFQ] Listener Cancellation Fix

Workaround to be added and documented here prior to launch (#1650)
When an rpc returns an error in listener, the entire listener for that chain shuts off. This of course should not happen because

Would recommend investigating and fixing  through unit tests on listener. Scaffolding for this already exists, errors need only be mocked out

Investigating this now, you can see the dropoff here in doPoll requests to arbitrum:

The pod breaks at 10:13 and I reset as per @aureliusbtc at 10:23:

As you can see, omnirpc returns an error here:

Because this happens on block.number, we expect an error return here:

To debug this, I'm going to log pollInterval:

Okay, nevermind all that
I think if pollInterval is time.Millisecond (1,000) and we multiply by time.Second we get a lot of minutes. I'm not sure this explained why the thing stalled overnight, but it's worth a shot

Fixed


Real-time analysis YAML files should append, not overwrite

Currently, the real-time analysis YAML files overwrite the old ones if the job is resumed.
Instead, we should open the files to append.

The real-time analysis files are from openmmtools, I will move this issue over there


Adjust paths for non-Windows

Update commands that are joining paths to work on non-Windows machines. For example, Set-PSProjectStatus fails on Linux because of errors constructing paths.

Fixed in v0.14.0


Better check if record is active

Questions
Answers

Description?
Makes sure that some row has been found.

Type?
bug fix

BC breaks?
no

Deprecations?
no

Fixed ticket?
Fixes PrestaShop/Prestashop#34036

How to test?
Warning should be gone with this PR.

Ping @aniszr to test this.

@aniszr This only fixes "trying to access array offset on value of type null".
Also, you need to read what is the error. On your video, you show a completely new error message that is caused by either not running composer OR now clearing cache. ;-)

@hibatallahAouadni Again, this only fixes "trying to access array offset on value of type null".


Album starts dragging up when I want to crop image

Thanks for a great project!
In album view
After having dragged the album up once to reveal more images and then selected one, pinching to zoom/crop and panning the loaded image with one or two fingers would start the dragging up of the album, but the intended action is rather to pinch to zoom or pan the crop view.
Adding a class variable solved this issue
var canPanDuringThisTouch = true

Then add the line to the panned() function
    if sender.state == .Began {

        let view    = sender.view
        let loc     = sender.locationInView(view)
        let subview = view?.hitTest(loc, withEvent: nil)

        if subview == imageCropView && imageCropViewConstraintTop.constant == imageCropViewOriginalConstraintTop {
            // if the pan starts in the image field, don't let this touch start dragging the album, since it's a crop gesture
            canPanDuringThisTouch = false
            return
        }

and in the last } else { , add:
        canPanDuringThisTouch = true // reset this value for the next interaction

@thyselius what about creating a PR? If you don't have time, I'll do it :)

I made some other changes too so I won't do it right now. Should be incorporated by author since it's a bug, but go ahead and create a pr sounds good!

@thyselius Hi, I'm having the same issue. I don't see anywhere in your answer that you are checking the bool value to stop album from dragging up, how do you make that happen?

Hi, saw this comment now, sorry for the late reply
In the function panned(sender: UITapGestureRecognizer)
`
...
} else if sender.state == .Changed {
		if canPanDuringThisTouch == false {
			return
		}

		let currentPos = sender.locationInView(self)

...
`

@thyselius thank you so much!


Add option to mark dependencies as single use

A dependency marked as singleUse will only be added to the dependencies of the requesting task for the current build iteration.
This allows tasks to request other tasks for running once and not get invalidated for following incremental builds.
rdar://91494744

@swift-ci please smoke test

@swift-ci please smoke test


Migrate United States holidays to holiday groups and subdivision holidays methods

Proposed change

Migrate United States holidays to holiday_groups standard and subdivision holidays methods.
Type of change

[ ] New country/market holidays support (thank you!)
[ ] Supported country/market holidays update (calendar discrepancy fix, localization)
[x] Existing code/documentation/test/process quality improvement (best practice, cleanup, refactoring, optimization)
[ ] Dependency upgrade (version update)
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] Breaking change (a code change causing existing functionality to break)
[ ] New feature (new python-holidays functionality in general)

Checklist

[x] I've followed the contributing guidelines
[x] This PR is filed against beta branch of the repository
[x] This PR doesn't contain any merge conflicts and has clean commit history
[x] The code style looks good: make pre-commit
[x] All tests pass locally: make test, make tox (we strongly encourage adding tests to your code)
[x] The related documentation has been added/updated (check off the box for free if no updates is required)

coverage: 100.0%. remained the same when pulling b27d555ad6da4150eec832120299629071bab37a on KJhellico:ref-united-states into ddf111e0da55725bd013aa3fd141078a0816c4fb on dr-prodigy:beta.


Fix: maxOCP ordering and version format

Fix mis-ordering maxOCP for FBC
Remove "v" and quotes from all version references

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 5 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 0.888%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/actions/extract_index.go
0
5
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
18

Relevant Lines:
2028

💛  - Coveralls


Removed the top padding in the details block of the kits page #56

Issue #56

Sweet! Thanks @abdullahsalem

Looks good.


Select component allow other units in width, fix #46

@Mrpanquecas you did it bruh, good job! 🤟🏻

:tada: This PR is included in version 3.0.0-beta.1 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


add UI to display and update following job traits: cpu, mem, disk, prior...

...ity

New UI

Edit screen UI

Exposing some parameters via the UI

@elingg - can you review?

@mngo87, very nice! After these UI changes, we probably want to push out another release. I will look at this ASAP.

LGTM, any comments @brndnmtthws?

Looks great!

Nice work @mngo87!


UnexpectedQuit when using it with WSL

Please see the log:
Deploying to static website "/subscriptionsXXXXXXXXXXXXXXXXXXXX/providers/Microsoft.Storage/storageAccounts/acttaoglobal/$web"
Uploading from "/home/XXXXXXX/dev/XXXXXXXXX-website/dist" to "$web"
Could not transfer "/home/XXXXXXXX/dev/XXXXXXX-website/dist/"
Error: UnexpectedQuit
Uploading from "/home/chris/dev/acttaoglobal-website/dist" to "$web"
Could not transfer "/home/chris/dev/acttaoglobal-website/dist/"
Error: UnexpectedQuit

@kknddandy Does this consistently reproduce for you?
If so, what Linux distro are you running in WSL?

Hi, yes the problem is still there. My WSL is Ubuntu 20.04
On Fri, Mar 5, 2021 at 5:27 PM Will Lorey<EMAIL_ADDRESS>wrote:

@kknddandy https://github.com/kknddandy Does this consistently
reproduce for you?
If so, what Linux distro are you running in WSL?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode-azurestorage/issues/948#issuecomment-791810610,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFZO5OE24N3BR3XCP5R6FTLTCFZG3ANCNFSM4YQU3EVA
.

--
Chris
Boyu Zhang 张博昱
总裁 president
M:+86<PHONE_NUMBER>3 | +1<PHONE_NUMBER>
E<EMAIL_ADDRESS>W:www.acttao.com
Dublin | Beijing | Hong Kong | Tokyo | Calgary
ACTTAO Ecommerce LTD.

This issue also reproduces when downloading a file or folder from a blob container or file share on Remote-SSH.

My guess is this is AzCopy related

Can confirm reproducible in Ubuntu 20.04.
Only occurs in WSL 2. It was working correctly in WSL 1 before I upgraded to 2.

I am also receiving this issue when I am trying to 'Deploy to Static Website via Azure Storage'.
I am using VScode on WSL 2 (Ubuntu 20.04 LTS),
About > 'Visual Studio Code':
Version: 1.58.2 (user setup)
Commit: c3f126316369cd610563c75b1b1725e0679adfb3
Date: 2021-07-14T22:10:15.214Z
Electron: 12.0.13
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19043

This is almost definitely related to this Known Issue.
I'm not sure if there's anything we can really do for our users in this case. I haven't been able to figure out how we can prompt users sudo commands on WSL. This can be mitigated by installing libsecret-1-0 though.
I suppose we can check beforehand if they have it installed and let them know it will fail ahead of time, but on failure, we do show this message: View help with [known issues](https://aka.ms/AAb0i6o). only on Linux.

Seems like someone found a fix for it in https://github.com/Azure/azure-storage-azcopy/issues/1297. That fix might be be usable by us though.


Create README-Korean.md

README-Korean.md is README.md file translated into Korean.
If there are any mistakes or requirements in this pull request process, please let me know. I'll fix it as soon as possible.
Thank you!!

Thank you, I appreciate you putting the time into this.
Can you rename the file to README_ko.md?

Sure! I changed the name of README.md file translated into Korean according to your request. Please check it again.

Thank you for this pull request! Going to merge it in now. Since I don't speak Korean, I won't be able to maintain the file but if you want to periodically check in and update it, that would be great!

Closes #138


[collab-galley] Introduce pkg/config/source/kube/apiserver

Adding the Kube based source for getting config from the API Server.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: ozevren
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

galley/OWNERS [ozevren]

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

@ozevren: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-mixer-k8s-presubmit-tests.sh
c3fe5b9597a40261c431694a9ec7440983a4e55b
link
/test integ-mixer-k8s-presubmit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ozevren: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-mixer-k8s-presubmit-tests.sh
c3fe5b9597a40261c431694a9ec7440983a4e55b
link
/test integ-mixer-k8s-presubmit-tests

prow/integ-security-k8s-presubmit-tests.sh
c3fe5b9597a40261c431694a9ec7440983a4e55b
link
/test integ-security-k8s-presubmit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ozevren: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-mixer-k8s-presubmit-tests.sh
c3fe5b9597a40261c431694a9ec7440983a4e55b
link
/test integ-mixer-k8s-presubmit-tests

prow/integ-security-k8s-presubmit-tests.sh
c3fe5b9597a40261c431694a9ec7440983a4e55b
link
/test integ-security-k8s-presubmit-tests

prow/e2e-simpleTests.sh
b1bd803e8f681c918fb6df35fc16b8875db078a8
link
/test e2e-simpleTests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ozevren: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-security-k8s-presubmit-tests.sh
c3fe5b9597a40261c431694a9ec7440983a4e55b
link
/test integ-security-k8s-presubmit-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
1879e65d4027c17be0afbc9cd8d47ff16b2e4cda
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ozevren: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-security-k8s-presubmit-tests.sh
c3fe5b9597a40261c431694a9ec7440983a4e55b
link
/test integ-security-k8s-presubmit-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
1879e65d4027c17be0afbc9cd8d47ff16b2e4cda
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
1879e65d4027c17be0afbc9cd8d47ff16b2e4cda
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-pilot-e2e-envoyv2-v1alpha3

@ozevren: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-security-k8s-presubmit-tests.sh
1d304d5088cf86b528e61db43ffb0a0bc4333e85
link
/test integ-security-k8s-presubmit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: nmittler, ozevren
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

galley/OWNERS [ozevren]

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


extract features from the ROI

Hi,
I want to ask, after the Fcos detector obtains the results of Bboxes, how does the ResNet-34 network extract features from the ROI region of interest（e.g. ape）? Is this implemented by the pre-trained model in the pretrained_backbone folder?
Best,
Joa

Hi Joa,
The dataloader will use the bounding box to extract the ROI, as implemented in #bop_dataset_pytorch.py,
You just need to provide the path of the JSON file, which stores all bounding boxes, to the config file.
Best,
Yongzhi

I have already understood the code now, thank for your enthusiastic respons3 ^_^


Docstrings for contributor-count and deprecation-helpers services

Added docstrings for contributor-count service
Added docstrings for deprecation-helpers service

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @pr7prashant!

  Generated by :no_entry_sign: dangerJS against f49e713ef8487342eecf409a57263dbdc673bb5d


Add better support for bootstrap horizontal form

I wrapped the form element, along with its hint and error
messages with a div.field-content.
This provides separation of the label of the element from the
actual input element, which is necessary in order to have a proper
horizontal form design.
In bootstrap v4 horizontal forms, we have the label on the left hand side,
and the input element (along with accompanying content like hints
below it and validation messages) floated to the right.
Without wrapping the field in a div, the content under the input
would not be properly aligned with the input itself if the input
is offset from the left-most border of it's parent. This means
that horizontal forms wouldn't work well.
I decided to add another div instead of moving the hint and error
messages into the div.field-wrap because I think there might still
be use-cases where you would want to have a separate parent for the
field-element.
The inserted div shouldn't affect styling, since in css it can be defined
as block, flex, inline, inline-block e.t.c to the users needs.

Please check if the PR fulfills these requirements

[ ] The commit message follows our guidelines
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

What is the current behavior? (You can also link to an open issue here)

What is the new behavior (if this is a feature change)?

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

Other information:

Coverage remained the same at 73.92% when pulling 8fe0be59ae72434aaabb84e2fc68f54b805e263a on muschottkey:v3-better-support-for-bootstrap-horizontal-form into 218bababcdb4dced2fb439d6f6644c23afbf2d16 on vue-generators:v3.

Is it possible to achive like below pics, i have tried many way but didnt get any solutions, pls help to completed this.
Under input box i have place hint, if valid it should always grey, if there have any errors need change it as red.

Thanks,
Gopal R


[0.4 Release]Add Pytorch-based TextPredictor & Experimental AutoMMPredictor

This PR implements the Pytorch-based multimodal predictors: TextPredictor and AutoMMPredictor (experimental)
Pytorch-based TextPredictor

Better performance than the MXNet-based TextPredictor. (Average score 0.672 vs. 0.66411 in the multimodal benchmark paper https://arxiv.org/pdf/2111.02705.pdf)
Faster training and inference. The new version has ~2.88x speedup in training and ~1.40x speedup in inference. With g4dn.12x instance, the model can further achieve 2.26x speedup with 4 GPUs.
Support multilingual models for zero-shot cross lingual transfer. This includes XLM-R and mdeberta-v3 (https://arxiv.org/abs/2111.09543).
Support backbones in Huggingface/Transformers, such as deberta-v3, roberta, electra-base and gpt2.
Half-precision training (less memory and faster training).

AutoMMPredictor

Flexible late-fusion for any combinations of single and multimodal models.
Support HuggingFace auto models (https://github.com/huggingface/transformers).
Support TIMM image auto models (https://github.com/rwightman/pytorch-image-models).
A general pytorch data loader system that can simultaneously load data for multiple models.
A scalable and easy-to-use configuration design with templates provided. Users can flexibly switch backbones by overriding the checkpoint_name hyper-parameter.
Support finetuning with CLIP.
Automatic GPU selection.

@Innixma @jwmueller @gradientsky @yinweisu The logic can be reviewed first while we are fixing the test + add more comments +  fix the tutorials.

Job PR-1537-15 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-1537/15/index.html

Job PR-1537-16 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-1537/16/index.html

Just a personal suggestion, but I would rename AutoMMPredictor to something more meaningful like MultimodalNetworkPredictor and in the file-paths/names would also change automm to something like multimodalnet

@jwmueller Regarding the naming, would you think that AutoMM is a good umbrella name for what we are doing about deep learning + multimodal data tables + AutoML?

Job PR-1537-17 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-1537/17/index.html

@jwmueller Regarding the naming, would you think that AutoMM is a good umbrella name for what we are doing about deep learning + multimodal data tables + AutoML?

Ya I do think AutoMM is a good name as long as there's a paper/blog describing the AutoMM model. Otherwise from the code alone this name seems too vague without being formally introduced in some writeup.

@jwmueller We may adopt the code name and write a paper about that later (potentially along with 0.5 release).

Job PR-1537-18 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-1537/18/index.html

Have one minor comment. Once fixed, the PR looks good to me.

Job PR-1537-24 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-1537/24/index.html

Job PR-1537-25 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-1537/25/index.html

+1 to @Innixma comment; open PR questions/discussions should be resolved in the follow-up PRs (tracking doc is created)


Migrated M2M to more generic handling

@DanielJMaher Looks fine to me.

I just hit a bug in this code, I'll need to push a fix shortly.

@petercable I didn't even manage to get it onto the test server yet.  can you add back in the GA when you push the fix?


Update SLSC Switch scripting API to refresh the list of possible connections

[x] This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?

Rename the load and autodetect VIs to match the new proposed names.
Update topology and endpoint configuration accessors to refresh the list of possible connections.
Update the examples to use the new entrypoints, fixes #69.
Update Add SLSC Switch Custom Device to call the initialization logic for the custom device.

Why should this Pull Request be merged?
It makes the scripting API maintain a consistent internal state when changing the topology or endpoint configuration. This brings us closer to the proposed palettes, with a few minor renames and additions remaining.
What testing has been done?
Added new unit tests. Ran examples and confirmed output.

[ ] Make Create All Endpoints as Load.vi and Refresh Possible Connections.vi private utilities. With all the utility private, you can just mark Utility folder as private and remove private virtual folder.

[ ] Update comment to read configuration from the module, not the JSON.


Fix argument order for invoke and manage commands

Description
The invoke and manage commands now work correctly
when flags like --raw and --all are specified after
the management command or function to invoke.
GitHub Issues
#564

Coverage increased (+0.04%) to 80.823% when pulling 1e35aba1c0d9047a0152c2c8242b7054148bd9ef on rmoe:arg-ordering into 27272d75d9d701e18222e18eb8eb8399e1f13620 on Miserlou:master.

Yay :)


staging: sdk.nft.createCollection succeeds but collection not available on rinkeby.rarible.com

This used to work but no longer.
create collection with:
params= {
"blockchain": "POLYGON",
"asset": {
"assetType": "ERC721",
"arguments": {
"name": "testpoly1",
"symbol": "testpoly1",
"baseURI": "https://ipfs.rarible.com",
"contractURI": "https://ipfs.rarible.com",
"isUserToken": true,
"operators": []
}
}
}
sdk.nft.createCollection(params)
result: {
"tx": {
"transaction": {
"receipt": {},
"hash": "0xe62633eea5a9add246f5a43b2d40ce34bfc2a680a9362b552687d7d85009fddb",
"data": "0x27050d1f00000000000000000000000000000000000000000000000000000000000000c000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000140000000000000000000000000000000000000000000000000000000000000018000000000000000000000000000000000000000000000000000000000000001c02a16e53a84bbf0100af4b75e8a06f44985b5cda5dc99e6a70e6ee3b8b5cd048b000000000000000000000000000000000000000000000000000000000000000974657374706f6c79310000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000974657374706f6c79310000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001868747470733a2f2f697066732e72617269626c652e636f6d0000000000000000000000000000000000000000000000000000000000000000000000000000001868747470733a2f2f697066732e72617269626c652e636f6d00000000000000000000000000000000000000000000000000000000000000000000000000000000",
"nonce": 561,
"from": "0x497f9faea098e12613ace222dcdca0cf91332c63",
"to": "0xa85180a21786ba65b0778be1cb5cba5e5c6cd21d"
},
"network": "mumbai",
"blockchain": "POLYGON"
},
"address": "POLYGON:0xFDCBC4c241140B39A9e0D0410b0Da05c9BC52fd2"
}
subsequently call:
https://api-staging.rarible.org/v0.1/collections/POLYGON%3A0xFDCBC4c241140B39A9e0D0410b0Da05c9BC52fd2
result: {"code":"NOT_FOUND","message":"Collection with id 0xfdcbc4c241140b39a9e0d0410b0da05c9bc52fd2 not found"}
Note the above call is also made by sdk.nft.mint(), which also fails.
collection also does not appear in collection list of owner.
ALSO. atttempting to create the collection manually on rinkeby.rarible.com spins after wallet signing with screen:
Follow steps
Deploy contract
Deploy code for the new collection smart contract
Please advise.
Thanks!
Victor

This is also occurs for Tezos:
create collection succeeds:
{
"tx": {
"transaction": {
"hash": "op4uKYT6CS828mKwqsR18kaEMUKZJEtU5dYWYsnkQA9gGePZybH",
"contract": "KT1KXPEjohRgZ6G5Kz2zkgqapVRpmnRVtAXX"
},
"network": "hangzhou",
"blockchain": "TEZOS"
},
"address": "TEZOS:KT1KXPEjohRgZ6G5Kz2zkgqapVRpmnRVtAXX"
}
https://test-tezos-api.rarible.org/v0.1/collections/KT1KXPEjohRgZ6G5Kz2zkgqapVRpmnRVtAXX - reports not found.
packages installed:
"@rarible/connector": "^0.8.52-beta17",
"@rarible/ethers-ethereum": "^0.12.64",
"@rarible/sdk": "^0.8.52-beta17",
"@rarible/sdk-wallet": "^0.8.52-beta17",
"@rarible/sdk-wallet-connector": "^0.8.6-alpha.4",
"@rarible/types": "^0.9.3",
"@rarible/web3-ethereum": "^0.12.64",

i am also get same issue ( after creation collection not found )
but not all times
occasionaly occurs

Indexing of new collections can take some time


Can't find this in chrome web store

I had used this extension very well. I recently reset my Windows, and all of my chrome extensions are disappeared. I wanna reinstall this extension, but I couldn't find it in chrome webstore. I wonder if this program doesn't service anymore.

Thank you for your comment. The project is discontinued. You can manually install the extension by entering developer mode and uploading the attachment.


bump the embedded k3s version to 1.25.5

Issue:

https://github.com/rancher/rancher/issues/39960
Problem

Solution

Testing

Engineering Testing
Manual Testing

Automated Testing

QA Testing Considerations

Regressions Considerations

Please fix the failures in the Drone CI.

fixed ci issues. removed unnecessary files as per release notes https://github.com/k3s-io/k3s/releases/tag/v1.25.5%2Bk3s1
@jiaqiluo


Using codehilite with Pygments doesn't place code blocks inside code elements

I'm using Python-Markdown 2.6.5 and Pygments 2.0.2 as installed from PyPI.
With Pygments installed:
>>> text = """
...     :::python
...     import foo
... """
>>> markdown.markdown(text, extensions=['codehilite'])
u'

import foo\n

'

Presentation works OK in this case, but I'd expect  tags to be present too to correctly indicate the semantics of the content.
Without Pygments installed, the behaviour's more what I would expect as the code is content that forms part of a  element:
>>> text = """
...     :::python
...     import foo
... """
>>> markdown.markdown(text, extensions=['codehilite'])
'
import foo
'

Can see in the codehilite code that if Pygments is unavailable, code tags are added, but no similar thing is done when Pygments is used.

While I understand your concern, Pygments does not offer support for wrapping the code in code tags. Therefore, we don't either. We just use whatever Pygments returns. If you want to address this upstream (with Pygments), I would be happy to support it. But this is not something that we can do on this end.

Thanks for the quick reply; I wasn't sure if you'd consider it a Pygments problem or not.
For anyone else who happens to read this, there's a stale pull request on Pygments here to address this.

Pygments recently added the wrapcode option for wrapping code in code tags: https://bitbucket.org/birkenfeld/pygments-main/commits/9ac63688129f98b8b1c2e320d6ea8f701ef185d1.
Can this option be set by default or should a codehilite option be added for it?

@pauloue thanks for the update. Note that this issue falls under #334 which covers a general refactor to support all Pygments options.

Please see #822 for an initial attempt at implementing #334.


Clean task added.

Issue fixed: https://github.com/WASdev/ci.ant/issues/26
Added a class that performs 5 types of cleaning:

Remove all the logs in the serverOutputDir and its subdirectories.
Remove all the files in the dropins folder.
Remove all the files in the apps folder.
Remove all the files in the serverOutputDir/workare folder.
Perform all of the above.

Changes to README:

Added the description of the clean task
Added some examples

Changes to IT build.xml:

Added a clean task.of type "all"

General changes:

Added a class for the clean task
Added some error and info messages

A few comments:

Seems like cleanDir and deleteDir seems exactly the same. Should be able to remove one.
Why only delete .log files from the logs directory?
Instead of passing type with a single value, I would change the task to take 4 attributes. Something like:

<wlp:clean dropins="true" logs="true" apps="false" workarea="true"/>

logs and workarea would default to true, while dropins and apps would default to false.

Thanks for the feedback, it's a great idea having these 4 attributes, I'm going to work on that, and yes, the cleanDir and deleteDir do the same, I missed that. Thanks again!

Looks great. Thanks!


Add functionality to schedule automated jobs via the portal

Requirements:

[ ] Centry Portal should send an the schedule to Centry Add-on
[x] Centry Add-on should store the schedule in the database, e.g. the cron expession and an array of job handles
[ ] A custom command should handle the schedules

Example of an incoming schedule:
[
  {
    "cron_expression": "1 * * * *",
    "job_handles": [
      "index_search",
      "generate_sitemap"
    ]
  }
]

Run schedules via CLI command: centry:run-schedules

This feature is now fully implemented. 🎉


Extension instance vs static member conflict

The following code works in CFE but produces an error in the analyzer
class A {}

extension Ext1 on A {
  int foo() => 1;
}

extension Ext2 on A {
  static int foo() => 2;
}

main() {
  print(() {A().foo();}); // Analyzer error (see below)
  print(() {Ext2.foo();});
}

The error is
  error • test.dart:26:25 • A member named 'foo' is defined in extension 'Ext1' and extension 'Ext2', and none are more
          specific. Try using an extension override to specify the extension you want to be chosen. • ambiguous_extension_member_access

Which tool is right and which tool is wrong here?
Dart SDK version: 3.5.0-edge.cf7a697aa50952378395957cb8c8957f291e9456 (main) (Sat May 25 05:31:18 2024 +0000) on "linux_x64"

A().foo() can not invoke a static member of Ext2 and no ambiguity should be reported.

Oh, I misread: It's the analyzer that reports the wrong error, I thought it was the CFE. Adjusting again. ;-)


Deal with undefined errors_outside_of_examples_count

This pull request has two motivations:

Protect SummaryNotification inner state against user misuse
Back compatibility.

Hello
Thanks for your proposal.
Do you can provide a test that express "Protect SummaryNotification inner state against user misuse"?
Cheers 👋

I'd like to see a spec for the cause of this, we're not generally in favour of adding protection against people meddling with the internals (defensive coding) unless they can happen for legitimate reasons.

Please ignore this pull request: a more thorough analysis of the case which motivated it showed the problem was generated by a misuse of SummaryNotification by an outdated gem.

Thanks for letting us know


⚠ DesiTorrents has degraded performance

In 9d75b85, DesiTorrents ($DST) experienced degraded performance:

HTTP code: 200
Response time: 1952 ms

Resolved: DesiTorrents performance has improved in af23114.


Correction in convert_engine with unknown exif orientation

My mistake, I should have realized it when this import became unused.


Can't parse XMLs containing BOM characters

Hello. Thank you for this library, I've been using it on some of my projects and I find it very useful!
Today I found out that when I try to parse XML strings, fetched from an API starting with either the \u FEFF or the \u FFFF, the JSON returned is empty.
Is there a way to parse such XML strings, without the obvious workaround xmlString.replace(Regex("[\uFEFF-\uFFFF]"), "") and using that as input to the XmlToJson? I think this should be implemented inside the library, since it can be very difficult to try and debug it, since those characters are not visible in the Strings. I spent some hours trying to pinpoint what was wrong with my input not getting parsed correctly. Thank you!

You may add removeBom() method.
    private static byte[] removeBom(byte[] bytes) {
        if ((bytes.length >= 3) && (bytes[0] == -17) && (bytes[1] == -69) && (bytes[2] == -65)) {
            return Arrays.copyOfRange(bytes, 3, bytes.length);
        }
        if ((bytes.length >= 2) && (bytes[0] == -1) && (bytes[1] == -2)) {
            return Arrays.copyOfRange(bytes, 2, bytes.length);
        }
        if ((bytes.length >= 2) && (bytes[0] == -2) && (bytes[1] == -1)) {
            return Arrays.copyOfRange(bytes, 2, bytes.length);
        }
        return bytes;
    }

hello Lucas @L4grange and Valentyn @javadev !
thanks for using XmlToJson :)
the bom characters are a little obscure to me, and this seem to be a very specific problem. The proposed solution certainly works in this case, but is not veryt generic.
I was wondering if there could be a wider solution for special characters like bom, or if this should be fixed outside of the library (before using it).
what do you think?

Thank you for your reply @smart-fun !
Before facing this problem I had never worked with BOM characters before. However, since they are not visible and easy to catch, and they do exist in some XMLs with deprecated formatting, I think it would be good for this library to handle XMLs with or without BOM characters.
As for a more generalised solution, I agree, but I haven't found any other whitespace characters that were breaking the parsing. If you have an example of other characters, we could look for such a solution.

I found bom bytes for xml with encoding UTF-16 and UTF-32.

Some entry points about BOM characters:
https://stackoverflow.com/questions/1772321/what-is-xml-bom-and-how-do-i-detect-it
https://stackoverflow.com/questions/499010/java-how-to-determine-the-correct-charset-encoding-of-a-stream/499033#499033
https://docs.oracle.com/javase/7/docs/api/java/io/InputStreamReader.html#getEncoding()
https://www.xponentsoftware.com/articles/Byte_order_mark.aspx
Is it possible for one of you to attach to this issue a XML file containing BOM characters?

@smart-fun I think the XML I've posted on https://github.com/smart-fun/XmlToJson/issues/20#issuecomment-542203816 contains BOM characters, as I was not able to parse it.

@L4grange I found usual xml without BOM. http://prntscr.com/qlp122

I found an example.
itemdescription_20140527014836.xml.zip

It seems there is a generic solution using pache BOMInputStream. I gave it some try, but no success so far and not much time to try.
https://commons.apache.org/proper/commons-io/javadocs/api-2.5/org/apache/commons/io/input/BOMInputStream.html
https://commons.apache.org/proper/commons-io/
tested things like:
BOMInputStream bim = new BOMInputStream(inputStream, false);

if (bim.hasBOM()) {
        bim.skip(bim.getBOM().length());
}


prevent ipv6 dns lookups

⚠ Please verify that this question has NOT been raised before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

📝 Describe your problem
My instance (running as a docker container) is performing IPv6 (AAAA record) queries each time it performs DNS lookup (in addition to IPv4 A record lookup). This is not an issue in and of itself, but it does clobber my pi-hole logs...
Apparently, I am on a quest to remove as much IPv6 traffic from my network as possible.
I've verified IPv6 is disabled on the container, and played a bit with its resolve.conf - alas, no progress:
nameserver <IP_ADDRESS>
nameserver <IP_ADDRESS>
options ndots:0
options  single-request

Anyone knows how to prevent such queries?
Thanks!
📝 Error Message(s) or Log
No response
🐻 Uptime-Kuma Version
1.23.11
💻 Operating System and Arch
Linux uptime-kuma 4.4.302+
🌐 Browser
Chrome 131.0.6778.110
🖥 Deployment Environment

Runtime: Docker version 20.10.23, build 876964a / Synology DSM 7
Database:
Filesystem used to store the database on:
number of monitors: ~30

Anyone knows how to prevent such queries?

That is not currently a feature we offer.
Lets track this in the other issues instead:

https://github.com/louislam/uptime-kuma/issues/1242
https://github.com/louislam/uptime-kuma/issues/1025


RunAsPrompt() doesn't validate the login

The dialog for asking the user and password during service installation doesn't validate if the login is right or wrong. Only validate if the passwords are the same.
Is that behaviour intentional?

But could it be some improvement for the library? I would love to have this, but I don't have the knowledge for making this and put a PR on this repo.

But could it be some improvement for the library? I would love to have this, but I don't have the knowledge for making this and put a PR on this repo.

The prompt validation is to make sure you are entering the same password, the password is not passed to windows authentication, so that is why it doesn't check, and it wouldn't be something topshelf could do directly.

Fine. I will close this issue as it's a feature that won't be done.


Scroll

Disabled scrolling in the body when file-explorer is opened. Re-enabled when the file-explorer is closed.

Thanks Joeson! I do think that this goes well when done together with https://github.com/Kloudless/file-explorer/pull/28/files since the body won't scroll when not visible. Let's add it to that PR?


Allow users to provide an already minted ca-cert

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
FEATURE REQUEST

Environment:

Cloud provider or hardware configuration:
Virtual Machines on VMware
OS (printf "$(uname -srm)\n$(cat /etc/os-release)\n"):
CentOS 7
Version of Ansible (ansible --version):
2.3.0

Kargo version (commit) (git rev-parse --short HEAD):
6ac1c1c
Network plugin used:
calico
I'd like to be able to provide kargo with an already minted ca-cert and key, the proposal would be to introduce a new variable that tells kargo we intend to use an existant ca, and perhaps another variable with either the contents of the file, or path to the file to copy up before running make-ssl.sh

kube-apiserver's --client-ca-file argument should accept a file with multiple CAs. I've never tried it myself, but it should be possible to merge in CAs taken as user input without greatly impacting kargo's existing cert generation.
Would we want to support multiple CAs with this as well?

Do you know if kube-apiserver needs knowledge of they keys as well? my current testing branch has the following
kube_ca_cert:
  cert: /path/to/cert
  key: /path/to/key

we could easily change that to
kube_ca_certs:
  - cert: /path/to/cert/1
     key: /paht/to/key/1
  - cert: /path/to/cert/2
     key: /path/to/key/2

If we determine it's worthwhile to support multiple CAs I can work on that, too

I think multiple CAs would be worthwhile. It would be helpful for clusters that have already been provisioned.

I've not been able to make any positive progress on this since opening the issue. i think i'm overlooking something small, but when i provide a cert into /etc/kubernetes/ssl/ca.pem and /etc/kubernetes/ssl/ca-key.pem the apiserver refuses to start. when i blow away /etc/kubernetes/ssl and run the script again, the apiserver starts.
I'm unable to start the apiserver by hand, too -- i'm not seeing anything meaningful being logged. my current guess is that there is a failed conditional in the kubernetes/secrets role when the cert exists, and is failing to do a critical step in the subsequent tasks. walking these tasks will take time and i'm not sure i have that much time to devote.