Update split to v1.2.1

Major Changes

Bump split gem to v1.2.1

Minor Changes

Adds NotImplementedError to Configuration#report to communicate intention
Remove MIT licence
Cleanup README.md

Links

Wimdu: Bump split to v1.2.1

Except for the unrelated and perhaps uncalled-for licence cleanup, this looks good.

TravisCI setup and badge added :)

Awesome :+1:

@iGEL Thanks for your comment. Just missed this is a public repo. So removing licence is not needed :)


[New Website] Set up Matomo (an alternative to Google Analytics)

Comments from @dave2wave:
Google Analytics are no longer allowed on ASF websites due to privacy concerns. See https://privacy.apache.org/policies/website-policy.html
This is a new policy. The privacy committee has setup an alternative Matomo service - https://privacy.apache.org/matomo/
🔹🔹🔹🔹🔹🔹
Comments from @Anonymitaet:
Currently, Pulsar is using Google Universal Analytics. Google Universal Analytics will no longer process new data in standard properties beginning July 1, 2023. Organizations that use Google Universal Analytics need to switch over to a Google Analytics 4 property.
If we make a consensus on migrating from Google Universal Analytics to Matomoto, we do not need to do that switchover.
Since GA is much more powerful than Matomo, may we keep both GA and Matomo for now?
GA will expire next year, we'll only use Matomo them.

@Anonymitaet

How does Google Analytics 4 property fix the PII issues with GA? Nothing on that link you provided indicates any improvements.
Here is what Google has about GDPR - https://support.google.com/analytics/answer/6366371?hl=en#zippy=%2Cin-this-article
The ASF has taken several years to address GDPR and this issue should be fully decided by the Foundation in one month. This is being done to protect the Foundation. This will become a hard policy of the ASF - No Google Analytics.

I'm going to send an email to<EMAIL_ADDRESS>asking for a site ID and integrating the website with the Matomo service.
In the first place, we keep the Google Analytics settings until it's forcibly forbidden by the ASF or we're confident that the Matomo solution has completed replace.

FYI @urfreespace


Understanding RC_Driver and thinking behind your approach.

Thank you for this fantastic project, I've been working to replicate something similar and add addition functionality and have been learning supervised machine learning on the go.
Just to test my understanding.

so we've collected our data (frames and assigned them keyboard inputs)
we reshape and process this data into our neural net
the neural is trained to make predictions and outputs 1 2 3 for driving and steering.

Coud you explain this part of the code
I'm not clear on how the .getTickCount() is used to generate predictions from the MLP.
create MLP
layer_sizes = np.int32([38400, 32, 4])
model = cv2.ANN_MLP()
model.create(layer_sizes)
model.load('mlp_xml/mlp.xml')
generate predictions
e0 = cv2.getTickCount()
ret, resp = model.predict(test)
prediction = resp.argmax(-1)
e00 = cv2.getTickCount()
time0 = (e00 - e0)/cv2.getTickFrequency()
print 'Prediction time per frame:', time0/(test.shape[0])`
On the actual RC_Driver.py file
I want to understand your approach on how you were able to use the trained MLP to drive the vehicle.
if i put this this trained model onto a new track how does it different a left tun from a right turn?
My understanding it the model has been trained to look at each frame and predict forward left or right based on the frame it sees.
I'd like to understand how your thinking how you added the stop sign classifiers to an already trained neural net.
Thanks for your time !
James

.getTickCount() is a OpenCV function, just used to calculate the time or duration. You could also use built-in Python time.time() to do the calculation as well.
After the training, the weights/parameters of the network are saved. In prediction, the weights are loaded and the network generates a prediction based on that. Basically, the purpose of training is to find the proper weights that minimize the cost.
Your understanding is correct, of course, the track can vary but should be in a similar pattern.
Stop sign and the neural net are different classifiers, they are not conflicting with each other.

I am getting this error. "F:/SDC CAR Project/AutoRCCar-1-aleonnet-stand-alone/computer/mlp_predict_test.py", line 38, in
prediction = resp.argmax(-1)
AttributeError: 'NoneType' object has no attribute 'argmax' any help? @coeshack @hamuchiwa

It is probably because your predict() returned None


Manual sync

Automatic sync creates too much commits on GitLab backed workspace.
There should be an option to disable autosave.

There is. Set autoSyncEvery: 99999999 in the settings.

@benweet How does syncing work?
If there was a manual sync, does it reset the auto sync timer?
Does it detect e.g. sentences, or commas, or it can sync even a half word while continuously typing?


[doc] Update README

I updated the README in regards with the requirements for running the unit tests.

Codecov Report

Merging #2294 (d9369d9) into master (3857bad) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head d9369d9 differs from pull request most recent head 27a01ca. Consider uploading reports for the commit 27a01ca to get more accurate results

@@           Coverage Diff           @@
##           master    #2294   +/-   ##
=======================================
  Coverage   86.12%   86.12%
=======================================
  Files          56       56
  Lines       10208    10208
=======================================
  Hits         8792     8792
  Misses       1416     1416

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 3857bad...27a01ca. Read the comment docs.


[FLINK-17028][hbase] Introduce a new HBase connector with new property keys

What is the purpose of the change
Add new hbase connector implementation which uses new interfaces proposed by FLIP-95, e.g. DynamicTableSource, DynamicTableSink, and Factory.
Brief change log

New HBaseDynamicTableSource and new HBaseDynamicTableSink.
New HBaseDynamicTableFactory which uses new connector options proposed by FLIP-122.
We reuses the implementation of HBaseLookupFunction.
Added HBaseSerde to support runtime conversion between RowData and HBase mutation.

Verifying this change

Added HBaseDynamicTableFactory to unit test factory
Added new connector test in HBaseConnectorITCase

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Resolve conflicts and address comments.

Added validate() and tests

The failed case is KafkaProducerTestBase.testExactlyOnce which is a known issue.
Merging this one...


Serial install of 16.7 fails on APU2 board

Hey,
I'm trying to install OPNsense 16.7 from an USB stick on an APU2c4 [1] via serial console, which fails with this error message:
Trying to mount root from ufs:/dev/ufs/OPNsense_Install [ro,noatime]...
mountroot: waiting for device /dev/ufs/OPNsense_Install ...
Mounting from ufs:/dev/ufs/OPNsense_Install failed with error 19.

Loader variables:
  vfs.root.mountfrom=ufs:/dev/ufs/OPNsense_Install
  vfs.root.mountfrom.options=ro,noatime

Manual root filesystem specification:
  <fstype>:<device> [options]
      Mount <device> using filesystem <fstype>
      and with the specified (optional) option list.

    eg. ufs:/dev/da0s1a
        zfs:tank
        cd9660:/dev/acd0 ro
          (which is equivalent to: mount -t cd9660 -o ro /dev/acd0 /)

  ?               List valid disk boot devices
  .               Yield 1 second (for background tasks)
  <empty line>    Abort manual input

mountroot> reboot
Invalid file system specification.

mountroot> ufs:/dev/ufs/OPNsense_Install
Trying to mount root from ufs:/dev/ufs/OPNsense_Install []...
Mounting from ufs:/dev/ufs/OPNsense_Install failed with error 2: unknown file system.

mountroot>

Some more details:
I'm using OPNsense-16.7-OpenSSL-serial-amd64.img.bz2 and sha256 sum matches.
Screen version 4.03.01 (GNU)  is invoked with /dev/ttyS0 115200
APU2s Bios versions is 20160307
It doesn't seem related, but to give you an overall picture:
there is an other issue with disordered output, which can be fixed with set console=comconsole.
Cheers
Woi
[1] http://pcengines.ch/apu2c2.htm

Hi Woi,
From the boot loader prompt (3) try:
set kern.cam.boot_delay="10000"
boot

I've seen the disordered output on a APU2C2 this week, didn't know that setting it to single console fixes this. I want to revise images and serial mode soon, this will probably be the new default, thanks!
Cheers,
Franco

Hey fitcherner,
thanks for the quick reply :-). I just managed to boot in to the installer the very same moment you answered  by following this blog post: https://randomproblem.wordpress.com/2016/03/31/installing-opnsense-16-1-on-pc-engines-apu2/
The same guy also blogged about the disordered output: https://randomproblem.wordpress.com/2016/05/15/installing-freebsd-via-a-serial-port/

Regarding the disordered output, I stumbled over this thread:
https://www.coreboot.org/pipermail/coreboot/2016-June/081542.html which  leads to this commit:
https://github.com/pcengines/seabios/commit/d161aaf84d4f71d93599f2ab72508095da7d30d2
So this behaviour might be a BIOS issue.
Since you marked this bug for milestone 17.1, I like to suggest to document both issues along with there workarounds for the current release. This is to improve user experience and save APU2 owners some time finding a solution on there own.
Thanks for OPNsense and your support :)


Unclear and contradictory information about filesystem layout on kubelet nodes

Hello,
According to [1] https://kubernetes.io/docs/tasks/administer-cluster/out-of-resource/#eviction-signals
kubelet supports only two filesystem partitions.

    The nodefs filesystem that kubelet uses for volumes, daemon logs, etc.
    The imagefs filesystem that container runtimes uses for storing images and container writable layers.

imagefs is optional. kubelet auto-discovers these filesystems using cAdvisor. kubelet does not care about any other filesystems. Any other types of configurations are not currently supported by the kubelet. For example, it is not OK to store volumes and logs in a dedicated filesystem.

What exactly is meant by "it is not OK to store volumes and logs in a dedicated filesystem" ? How or why is it not okay?
This same paragraph says it IS okay to store volumes and logs in a "nodefs" filesystem, so it seems to be a contradiction.
Does it depend on whether "nodefs" is dedicated? How can we know what "nodefs" is? Is it where /var/lib/kubernetes is located, or ... ?
There is some related information here:
[2] https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#configurations-for-local-ephemeral-storage
Issues with the description of the single filesystem layout:

It describes putting all ephemeral local data into one filesystem, and dedicating the filesystem to Kubernetes. But after that, it explains that the default locations for those files are /var/lib/kubernetes and /var/log .  The only way for those two directories to be in the same filesystem is if they are in the root filesystem or a /var filesystem . But /var/log is not dedicated for Kubernetes, all other system applications log there too.  Moreover, if everything is stored in a / or /var filesystem, it is even less dedicated. No matter what, it seems there is no way for this filesystem to be dedicated to Kubernetes as the documentation describes.
This paragraph implies it should be a dedicated FS (though as I said, it can not be) , while the first documentation page [1] says it can not be a dedicated FS.

Regarding the two filesystem layout:

It describes a second filesystem, "the directory where you tell the kubelet to place container image layers and writeable layers". What directory is that? Where is it located by default? How can you change the kubelet configuration to use a different location? AFAICT this is actually about the container engine storage, e.g. /var/lib/docker , which is not directly related to the kubelet, is it?

It takes a bit of connecting the dots to figure out (at least this is the tentative inference/hunch I get from reading the documentation but I could definitely be wrong), but a simpler and more direct way to write these requirements could instead be:

The number 1 most important point is that the logs and ephemeral volume locations (/var/log and /var/lib/kubelet) need to be on the same FS for ephemeral storage limits to be enforced
Optionally you can have a separate FS for the container engine
Optionally you can have other filesystems unrelated to k8s if you want

@rptaylor Thanks for the indepth analysis. It is really helpful. Would you like propose a PR to get this issue closed?

/sig node
/kind bug
/language en
/priority important-longterm
Also relevant, a bit: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#local-ephemeral-storage

Well I could propose some text if we have some information confirming and clarifying what the situation is, but I don't have that information needed to know for sure what the documentation should say. I have just speculated and guessed my way to a tentative understanding of the situation based on ~ 30 minutes of googling. It would be good to have some authoritative confirmation of what the situation really is and what the intended meaning was and if it has  since changed, perhaps from whoever wrote or is responsible for the original documentation.   The official documentation says "it is not OK to store volumes and logs in a dedicated filesystem" with italics for emphasis so it must have been important.

/triage accepted

/remove-lifecycle stale

/remove-lifecycle stale

/reopen
/remove-lifecycle rotten

Subscribed.
I suppose somebody did know what was there and how it should have be configured, but the knowledge was lost...

A related thing we don't describe well: the difference between:

the node's root filesystem which is always / and its same-filesystem children
the kubelet's “root filesystem”, which defaults to whatever filesystem contains /var/lib/kubelet

The page https://kubernetes.io/docs/tasks/administer-cluster/out-of-resource/#eviction-signals seems to be gone; now it redirects to https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals
The information about supported filesystem layouts for the node is changed, now it says
The kubelet supports the following filesystem partitions:

    nodefs: The node's main filesystem, used for local disk volumes, emptyDir, log storage, and more. For example, nodefs contains /var/lib/kubelet/.
    imagefs: An optional filesystem that container runtimes use to store container images and container writable layers.
Kubelet auto-discovers these filesystems and ignores other filesystems. Kubelet does not support other configurations.

It is still not totally clear what nodefs and imagefs would actually be on a node.
Reading this page, I think an admin would still not have enough information to e.g. decide how/where to attach additional storage volumes and configure filesystems on cluster nodes.

/remove-lifecycle stale

/remove-lifecycle stale

/cc

@sftim Since you helped review the container runtime filesystem, should we consider updating these docs as part of this issue?

@sftim Since you helped review the container runtime filesystem, should we consider updating these docs as part of this issue?

I'm very happy for someone else to comment here.

Need clarification to


Addictives came from files not from API

Addictives files (english and french) came from the filesystem.
Why not fetch the Open food API ? cf http://world.openfoodfacts.org/additives.json
We also fetch both english and French during the first launch of the application; why not fetch only the locale one ?

Also, a number of strings are not translated while the additives files permit doing that.
An offline version updated using the API would be nice.

You mean there is a post-job on the current addictives files which add missing translations ? for other languages than english/french ?
The english version is available though http://en.openfoodfacts.org/additives.json but the french version doesn't exist http://fr.openfoodfacts.org/additives.json (404)

There's not, AFAIK. @itchix your take on this ?

OK but i don't understand why both english and french addictives files are saved in the DB (without a locale flag/field) ?
So duplication items are in db and when you need one of them, we estimate that the first is french and second is english; which is not very secure. Then why not only add additives for the current locale ?
final List<Additive> la = Additive.find(Additive.class, "code = ?", tm.toUpperCase());
            if (la.size() == 2) {
                ClickableSpan clickableSpan = new ClickableSpan() {
                    @Override
                    public void onClick(View v) {
                        Additive a;
                        if (Locale.getDefault().getLanguage().contains("fr")) {
                            a = la.get(0);
                        } else {
                            a = la.get(1);
                        }
                    // using a for display
                    }
                };
            }

I don't remember why I did this... :/
But I think we have to change it and improve it like you said =)

Ok i will make you a proposal with a PR.
Le mar. 4 oct. 2016 17:43, itchy<EMAIL_ADDRESS>a écrit :

I don't remember why I did this... :/
But I think we have to change it and improve it like you said =)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/openfoodfacts/OpenFoodFacts-androidApp/issues/149#issuecomment-251427165,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC0GChUD8bvbLjkK0HSt6bPl5kwmuWKlks5qwnQZgaJpZM4KNtOr
.


using Parser blocks as local variables fails in compilation

when Kind is compiled to FormCore, it inlines certain definitions, such as Parser.bind and Parser.pure. because of that, if you use "let" to define a parser, such as:
Test: _
  let parser =
    Parser {
      get k = Parser.text("oi")
      return k
    }
  parser(Parser.State.new(none, "", 0, 0, "oi oi"))

it will fail to compile, because the Parser { … } block will become a lambda, and FormCore can't infer the type of lambdas in the body of a let expression.

That's because the Parser monadic functions are inlined when compiled to FormCore, and, thus, it becomes a lambda. On FormCore, let with a lambda results in a "can't infer" error. We can solve this by not inlining the parser, but that would cause errors on the JS and Scheme backend, since Kind's parser has some mutual recursive definitions that can't be sorted by dependency order and thus will be seen as undefined variables on either back-ends. We can prevent that by wrapping all top-level definitions around a lambda, but that will cause re-computation of top-level constants. We could memoize, though. That will allow Parser to work, but will probably result in some loss of performance. Alternatively, perhaps we can make the inliner smarter to avoid inlining inside the expression of a let?

Closed because the repository now only contains the code for the Kind2 language.


GET requests fail due to uri encoding

Recently setup a lambda behind an ALB and attempted to make GET requests resulting in error message 'The variables search parameter contains invalid JSON.'
Example query params
queryStringParameters: {
          operationName: 'product',
          query: example query',
          variables:
'%7B%22productId%22%3A%22756817%22%2C%22countryCode%22%3A%22GB%22%2C%22currencyCode%22%3A%22GBP%22%7D',
        }

decoding the value via decodeURIComponent solved the issue.
parseQueryParams(event) {
      const params = new URLSearchParams();
      for (const [key, value] of Object.entries((event.queryStringParameters as Record<string, string>) ?? {})) {
        params.append(key, decodeURIComponent(value) ?? '');
      }
      for (const [key, value] of Object.entries(
        (event.multiValueQueryStringParameters as Record<string, string> | undefined) ?? {},
      )) {
        for (const v of value ?? []) {
          params.append(key, v);
        }
      }
      return params.toString();
    }

Thanks for reporting this, seems to be an oversight in testing. I'll get a fix implemented and pushed here in the next day or so!

Fixed in #122


No useful stack trace on error

When there's an error inside a dccautomation.RemoteTestCase, I seem to get an opaque stack trace that doesn't point me to where the issue is.
----------------------------------------------------------------------
Traceback (most recent call last):
  File "..\dccautomation\testcase.py", line 72, in wrapped_test
    self._wrapped_test(client)
  File "..\dccautomation\testcase.py", line 103, in _wrapped_test
    client.exec_(formatted_str)
  File "..\dccautomation\client.py", line 108, in exec_
    return self.sendrecv(['exec', s])
  File "..\dccautomation\client.py", line 86, in sendrecv
    raise errtype(response['traceback'])
RuntimeError: Traceback (most recent call last):
  File "..\dccautomation\server.py", line 70, in start_server
    exec_context(exec_, arg)
ZeroDivisionError: integer division or modulo by zero

Hi Ruutuu. Can you provide more information about your environment? Python version, and what app you're remote-ing into? Unfortunately it may be pretty difficult for me to debug this exactly because I don't have most dcc apps anymore (switched from games/vfx industry) but we may be able to repro this with a simple python-calling-python test case.


The container image for arm64 doesn't include the aarch_64 netty-tcnative artifact

The container image quay.io/artemiscloud/activemq-artemis-broker-kubernetes:1.0.19 for the arm64 doesn't include the aarch_64 netty-tcnative artifact.

Closing this as it was fixed by https://github.com/artemiscloud/activemq-artemis-broker-kubernetes-image/commit/70f5a197b464fbc36b380b1fdf555dc6c09a71bc


[CI]: Add pytest suite into CI

We should add pytest in our CI otherwise i expect them to become outdated very quickly.
You can check how to run these tests here.

Blocked by https://soramitsu.atlassian.net/browse/DOPS-2714


[TEST] This is TEST PR for Gpu caching #2503

This is TEST PR for Gpu caching #2503

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #2534. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ci.nnstreamer.ai/.

:octocat: cibot: @DonghakPark, nntrainer/opencl/opencl_program.cpp includes bug(s). Please fix incorrect coding constructs in your commit before entering a review process.

RESOLVE


Traversing inv item files

In so far I can't tell where I am to run filters for items that have skill requirements since all of the files are split.

Pretty much going with this: http://petstore.swagger.io/?url=https://evekit-sde.orbital.enterprises/20160913/api/ws/v20160913/swagger.json#!/Inventory/getCategories
I suppose all I needed was particular json list.


Update of GSoC-Interest.md by Heramba

Signed-off-by: HerambLimaye<EMAIL_ADDRESS>

@HerambLimaye is there a reason you are suggesting changes to the numbering in the description?

@germonprez did not get your question

Ok got it @germonprez , actually it was my default editor settings
Should I change it back and then open the request again

Yea. Just put it back. Just update your PR.
On Sun, Apr 17, 2022 at 2:06 PM Heramba Limaye @.***>
wrote:

Ok got it @germonprez https://github.com/germonprez , actually it was
my default editor settings
Should I change it back and then open the request again
—
Reply to this email directly, view it on GitHub
https://github.com/chaoss/community/pull/356#issuecomment-1100933565,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFAGUDYFYRDV4FIMCECWALVFROKNANCNFSM5TUHYJBA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Mutual of Omaha Distinguished Chair of Information Science & Technology
Professor of Information Systems and Quantitative Analysis
College of Information Science & Technology
University of Nebraska Omaha
CV: https://bit.ly/2kftONr
Vice President
Omaha Parks Foundation
CHAOSS Board Member
https://chaoss.community/
@.***
he / him / his

ok fixed that @germonprez , hope its ok now?

Hi @HerambLimaye. There are a few conflicts now (new applicants). Could you fix these and then I'll merge.

Thanks @germonprez


Add a iframe preview template for local development.

TBD, since it's useless for new content.

Seems not really useful, since Hugo re-render the page after saving changes, that is, the iframe preview isn't real time.


Follow symbolic links

/search

doesn't follow symbolic links because it uses filepath.Walk(), which doesn't follow symlinks.

/query

~doesn't follow symbolic links~ but it uses go-zglob, which says it follows symlinks.
follow symbolic links in the middle of the path.
doesn't follow symbolic links in the top directory.

Would help us as well. I'm now working around this by using bind mounts.


add Web Animations Resources update

Now in material-design branch. @PaulKinlan

It's still failing for some reason.

As a side.  @jpmedley should take a look over the text.

Its failing because it uses the old style, need to update.

Looks good - merging and will push either Wednesday or Thursday.


Using tooltipster in browser extension

I was looking for libraries that were working out of the box in browser extension and found this one very useful, but:

Tooltips are not inserted in http://iamceege.github.io/tooltipster/ for example. (Seems they have size 0 or smth.)
Positioning working bad (i need to put tooltip in certain place, maybe doing smth wrong)?

Help Please,  I am new to all of this, what am i doing wrong?
This is sample for the code that is used
`        $('.tooltip').tooltipster();
    $(selectedElem).tooltipster("destroy");

    selectedElem = selectedElement;

    $(selectedElem).tooltipster({
        animation: 'grow',
        trigger: 'custom',
        triggerOpen: {},
        triggerClose: {
        click: true
        },
        // delay: 100,
        position: 'bottom',
        interactive: 'true',
        theme: 'tooltipster-shadow',
        touchDevices: false,
        interactive: true,
        minWidth: 500,
        minHeight: 100,
        //maxWidth: 900,
        restoration: 'none',
        contentAsHTML: true,
        functionPosition: function(instance, helper, position){
    position.coord.left = ttPos.left;
    position.coord.top = ttPos.top;
    position.size.height = 500;
    position.size.width = 500;
    return position;
},
        content: $(html)
    });

    $(selectedElem).tooltipster( {functionPosition: function(instance, helper, position){
    position.coord.left = ttRect.left;
    position.coord.top = ttRect.top;
    position.size.height = 500;
    position.size.width = 500;
    return position; }});

     $(selectedElem).tooltipster("show");`

Hi, I see no obvious mistake here, provided that ttRect is defined. I can't help you with this, sorry.

@louisameline  The main trouble for me was positioning function and it not worked.
Also in Edge browser there were some problems with creating tooltips.
Will close ticket cause it need more investigation and i cannot do it right now.


We need endpoints that provide pending transactions

We were able to provide pending transactions in Stoa using pushTransaction, which was addressed in Issue https://github.com/bpfkorea/agora/issues/1403.
It was also used to filter the UTXO used in pending transactions when UTXO was provided.
However, transactions received when Stoa is stopped do not exist on Stoa even if Stoa is restarted.
Therefore, Stoa requires the ability to automatically synchronize to solve this problem.
To do this, we need to add API endpoints that provide pending transactions to Agora.
And Agora does not have the time to receive transactions.
It also provides the time to receive the transactions needed in Stoa to help achieve full synchronization.

This also will need pagination.

We already have https://github.com/bosagora/agora/blob/2abe0897941598847bf06c1684b675ee08413b9f/source/agora/node/FullNode.d#L1233-L1258 but we need something that doesn't require prior knowledge of the hashes.
Parameters could be page size and page count, but that creates an issue with mutation of the tx pool across query.
Another approach is to use a from=hash value so that we never get duplicates (we still miss intermediate hashes, but those will be pushed).


move generated deployment manifest to project directory

[#143825851]
note: the change on apisever pre-start script is used to debug API severs deployment failures described in story https://www.pivotaltracker.com/n/projects/1566795/stories/143471329

@kanekoh  are you good with the PR?  I did not save the manifest to the same file path "app-autoscaler-release/bosh-lite/deployments/autoscaler-bosh-lite-manifest.yml" and have directories to keep all the manifests to make sure the current manifest is not lost when running the script to generate a new one.

LGTM. OK, I understand what you thought.

As our intention is to keep a copy of the generated manifest for future reference, its better to name the directory as "manifests" rather than "deployments". Otherwise LGTM.

@paltanmoy  changed the directory name to "manifests"

I don't totally understand what this is for, do people really have a use case for seeing previous bosh-lite manifests (and if they do can't they script it themselves)? I notice e.g. cf-release doesn't have a comparative thing so it's not (afaik?) standard for the manifest gen script to do this? (the set -x bit definitely seems like a good idea, tho)

@julz so far this is for dev/test purpose only, the whole directory will  be ignored when git commit.  We don't have recommended manifests for different infrastructure yet.
Once we are ready, then we need to

move the 'bosh deployment ${tmpdir}/autoscaler-bosh-lite-manifest.yml' out of 'generate_deployment_manifest' script

2)create a directory "templates" to store all recommended deployment manifests for different infrastructure( bosh-lite goes first)

add a step in readme.md to ask user to set the deployment manifest before running deploy script

LGTM


Fix for page reload on file type setting in composite resource-HOTFIX

This is a hotfix for release candidate 1.12.

@hyi Can you review this small change?

+1


feat: support hot module replacement (HMR)

Fixes #30
Based on #89, https://github.com/TrejGun/extract-text-webpack-plugin/

@bebraw Here's my attempt at adding HMR. Can you review? Thanks.

@msuperina @jantimon Do you want to give this a go and let me know what you think? HMR for extract-text-webpack-plugin is here. 👍

Hello folks, Any plans for merging this?

We probably want final decision from Tobias before moving forward with this.

I had a quick discussion with Tobias. Main points:

ETWP is slow so even with HMR, it's not a good solution for development.
Instead, we should recommend development specific setup (['style-loader', 'css-loader']) (faster) and document that.

Based on this the only way I can see this type of functionality going in is through a plugin of a plugin (html-webpack-plugin style). If it's possible to expose enough hooks, then you could implement extract-text-webpack-hmr-plugin or so without growing the core apart from the plugin interface.

I wish I had time to look into it properly. In my opinion dev configuration
should be as close as possible to production configuration. But as I said I
can only blame myself for not bringing a proper solution.
On Mon, Mar 27, 2017 at 10:42 AM, Juho Vepsäläinen<EMAIL_ADDRESS>
wrote:

I had a quick discussion with Tobias. Main points:

ETWP is slow so even with HMR, it's not a good solution for
development.
Instead, we should recommend development specific setup (['style-loader',
'css-loader']) (faster) and document that.

Based on this the only way I can see this type of functionality going in
is through a plugin of a plugin (html-webpack-plugin style). If it's
possible to expose enough hooks, then you could implement
extract-text-webpack-hmr-plugin or so without growing the core apart
from the plugin interface.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/webpack-contrib/extract-text-webpack-plugin/pull/457#issuecomment-289404455,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARdIg_SkNQ0MLlC0xym5Nd1hJ5U_ot-gks5rp4RrgaJpZM4MYXeL
.

@bebraw

ETWP is slow so even with HMR, it's not a good solution for development.

I fail to see how this is an argument against adding the option for HMR. I'm totally fine if the public recommendation is to avoid it and use a separate dev setup. I'm even fine if you have to pass ETWP an hmr flag. But not having the option because it may be slow? I think we can take it from the large number of comments asking for this feature that users want it, even if it may be slower. Also, at many companies, the developer time spent managing a large, complex split configuration far outweighs any slight decrease in speed using ETWP in dev.

For anyone else who wants this feature, feel free to use my fork (npm install cletusw/extract-text-webpack-plugin#hmr or npm install cletusw/extract-text-webpack-plugin#hmr-webpack-1 if using webpack-1) in the mean time.

@cletusw It's not my call to make. Tobias made it clear to me HMR does not belong here.

@bebraw here's something that might change the equation:
Sever Side Rendering and Split Css Chunks. React Loadable is on course to serve up just the chunks (js + css) your current request needs (I'm working on this feature). However, this can't be a production-only thing, where you only finally see that your server-side rendered code splitting is working during production. So you need to be able to serve up css chunks and you need HMR to continue to work. This is actually 2 issues, and I've discussed elsewhere how to get the ability to have more than one extracted text chunk. So if we can merge such a PR in, you need to be able to have access to those chunks AND HMR at the same time during development.
So @cletusw already built support for this. Not having it as an option is a major mistake. Perhaps @sokra isn't privy to the latest developments in server-side rendered code splitting. It seems to me an important direction that React + Webpack must finally go. As is, you can split chunks, but most apps then require a second request to get that chunk, which also means any HTML it generates is not embedded in the initial page, which is bad for SEO. Otherwise, there is NO general and popular solution to embed required chunks (both JS + CSS) in the initial request for synchronous use client-side so React checksums match. I'm working on precisely this for React Loadable and am almost done. I have a few roundabout ways to make this all work that would be more seamless if ETWP extracted to individual chunks and if it supported extraction plus simultaneous HMR via the style-loader.
The future of apps is code splitting everywhere, but that can't happen if it only becomes a testable reality in production.

@cletusw I started using your fork and it seems to almost be working. On changes to CSS files, I'm seeing hot-update.js files like this added to the head of the page:
webpackHotUpdate(1,{

/***/ 161:
/***/ (function(module, exports, __webpack_require__) {

if (true) { __webpack_require__(92); }
// removed by extract-text-webpack-plugin
module.exports = {"title":"App__title--2FM-W"};
if (true) {
	module.hot.accept();
	if (module.hot.data) {
		__webpack_require__(92)('a4266d22532e157a0f3e','/static/','styles.css');
	}
}

/***/ })

})
//# sourceMappingURL=1.1f2fdd619a534186e86f.hot-update.js.map

And based on examination of the CSS HMR aspect of your code:
https://github.com/cletusw/extract-text-webpack-plugin/blob/360c155567b5e5f61ee0ecdab6d46c01a277b8c4/hotModuleReplacement.js
it's now supposed to look for the previous css file to replace. But how are those stylesheets supposed to initially get embedded in the page??
Here's my usage of the plugin in my webpack config:
{
        test: /\.css$/,
        use: ExtractTextPlugin.extract({
          fallback: "style-loader",
          use: "css-loader?modules&localIdentName=[name]__[local]--[hash:base64:5]"
        })
      },
...
 new ExtractTextPlugin({
      filename: 'styles.css',
      allChunks: true
    }),

UPDATE: I set allChunks: false and it filename: [name].[contenthash].css and HMR works on chunks lol, but not the main entry point. It would be nice to actually make this work with individual css files generated for each chunk, as that is another feature I'm working on getting into this package or a fork. Perhaps that's more natural with how HMR is supposed to work anyway.

@cletusw also, the extract styles file is no longer registered in the stats, e.g: stats.chunks[0].files.inculdes('styles.css') === false. It's also not in stats.assetsByChunkName.main, etc. This is key since most apps use the stats to discover such assets.

@faceyspacey You need to include the CSS files manually in whatever .html file loads your .js. That's the same regardless of HMR.
As for the stats, I might not be able to get around to that for a while, but feel free to PR my fork!

@cletusw Thanks so much for the response. Including the files manually is basically what I resolved to. That actually happens to work out perfectly in my unique scenario since I changed extract-textwebpack-plugin to produce multiple css files for dynamic chunks.
A for fixing my issues with HMR, I actually was able to make your implementation work eventually. I then tried to make it work with my setup to produce multiple css files. For some reason, I had the following issue: HMR appends ?123455, but the corresponding files aren't updated on the server. This is funny because if I use the [contenthash] in the file names, they are generated. What I did was then change the HMR code to append/replace file names like this: main.12345.css, 0.12345.css, etc, which is unfortunate since it essentially hard-codes the requirement that your format the names of your css files that way. Do you know of any reason why file names without hashes might not get updated, whereas if they do have hashes, new files are in fact created for each change?
I know I'm introducing another aspect (creating multiple css files for dynamic chunks), but I'd love if you could take a look at what I've done. I built this to work with React Loadable by the way so all the css and js of dynamic chunks can be sent from the server for synchronously requiring on the client in one render. I have a real nice setup going right now--it just would be ideal to get the code back into this package.
I'll send you my fork in a little bit. Basically the goal would be to make what I built work with filenames just based on [name] without the [contenthash], and of course to make handling of dynamic chunks an option, whereas now my fork is basically a package i intended on naming extract-css-chunk with very few configuration options, since I haven't received much response from the people behind *extract-text-webpack-plugin`.

@cletusw here's my package that provides css files per chunk and working HMR:
https://github.com/faceyspacey/extract-css-chunk
If you have some time, take a look at it, and then maybe we can discuss a version of these changes that can be merged into this package.

@faceyspacey That looks awesome!

Just to chime in, likely the best way to proceed would be to figure out how to expose an API you can hook into. After that it would need ETWP+ to work. That feels like the best way based on Tobias' decision.

@bebraw ok, that shouldn't be too hard. But first we need to figure out how to make files update with HMR when the file name is the same, i.e. doesn't use a content hash. @cletusw did you have any ideas on what could be preventing that?

Hey guys, sorry for jumping in on the conversation, but doest HMR works with this plugin and if so where could I go and find a working implementation I could use as a reference or what do I need to change to make it work. Thanks.

@cletusw up above provides a fork to use his HMR implementation:
https://github.com/webpack-contrib/extract-text-webpack-plugin/pull/457#issuecomment-289497923
It works. Give it a try and report back if there are any problems. ...FYI, I took his implementation and made HMR work part of a a new package extract-css-chunk (linked above), which creates individual css files for all your chunks (for use with code splitting).

@cletusw ...I was thinking back to what you said regarding:

You need to include the CSS files manually in whatever .html file loads your .js. That's the same regardless of HMR.

That didn't affect what I was doing since extract-css-chunk's specific goal is getting those individual CSS files into the page, however that is not in fact how style-loader typically works. It typically appends the <style> elements for you, and then keeps them up to date. That's the expected behavior.
I made the following edit to your code to make that work
resultSource += `
var moduleId = "${text[0][0]}";
var css = "${text[0][1].split("\n").join("")}";
var addStyles = require("${require.resolve("../style-loader/addStyles.js")}");
addStyles([[moduleId, css]], "");

// REMOVE THE FOLLOWING:
//if (module.hot) {
//	module.hot.accept();
//	if (module.hot.data) {
//		require('${require.resolve("./hotModuleReplacement.js")}')('%%extracted-hash%%','${publicPath}','%%extracted-file%%');
//	}
//}`

So notice how style-loader/addStyles.js is used instead. Currently I have to manually add this file to my bootstrap or vendor entry point like this:
entry: {
   vendor: ['style-loader/addStyles.js']
   main: [...]
}

But it works like a charm, and you don't have to worry about adding the css file (possibly with a dynamic hash, which you need to get from stats) to the page. Perhaps this is less relevant in how you initially envisioned it where you have just one main.css file. For me having multiple chunks, it was a bit scarier. In addition, it's something I have to bring back given that if you load chunks asynchronously after the first page load, they won't have the extract css chunk giving it its css.

@faceyspacey  Ummm, why do you need extract-text-webpack-plugin then? style-loader already does exactly what you want by itself. The only reason to use extract-text-webpack-plugin is when you want a separate CSS file that you can load from your HTML. If you're loading it from JS, then you don't need extract-text-webpack-plugin.

@bebraw Thanks for all your responses, but at this time I'm not interested in adding additional complexity (both code-wise and for the user) to this by having it be a separate plugin-to-a-plugin, especially when the lack of HMR is explicitly listed as a shortcoming of the existing implementation. From the README:

I'll continue using my fork in the hope that this PR will someday be merged. In the meantime, anyone else is free to take this work and attempt to implement it as a separate plugin to this plugin.

@cletusw good point. The goal has been to have both, but if you're using extract-text-webpack-plugin, you're obviously using it to embed the CSS manually. So yea, if you only have one CSS file, style-loader isn't needed.
However, having both solves a key problem when it comes to multiple css files generated from dynamic chunks: the fact that you're only embedding the needed css chunks for the initial request, whereas if the client later loads different split chunks, webpack doesn't know how to load both the js and css chunk files. So to handle that what I've done is create 2 js chunks:

0.1234.js
0.1234.no_css.js

And then what I have is React Loadable embedding the js chunk without the css in the initial HTML returned from the server. And then as more chunks are asynchronously loaded, the chunks with the css (provided via style-loader) are provided!
This allows for the smallest chunk sizes embedded in the initial request, i.e. no duplicate css.
Anyway, that's how I stumbled upon using style-loader directly. But, it's not needed in the initial single css file setup you envisioned the HMR for.

@cletusw Using your fork with combination of https://github.com/halt-hammerzeit/universal-webpack/ for some reason generates an empty styles: {} object in webpack-chunks.json - this file should contain styles: {} with filenames of generated .css.
It happens to me when I build my client files.

I will close this, please release this PR as a separate plugin, the sole purpose of ETWP  is to extract the CSS chunks from the bundle and emit a separate CSS file. For HMR in development enviroments style-loader is the recommended solution. Thx

@michael-ciniawsky I could not set style-loader with source maps as I did with ETWP - that's why I would like to see ETWP to implement HMR.

@mieszko4 Please open an issue in regard to what currently doesn't work, when using sourceMap + style-loader  @style-loader instead 😛 . We appreciated any feedback you can provide us to fix regressions there, but HMR isn't simply the purpose of ETWP. ETWP should mainly be used for production builds to gather and extract the CSS chunks
style-loader
https://github.com/webpack-contrib/style-loader/pull/153 (Fix/Set sourceRoot)
https://github.com/webpack-contrib/style-loader/pull/219 (Inline SourceMap)

UPDATE: Here's the latest from extract-css-chunks-webpack-plugin
HMR + Multiple Chunks
USE IT!
To immediately see it in action, try out the boilerplate:
https://github.com/faceyspacey/flush-chunks-boilerplate
Also note, it's part of a larger initiative revolving around React Loadable and its companion package 💩 Webpack Flush Chunks:
https://github.com/faceyspacey/webpack-flush-chunks
https://github.com/thejameskyle/react-loadable
I'm open to merging code back into EWTP, but given how complex this code is (and it is), it really needs leadership from the original maintainers. Kickstarting the plugin of a plugin thing is something I'm willing to help anyone else who gets serious about it and wants to lead it, but I likely won't end up spearheading it.


Logging level by namespace is not covered or clearly explained

This page never mentions that log level needs to be specified for each namespace in the function.  In situations where a function calls code outside the function body no informational logging is done.
This is often perplexing to new users and while the answer may be found in third party blogs or StackOverflow, the real answer belongs here first.
There is a vague example with what appears like a namespace, although it leaves me none the wiser.
Apart from this, the documentation is very useful and always my first step (and choice).
PS.  Examples are very welcome and help put context to the theory.
Regards,
Edwin
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 86aff194-f810-3c21-e322-cdda05dfc734
Version Independent ID: 0864707c-97a7-1166-1bd4-ef9ea212c64e
Content: Configure monitoring for Azure Functions
Content Source: articles/azure-functions/configure-monitoring.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

Thanks for your feedback! We have assigned this issue to the doc author to review further and take the next course of action.


Type duplications

Describe the bug
With valid schema type duplications are generated. See pic below:

overwrite: true
schema: http://localhost:3000/api/v1/data
documents: null
generates:
    src/shared/types/GraphQLSchema.ts:
        plugins:
            - 'typescript'
            - 'typescript-resolvers'
        config:
            typesPrefix: GQL

OS: Windows 10
@graphql-codegen/...: 1.7.0
NodeJS: 10.16.1

And the reason seems is that type from inner field is appearing in all gql types array:

It's valid schema which generates invalid types...

@deser can you please share your schema and config? and maybe a reproduction in a repo/codesandbox?

@deser Closing for now. Please let us know if it's still relevant, and please share a complete reproduction.


Make a separate website for docs

Add recipes, component list, examples, and such on a separate website.
If anyone has input on what the best way to manage OS docs is, let me know here. I'm liking dokz.site. Ideally, it would be on Gatsby or Next.js, so we can use MDX to show the components.

I know there are a few gatsby themes for documentation. I found this one after a quick search: https://github.com/johno/gatsby-theme-documentation. It was created with MDX and theme-ui.
I'm in agreement using MDX for the components would be the way to go.
I don't have as much experience with Next but don't mind digging in and helping with the site.

@cmaycumber thanks so much! I'll investigate Gatsby vs Next a little bit (I know that theme-ui uses gatsby). My only reservation with Gatsby is that I'm not sure how well the react native web will perform with its mdx, since expo has given more priority to Next.js's integration in general.
However, I know that @slorber has done some amazing work with RNW + Gatsby, including having Expo + MDX in his own blog, so if we could use Gatsby like he did, I'm sure it would work!

Hey,
The Gatsby plugin works but is a bit hacky (using a duplicate babel loader, and some people reported problems recently that I need to check)
The support is probably better for Next.
I work on docusaurus (as a contractor for Facebook), it's quite similar to Gatsby, but with a focus on docs feature. If you want to focus on content (ie just md files), it would work great. There's a plugin system and you should be able to add the rnw babel plugin easily. But for RNW SSR I think it would be more complicated to integrate (probably need more lifecycles), so it's up to you, if you need to render the RNW stuff server-side or if you can init them on client side in something like a react-live playground.

We don't really need to SSR RNW components for docs. We could lazy load them in an MDX playground, if that's possible.

As long as you have the babel plugin, and setup the babel transpilation of the source lib (this one), that should work. Even with SSR, it should work, it's just that you won't get the styles inlined in html page, that would produce fouc.
I can create an example if you want

That would be super helpful if you have the time, thanks so much!

I can try to take a crack at setting up Docusaurus once we get the fresnel-2 PR merged.

I'm still a bit swamped with work so I'm trying to knock out issues that I'm facing in my app, but as Dripsy increases in visibility I'm going to start thinking more about docs.
I think what SWR did for their docs is really clean: https://swr.vercel.app/
Codesandboxes like they have could be cool for more elaborate examples too.

SWR's docs do look super clean. Do you know if they are using another library/framework to build them?
I've been playing with a few doc examples with Dripsy using Gatsby and Docusaurus.

Looks like SWR is using Nextra: https://github.com/shuding/nextra

The person maintaining nextra recommended using Dokz https://github.com/remorses/dokz

The person maintaining nextra recommended using Dokz https://github.com/remorses/dokz
Docz seems more feature-rich, but I'm not crazy about the design: https://www.docz.site/

If the documentation site they use for docz is the base site I agree the design isn't the best.
It looks like this docz theme might have some promise:

@nandorojo Have you already started on this? I don't mind prototyping a few versions from a few different doc generators this weekend in separate PR's.

Not yet. I think that sounds good if you want to start prototyping them. Since this is a design system, I like the idea of sleek docs. Nextra appears to be getting more maintenance now, so it could be a good option.
Theme UI's docs are nice as well. Same goes for Stitches.

Cool, I'll put something together for both of those.

I've started playing around with a few of the doc generators. My favorite so far has been Docusaurus it's pretty feature-heavy and is pretty easy to work with after I set it up the first time.
I'm not sure how you think the style compares to some of the others but the functionality is pretty great so far.

Hi there
Docusaurus maintainer 😉 happy you like it.
As a RNW user myself I'd really like you to use it, and work on proper SSR
RNW support (ie providing the required hooks) and hope to be able to help
you a bit get started if needed.
Unfortunately I'm quite busy on the short term as I need to ship i18n asap.
We have MLH interns, they are likely going to work on the WIP bootstrap
theme and a new Tailwind theme. With classic theme they should have the
same UX and feature parity, only a slightly different design. We'll also
make it easier to provide your own styles without having to reimplement the
default theme behavior.
Other solutions look great too and you likely can set up RNW on Gatsby or
Next already. Docusaurus has other unique advantages, by being opiniated
and providing versioning, soon i18n etc...
Le lun. 19 oct. 2020 à 22:22, Chadwick Maycumber<EMAIL_ADDRESS>a écrit :

I've started playing around with a few of the doc generators. My favorite
so far has been Docusaurus it's pretty feature-heavy and is pretty easy to
work with after I set it up the first time.
I'm not sure how you think the style compares to some of the others but
the functionality is pretty great so far.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nandorojo/dripsy/issues/5#issuecomment-712420010, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFW6PQXOYHZ4OZZEG53PPLSLSNXXANCNFSM4OYWIZHA
.

@slorber Thanks for the input! I really enjoy the opinionated style of Docusaurus especially because it's a doc only solution and seems to do a great job at what it's built for.
A few quick questions:

Is there a way to wrap the entire application in an additional provider (e.i DripsyProvider so we can use component styles in MDX) without ejecting the layout theme component? Does the Layout component wrap the MDX by default?
I had some trouble getting the MDX to read the Dripsy package when it was aliased to the root folder when the Docusaurus was a subfolder inside of that. Do you think that this is possible? As a workaround, I just installed the latest version of Dripsy in the project and it worked fine in the MDX so definitely not a deal-breaker.

Great to know 👍

Is there a way to wrap the entire application in an additional provider (e.i DripsyProvider so we can use component styles in MDX) without ejecting the layout theme component? Does the Layout component wrap the MDX by default?

We can to have a "wrapRoot" lifecycle method for CSS-in-JS libs and declaring providers.
Last alpha66 release split the layout in 3 so it's easier to maintain if you swizzle it in the meantime.
You can still create pages without this theme layout component, but all theme created pages use it.
I'd like to add an extra theme/Root component that is guaranteed to be there everywhere at the very top.

I had some trouble getting the MDX to read the Dripsy package when it was aliased to the root folder when the Docusaurus was a subfolder inside of that. Do you think that this is possible? As a workaround, I just installed the latest version of Dripsy in the project and it worked fine in the MDX so definitely not a deal-breaker.

I don't understand 🤪

We can to have a "wrapRoot" lifecycle method for CSS-in-JS libs and declaring providers.

This reminds me of something very similar to Gatsby and was where I was originally looking for when trying to implement the provider at the top level.

I'd like to add an extra theme/Root component that is guaranteed to be there everywhere at the very top.

This makes sense to me as well!

I don't understand 🤪

Sorry, let me clarify a little.
The current project structure looks like:
- docs (Docusaruas)
- src
package.json

I'm curious if I can reference the top-level package.json as an alias in Docusaruses MDX.
For example File.mdx in Docusaruas:
import { View } from 'dripsy'; // This dripsy import looks for the package.json in the project root

I hope that makes better sense. Thanks again for getting back.

I think you should use a monorepo in such case and it should work out of the box. So you have any error?

Chakra has nice docs: https://chakra-ui.com/docs/layout/box

Chakra has nice docs: https://chakra-ui.com/docs/layout/box

I do like their docs a lot. They are extremely extensive.
@nandorojo Do you think that it's better to go with a doc generator or build a more custom solution? I think it would be nice if we can replicate a similar style with docusaurus because it's so easy to use.

I don't see a problem with using a doc generator technically. My main concern with it is making sure the style can be unique and customized closely.

Just some inspiration on how to organize docs. I'm pretty impressed by this: https://fullcalendar.io/docs

Another clean design: https://radix-ui.com/primitives/docs/overview/introduction
I'm pretty far along on remaking geist UI using Dripsy by dogfooding in my app, so most of my time has been going towards that, as well as a framer-motion for react native using reanimated 2. I'll be publishing the monorepo of Dripsy asap, then we can set up CI/CD and implement docs.

Do you think that you'll open-source the dripsy version of geist-ui?
I planned on releasing the component lib I've been building for my app and would much rather put efforts into helping maintain yours and extending mine with yours as a base if needed to reduce duplicate work.
That would also be great if we could build a custom docs site with a component lib that's built-in dripsy. Especially if it's very similar to geist, I think it looks great on doc sites.

I'm open to open-sourcing it. It's currently a package in my app's monorepo, and since I'm still adding code to it a bit rapidly, getting it into its own repo will be a bit of work. Once I get it like 80% of the way there, I can start moving it into its own package, so I'll keep you updated on that @cmaycumber

https://github.com/gorhom/react-native-base-ui

https://github.com/gorhom/react-native-base-ui

Recently just started playing around with react-view. It might be helpful for showcasing the different components, props, and the theming in the dripsy docs.

Recently just started playing around with react-view. It might be helpful for showcasing the different components, props, and the theming in the dripsy docs.

That would be very cool.
These are nice: https://react-hot-toast.com/docs
I might build some sort of toast using that + Dripsy + AnimatePresence in my upcoming animation package.

That would be very cool.
These are nice: https://react-hot-toast.com/docs
I might build some sort of toast using that + Dripsy + AnimatePresence in my upcoming animation package.

Closing until there's movement here.


support (html) fragments

As a user, I want to convert partial documents and other text fragments (such as markdown).

A simple boolean changing the output to body.innerHTML might do.


Kaminari vs WillPaginate

Forem does require "kaminari", which causes the following to happen:
Creating scope :page. Overwriting existing method Forem::Category.page.
Creating scope :page. Overwriting existing method Forem::Topic.page.
Creating scope :page. Overwriting existing method Forem::Forum.page.
Creating scope :page. Overwriting existing method Role.page.
Creating scope :page. Overwriting existing method Listing.page.
Creating scope :visible. Overwriting existing method Listing.visible.

I especially don't like how it overwrites an existing scope visible on my Listing model.
Since Forem supports both kaminari and will_paginate, could we remove the require?

Unfortunately it's not as simple as removing the require statement.

Just tried, removing require didn't help, my guess is that it is being automatically required because of the gemspec

Yup, Bundler.require would do it automatically. Weeeeee.

If it is removed entirely, then we would need to specify in the documentation that kaminari/wp should be added to the app's Gemfile, which is not ideal
There might be a workaround though:
gem 'kaminari', :require => false

It's specified as a gemspec dependency. I wasn't aware that you were able to do :require => false with that.

I don't know if you can, will check bundler source now

Ah I see what you're saying, maybe. You could do this in your Gemfile:
gem 'kaminari', :require => false
gem 'will_paginate'

That would at least tell Bundler to not require kaminari. It's a slight hack though.

Just tried, Bundler still requires it

:rageface:

How about
if !defined?(Kaminari) && !defined?(WillPaginate)
   raise "Please add gem 'kaminari' or gem 'will_paginate'" to your gemfile?
end

Now that I've had a couple (read: eleven) hours to think about this, I reckon your idea is a pretty good one. Let's do it.


[incorrect warning] Existing reader_endpoint_addressof aws_elasticache_replication_group but Unresolved reference

Prerequisites

[x] Ensure you have latest version of plugin installed
[x] Search for possible issue duplicates

Installation details

[x] IDE version : IntelliJ IDEA 2020.3.2 (Ultimate Edition) Build #IU-203.7148.57, built on January 26, 2021
[x] intellij-hcl plugin version: 0.7.10
[x] Terraform version: v0.13.6

Terraform Configuration Files

output "out_redis_replication_group_endpoints" {
  value = [
    aws_elasticache_replication_group.redis_replication_group_module.primary_endpoint_address,
    aws_elasticache_replication_group.redis_replication_group_module.reader_endpoint_address,
  ]
}

Exception
(none: Only WARNING : Unresolved reference )
Expected Behavior
No WARNING Unresolved reference showed.
Actual Behavior

Unresolved reference showed.

Steps to Reproduce

Generate a new .tf file. (aws_elasticache_replication_group)
Generate a new outputs.tf and Copy & paste outputs.tf content. (See  above section Terraform Configuration Files)

Fixed in 0.7.11

Thanks for report. I've confirmed.


Be more conscious with version number

I get notification about new releases of jfrog-cli. When there is an update of the minor version number, I usually look into the change log what has changed. Often I then see that there are only bug fixes listed.
Please be more conscious with the version number: when adopting the semantic versioning scheme,, implementing only bug fixes means to only increase the patch version. Increasing the minor version implies to provide improvements or new features with API compatibility to the previous version.
Thanks!

@schtefan
Thank you for using the JFrog CLI.
The JFrog CLI relies on several components, including jfrog-cli-core, jfrog-client-go, build-info-go, and others.
In order to streamline the release process, we have implemented automated release notes generation. Here is how it works:

When a developer adds a new feature to jfrog-cli-core.
We release a minor version of jfrog-cli-core.
We release a minor version of jfrog-cli, with the new the version of jfrog-cli-core. In this particular scenario, it also introduces a new feature to the jfrog-cli.
The release notes generator automatically sends an email with the release notes, but it does not include the changes made to jfrog-cli-core.
We manually edit the release notes to include the changes made to jfrog-cli-core.

To ensure that the release email always contains accurate information, we have created a pull request at https://github.com/jfrog/jfrog-cli/pull/2059.
To ensure that the release notes sent by email include the relevant information for all components, a human will be responsible for generating the release notes in the upcoming release.
If you have any further questions, please don't hesitate to ask.


ProtonVPN update v1.17.5

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

Microsoft Reviewers: Open in CodeFlow

Seems to have an error code on install.  this may be blocked on the update to have a different return value.

@KevinLaMS It worked for me. Sorry, but I'm not yet enough experienced with the winget or installers to understand what's going wrong or how to fix it :-(

@mloskot i think you can close this one as 1.18.5 and 1.20.1 have been added, i don't know if @KevinLaMS used the Silent switch (that seems to be broken), if so that might be why it failed for him and worked for you.
Also this manifest is out of date since manifest version 1.0.0

Closing as per @OfficialEsco suggestion https://github.com/microsoft/winget-pkgs/pull/5007#issuecomment-827374058


[Branch-2.3] Cherry-pick bugfix from main to branch-2.3

What type of PR is this：

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

run starrocks_fe_unittest


Migration process from Asp.net core 1.x to 2.1 applications targeting .Net framework

Can we consider the following as steps to migrate a Asp.net core application from 1.x to 2.1 for applications that target full framework .

Update target framework monikor to target framework > 462

Update .net core sdk version to 2.1.4 in global.json.

In packagereference attribute  for all .csproj, for all references that connect to microsoft.aspnetcore.* change the  version number to 2.1
E.g   <PackageReference Include=""Microsoft.AspNetCore.Authentication.Cookies" Version="2.1" />

Update the main method of program.cs as per https://docs.microsoft.com/en-us/aspnet/core/migration/1x-to-2x/?view=aspnetcore-2.1#update-main-method-in-program.cs

Startup.cs code changes for adding and removing configuration providers as per https://docs.microsoft.com/en-us/aspnet/core/migration/1x-to-2x/?view=aspnetcore-2.1#add-configuration-providers

Database initialization code changes as required - https://docs.microsoft.com/en-us/aspnet/core/migration/1x-to-2x/?view=aspnetcore-2.1#move-database-initialization-code

Remove references to <DotNetCliToolReference> elements for the following packages. These tools are bundled by default in the .NET Core CLI and don't need to be installed separately.
Microsoft.DotNet.Watcher.Tools (dotnet watch)
Microsoft.EntityFrameworkCore.Tools.DotNet (dotnet ef)
Microsoft.Extensions.Caching.SqlConfig.Tools (dotnet sql-cache)
Microsoft.Extensions.SecretManager.Tools (dotnet user-secrets)

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

ID: 4fa0f562-bdf0-eeea-f076-0c3e05222f75
Version Independent ID: 8269d917-3b32-1607-71da-c756d4d7ad32
Content: Migrate from ASP.NET Core 2.0 to 2.1
Content Source: aspnetcore/migration/20_21.md
Product: aspnet-core
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

If the above steps are good, then can we create a new documentation article for applications targeting full framework that want to migrate from .net core 1.x to 2.1

@scottaddie 	where would this information go? In Migrate from ASP.NET Core 1.x to 2.0


Long-term improvements to custom.py

There are a number of improvements that can be made to custom.py in the long term that will improve its organization, decrease the number of lines of code, be more idiomatic, and better align with conventions for APIs:

[ ] Most of the GET and POST requests use try/catch statements that first try to perform some operations and then, if they fail, return an error. Flask recommends using this pattern: http://flask.pocoo.org/docs/0.10/patterns/apierrors/. We could also create a decorator function that automatically wraps each route's internals with a standard pattern that tries to perform given operations, returns the result if it's a success, and returns an error if it's not. This would save maybe 300 lines of code. It's good to handle errors gracefully, but having every route's structure dominated by error handling weakens the code's readability.

[ ] request_parameter is big and complicated and can probably be eliminated entirely at some point by using existing functionality within Flask & Python. Just an example, the following code:

    try:
        value = request.values[parameter]
    except KeyError:
        # if it isnt found use the default, or return an error Response
        if default is not None:
            return default

can be written as value = request.values.get(parameter, default).

[ ] worker_function is too long and should be refactored.

[ ] The API should consistently return JSON when it is requested. Right now, errors return HTML even if JSON is requested, and return JSON even when HTML is requested.

wrt your first point. The form suggested by Flask that you link to seems similar to what we already have, but I think moving to a decorator is a good idea. This means the entirety of each route would be in a single try/except bracket, so we would lose some specificity, but it doesnt really matter as we print the traceback anyway.

This issue was moved to Dallinger/Dallinger#151


Workmanager status Observer

with workmaneger plugin add observer to tack status of workmanager (start, failed, progress, complete, result)

Hi @halimpuckjava,
By workmanager, are you referring to this plugin ?

hi @darshankawar
yes, i mean flutter workmanager, so why not add observer to track status (start, progress, failed, complete, result)

@halimpuckjava,
the plugin you are using workmanager is a 3rd party plugin. Please consider opening this issue in their repo (https://github.com/fluttercommunity/flutter_workmanager/issues).
Closing this, as it's not related to Flutter. If you disagree, write in comments and I'll reopen.
Thanks.


[parser] Add esprima 3.0.0 tests

Adds the test/fixtures/ directory from Esprima 3.0.0, and a test runner (see src/parser/test/run_esprima_tests.ml) that runs the flow parser against these fixtures.
Here's the current output: https://gist.github.com/mroch/085d5e3f5fb5e08c85972fa5cffe4655
These fixtures work via pairs of files: a .js source file and a .json expected output file. So far, this supports .tree.json outputs, which is a dump of the AST. It doesn't yet support .tokens.json (just the list of tokens), .failures.json (expected errors), etc. and instead marks those tests as skipped.
There is still a lot of work to do both to run all of the tests, and also to fix Flow's estree compatibility, so this PR doesn't run these tests via make test yet. Run make test-esprima-ocaml instead.

this is too big for our import scripts... will have to import it manually.


Create configuration file for ISO8583

Using [1], create a configuration file similar to [2].
[1] - https://docs.wso2.com/display/ESBCONNECTORS/ISO8583+Connector+and+Inbound+Endpoint
[2] - https://github.com/wso2/docs-ei/blob/ConnectorTest/en/micro-integrator/docs/references/connectors/file-connector/file-connector-config.md

Fixed.
https://ei.docs.wso2.com/en/7.1.0/micro-integrator/references/connectors/ISO8583-connector/ISO8583-connector-reference/


Example doesn't compile using the latest aide and Axum crates

error[E0277]: the trait bound `axum::http::Response<Body>: axum_core::response::into_response::IntoResponse` is not satisfied
  --> api/src/docs.rs:45:86
   |
45 |   async fn serve_docs(Extension(api): Extension<Arc<OpenApi>>) -> impl IntoApiResponse {
   |  ______________________________________________________________________________________^
46 | |     Json(api).into_response()
47 | | }
   | |_^ the trait `axum_core::response::into_response::IntoResponse` is not implemented for `axum::http::Response<Body>`
   |
   = help: the following other types implement trait `axum_core::response::into_response::IntoResponse`:
             http_body::empty::Empty<axum::body::Bytes>
             axum_jsonschema::Json<T>
             JsonSchemaRejection
             http_body::combinators::box_body::BoxBody<axum::body::Bytes, E>
             http_body::combinators::box_body::UnsyncBoxBody<axum::body::Bytes, E>
             axum_extra::either::Either<E1, E2>
             axum_extra::either::Either3<E1, E2, E3>
             axum_extra::either::Either4<E1, E2, E3, E4>
           and 138 others
   = note: required for `axum::http::Response<Body>` to implement `IntoApiResponse`

There probably is a version issue, i'll check them before the next release. Also the example could just return without the into_response() i'll rework that too

it was working on 0.13, it's released now.

Thanks @Wicpar


JVM option -XX:+UseShenandoahGC is not supported in JDK-15.0.2+7

Linux x64 JVM 15.0.2+7 says "Option -XX:+UseShenandoahGC not supported". Everything was OK with the previous build of JDK15.

Cannot reproduce:
$ java -XX:+UseShenandoahGC -Xlog:gc -version
[0.022s][info][gc] Using Shenandoah
[0.022s][info][gc] Heuristics ergonomically sets -XX:+ExplicitGCInvokesConcurrent
[0.022s][info][gc] Heuristics ergonomically sets -XX:+ShenandoahImplicitGCInvokesConcurrent
openjdk version "15.0.2" 2021-01-19
OpenJDK Runtime Environment AdoptOpenJDK (build 15.0.2+7)
OpenJDK 64-Bit Server VM AdoptOpenJDK (build 15.0.2+7, mixed mode, sharing)
[0.054s][info][gc] Cancelling GC: Stopping VM

Please provide more details.


Add Dracula dark theme

This PR adds the popular Dracula dark theme using the colours defined in the specification 🧛
There isn't an accompanying light theme because as stated in the official Dracula FAQ:

Dracula can't stand the light.

😄
Screenshot with VSCode also using a Dracula theme

That's really nice! It is absolutely not mandatory to provide systematically a light theme haha!
Thank you! :)


Remove Conditional Compile Flags Around miden-node-proto and Associated Code

What should be done?
As a result of these two discussions

https://github.com/0xPolygonMiden/miden-client/pull/378#discussion_r1630952918
https://github.com/0xPolygonMiden/miden-client/pull/378#discussion_r1639948388

in a recent miden-client PR, this ticket was filed in the miden-node repo https://github.com/0xPolygonMiden/miden-node/issues/388. Once this is complete and the miden-node-proto crate is able to be used as a dependency for both WASm and non-WASM targets, we can go ahead and remove some obsolete code that was added to the miden-client crate as a workaround to get the crate to compile for WASM targets.
How should it be done?

The dep:miden-node-proto can be removed from the list of dependencies for the tonic feature

https://github.com/0xPolygonMiden/miden-client/blob/68aed5e91705ab7dc980c3b05ba7921e5bc37efc/Cargo.toml#L37

The error code gated under the tonic feature can be removed this using statement use miden_node_proto::errors::ConversionError; can be compiled at all times

https://github.com/0xPolygonMiden/miden-client/blob/68aed5e91705ab7dc980c3b05ba7921e5bc37efc/src/errors.rs#L20

hex, prost, and thiserror can be removed as dependencies from the Cargo.toml file.

When is this task done?
This task is done when https://github.com/0xPolygonMiden/miden-node/issues/388 is merged and released in the miden-node repository, and when you can successfully pull in the miden-node-proto crate for both WASM and non-WASM targets. Additionally, the workaround code that was added in the meantime is removed.
Additional context
Related discussions in recent miden-client PR

https://github.com/0xPolygonMiden/miden-client/pull/378#discussion_r1630952918
https://github.com/0xPolygonMiden/miden-client/pull/378#discussion_r1639948388

Closed by #409.


Make the Deployment Process Easier

Right now, the deployment process is as follows:

[Implement and thoroughly test a feature in the master branch.]

Merge master into release. AppVeyor will build the binaries.
Log into AppVeyor, go to Environments / Duality NuGet Package Release, click Update and select the latest merge commit into release.

The obvious problem is in the Package Update step, which is just a lot of manual work that could easily be automated using a command line tool. Ideas for such a command line tool:

It should be executed manually on the developer's machine who does the Package Update commit.
It could scan the directory structure and automatically determine the projects that are affected by the sum of all commits since the last Package Update commit in git history.
For each affected project, the appropriate git commit messages can be retrieved and condensed into each package's release notes. They can be added to the nuspec automatically.
The tool would then display a list of commits for each affected project and ask whether this should be considered a major, minor or patch update. The appropriate version number can be incremented.
The version numbers in both nuspecs and AssemblyInfo files are updated accordingly.

This would streamline the binary release process. It would also make it a lot more failsafe and easier for other developers (who might be entering the future core team of Duality) to grasp.

Wrote a command line tool that can automatically create the Package Update commit as outlined above. Closing this.


forceImport fails with The following deployment clashes with an existing one...

I am deploying some proxies from a factory contract. I want to do some checks of the storage layout before upgrading these proxies, so in preparation for that I was hoping to import the "before" implementations into openzeppelin-upgrades using the forceImport.
At the time of calling forceImport I do not have any .openzeppelin folder, nor (obviously) any manifest file within that folder. Yet I get the following error when importing the layout for a contract at (say) 0x123:
Error: The following deployment clashes with an existing one at 0x123.
Debugging a little, it seems like checkForAddressClash is bing called twice, with the second invocation failing (because the first succeeded?). The two callstacks (console.trace()) are:
    at checkForAddressClash (/Users/neil/dev/voltz/voltz-core/node_modules/@openzeppelin/upgrades-core/src/impl-store.ts:168:7)
    at /Users/neil/dev/voltz/voltz-core/node_modules/@openzeppelin/upgrades-core/src/impl-store.ts:59:17
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Manifest.lockedRun (/Users/neil/dev/voltz/voltz-core/node_modules/@openzeppelin/upgrades-core/src/manifest.ts:123:6)
    at async fetchOrDeployGeneric (/Users/neil/dev/voltz/voltz-core/node_modules/@openzeppelin/upgrades-core/src/impl-store.ts:43:24)
    at async simulateDeployImpl (/Users/neil/dev/voltz/voltz-core/node_modules/@openzeppelin/hardhat-upgrades/src/utils/simulate-deploy.ts:39:3)
    at async addImplToManifest (/Users/neil/dev/voltz/voltz-core/node_modules/@openzeppelin/hardhat-upgrades/src/force-import.ts:94:3)
    at async importProxyToManifest (/Users/neil/dev/voltz/voltz-core/node_modules/@openzeppelin/hardhat-upgrades/src/force-import.ts:68:3)
    at async Proxy.forceImport (/Users/neil/dev/voltz/voltz-core/node_modules/@openzeppelin/hardhat-upgrades/src/force-import.ts:44:7)
    ```

at checkForAddressClash (/Users/neil/dev/voltz/voltz-core/node_modules/@openzeppelin/upgrades-core/src/impl-store.ts:178:6)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async /Users/neil/dev/voltz/voltz-core/node_modules/@openzeppelin/upgrades-core/src/impl-store.ts:59:11
at async Manifest.lockedRun (/Users/neil/dev/voltz/voltz-core/node_modules/@openzeppelin/upgrades-core/src/manifest.ts:123:6)
at async fetchOrDeployGeneric (/Users/neil/dev/voltz/voltz-core/node_modules/@openzeppelin/upgrades-core/src/impl-store.ts:43:24)
at async simulateDeployImpl (/Users/neil/dev/voltz/voltz-core/node_modules/@openzeppelin/hardhat-upgrades/src/utils/simulate-deploy.ts:39:3)
at async addImplToManifest (/Users/neil/dev/voltz/voltz-core/node_modules/@openzeppelin/hardhat-upgrades/src/force-import.ts:94:3)
at async importProxyToManifest (/Users/neil/dev/voltz/voltz-core/node_modules/@openzeppelin/hardhat-upgrades/src/force-import.ts:68:3)
at async Proxy.forceImport (/Users/neil/dev/voltz/voltz-core/node_modules/@openzeppelin/hardhat-upgrades/src/force-import.ts:44:7)
```

In case it is relevant, I am also using the hardhat-deploy plugin.

Can you share your script that calls forceImport?  Are you using a specific network or just the hardhat development network?
Can you run rename the .openzeppelin folder to something else (so that it will be re-created by the plugin), run export DEBUG=@openzeppelin:upgrades:* to enable debug logging, then run your script again and provide the output?

Any solution to this? I ended having a similar issue as well.

@Hampton-Black Would you be able to share a minimal GitHub repo that can be used to reproduce this issue?

@ericglau I'm working out of a private repo in GitLab, but the basics of it are very similar to the above scenario:

I'm using hardhat-deploy plugin,
I'm using forceImport from openzeppelin-upgrades in order to update the deployment artifact that was previously created with the new proxy deployed
I'm specifically using beacon upgradeable proxies

From your debug mode mentioned above, I'm attaching some of the log output.
Thanks for quick response btw!

Thanks for providing that info.  Please note that the Hardhat Upgrades plugin is not currently integrated with hardhat-deploy.
I haven't been able to reproduce this yet, but I've set up an example repository here of deploying a proxy using hardhat-deploy, then running forceImport and upgradeProxy using the plugin.  See the readme of that repo for the steps to run this example.
Also keep in mind that when you call forceImport, the second argument must be the contract factory of the current implementation contract version that is being used, not the version that you are planning to upgrade to.
Hope this example helps.  (And if you are still encountering the issue in your project, could you modify that example repo to be more similar to your scenario so that the issue can be reproduced?  Thanks!)

Thanks for the feedback.
A little more background and possibly the use of forceImport may not be necessary now that I think about it?
In our deploy script, it does the following:

Deploys the Implementation contract,
Deploys the Beacon using openzeppelin-upgrades
Deploys a custom NFT factory contract we've created
Calls the deployed factory contract to create a new collection (this process creates a new Beacon proxy, using the above deployed Beacon and Implementation addresses).
then we would use forceImport in order to store the newly deployed Beacon proxy so that it would be stored in the .openzeppelin/$(network).json file that is created
and lastly, from hardhat-deploy, we get the artifact associated with the original Implementation contract and save the new Beacon proxy address to it, to use in additional scripts.

But reading the documentation again, is this forceImport even needed to accomplish our purpose? I may have misread it. When passing the option, kind: 'beacon', does it try to force import the Beacon or the Beacon proxy address?
Hope this helps.
Thanks

In my case I need a custom proxy implementation (I need to override receive() function on proxy itself).
So i'm doing the following:

deploy implementation with upgrades.deployImplementation(...) <- this adds implementation to the manifest
deploy custom proxy manually with ethers
run upgrades.forceImport(proxyAddress, ImplementationFactory, { 'kind': 'transparent' })

forceImport is when things go wrong. It seems that it wants to re-add implementation to the manifest and it fails because it's already there.
The problem is here:
   at checkForAddressClash (redacted/node_modules/@openzeppelin/upgrades-core/src/impl-store.ts:240:15)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async redacted/node_modules/@openzeppelin/upgrades-core/src/impl-store.ts:77:11
    at async Manifest.lockedRun (redacted/node_modules/@openzeppelin/upgrades-core/src/manifest.ts:265:14)
    at async fetchOrDeployGeneric (redacted/node_modules/@openzeppelin/upgrades-core/src/impl-store.ts:52:24)
    at async fetchOrDeploy (redacted/node_modules/@openzeppelin/upgrades-core/src/impl-store.ts:138:11)
    at async simulateDeployImpl (redacted/node_modules/@openzeppelin/hardhat-upgrades/src/utils/simulate-deploy.ts:38:3)
    at async addImplToManifest (redacted/node_modules/@openzeppelin/hardhat-upgrades/src/force-import.ts:100:3)
    at async importProxyToManifest (redacted/node_modules/@openzeppelin/hardhat-upgrades/src/force-import.ts:74:3)
    at async Proxy.forceImport (redacted/node_modules/@openzeppelin/hardhat-upgrades/src/force-import.ts:46:7)

Hi community, I found that if you want to use forceImport function, you must have kept your old-version contract file, which doesn't make sense.
So I write a simple TS script to help you upgrade a contract using hardhat, without the cache of deployment phase.
https://gist.github.com/wyf-ACCEPT/3a4a96ef5dfb7c73c537ed7ee629d49e

Also leave the solution here:

Fill the .env file:

USDC_ADDRESS=""
PROXY_ADMIN=""

Add contracts/proxy-utils.sol file (just to compile the ProxyAdmin contract):

// SPDX-License-Identifier: MIT
pragma solidity ^0.8.20;

import<EMAIL_ADDRESS>

Add scripts/upgradeManual.ts file:

import "dotenv/config"
import { ethers } from "hardhat"

async function main() {
  const proxyAddress = process.env.USDC_ADDRESS!
  const proxyAdminAddress = process.env.PROXY_ADMIN!

  const proxyAdmin = await ethers.getContractAt("ProxyAdmin", proxyAdminAddress)
  const newImpl = await ethers.deployContract("UpgradeableUSDC", [])

  await proxyAdmin.upgradeAndCall(proxyAddress, await newImpl.getAddress(), "0x")

  console.log(`\x1b[0m${"UpgradeableUSDC"}(upgradeable) upgraded to: \x1b[32m${proxyAddress}`)
}

main()
  .then(() => process.exit(0))
  .catch((error) => {
    console.error(error);
    process.exit(1);
  });

Run the script with:

npx hardhat run ./scripts/upgradeManual.ts --network <your_network>


Create Voice Channel Category set with User limit bug.

When bot creates a voice channel, where Category ID and User limit are already set it will first create voice channel without category with desired user limit, then it will remove user limit and move the channel to category.

Create a voice channel
Set Category ID and User limit
Run the command
See what happens

I have same problem...

Hello, this has been solved in the latest mods a while ago you have to use discord.js 11.5.1.


chore: Remove Dead Code

Pull Request Description
Overview
This PR addresses the backlog item #347 and involves the removal of dead code from the project.
Changes
The following files have been removed:

cloudplatform-connectivity-scp-cf: AccessToken.java
cloudplatform-connectivity-scp-cf: ScpCfDestinationServiceResponseProvider.java
cloudplatform-connectivity-scp-cf: AccessTokenTest.java
cloudplatform-core: WithRuntimeDependencies.java
cloudplatform-core: ConstraintViolationException.java
cloudplatform-core: DependencyNotFoundException.java
cloudplatform-core: EntityAlreadyExistsException.java
cloudplatform-core: EntityNotFoundException.java
cloudplatform-core: StringParsingException.java
cloudplatform-core: UnsupportedCloudFeatureException.java
security: PrincipalAttributeException.java
security: ScpCfSecretStore.java
security: ScpCfSecretStoreFacade.java
security: SecretStore.java
security: SecretStoreAccessor.java
security: SecretStoreFacade.java
security: exception/KeyStoreAccessException.java
security: exception/SecretStoreAccessException.java
s4hana-connectivity: MissingConfigException.java
s4hana-connectivity: VersionNotSupportedException.java
testutil-core: DefaultSecretStoreMocker.java
testutil-core: MockUtil.java
testutil-core: SecretStoreMocker.java
testutil-core: SecurityUtil.java
testutil-core: ThreadContextInvocationInterceptor.java
testutil-core: ThrowableAssertionUtil.java

Reviewer Instructions
Please review the changes to ensure that no necessary code has been removed and that the project builds successfully without these files.

Changes LGTM - release notes are still missing though.

They are here, added them yesterday here 😉


add queue length handling for redis broker with priority

Thanks to @SavinaRoja pull request.
I added priority handle as well for your review.
@danihodovic
@andreynovikov

@danihodovic do you have a chance to check that PR?


upscaler a video, but the result is bad

upscaler a video, but the result is bad
https://storage.googleapis.com/mlserver-environment/frames.mp4

run code: python inference_realbasicvsr.py configs/realbasicvsr_x4.py checkpoints/RealBasicVSR_x4.pth data/demo_001 results/demo_001 --max_seq_len=5


I was able to get the hash of a bitcoin transaction on the testnet, but it is never displayed on the blockchain. Why is this happening?

My code:
`function Transaction($to,$amount,$privateKey,$from){
// Load private key
$ecAdapter = Bitcoin::getEcAdapter();
$privKeyFactory = new PrivateKeyFactory();
$private_key = $privKeyFactory->fromWif($privateKey);
// Generate raw transaction
$addressCreator = new AddressCreator();
$transaction = TransactionFactory::build();
// inputs
$inputs = file_get_contents("https://testnet-api.smartbit.com.au/v1/blockchain/address/".$from);
$inputs = json_decode($inputs, true);
$inputs = $inputs['address']['transactions'];
$inValue = '0';
$inputs_all = array();
$ouputs_all = array();
$i = 0; while ($i < count($inputs)) {
	unset($item_input);
	$item_input = array(
		'txid' => $inputs[$i]['txid'],
		'vout' => $inputs[$i]['inputs'][0]['vout'],
		'sequence' => strval($inputs[$i]['inputs'][0]['sequence']),
		'scriptPubKey' => $inputs[$i]['outputs'][0]['script_pub_key']['hex']
	);
	$inValue += $inputs[$i]['inputs'][0]['value'];
	array_push($inputs_all, $item_input);
	unset($item_ouput);
	$item_ouput = array(
		'satochis' => $inputs[$i]['outputs'][0]['value_int'],
		'address' => $inputs[$i]['outputs'][0]['addresses'][0]
	);
	array_push($ouputs_all, $item_input);
	unset($item_ouput);
	$item_ouput = array(
		'satochis' => $inputs[$i]['outputs'][1]['value_int'],
		'address' => $inputs[$i]['outputs'][1]['addresses'][0]
	);
	array_push($ouputs_all, $item_input);
$i++; }

foreach ($inputs_all as $input) {
   	$transaction->input(
       	$input['txid'],
       	$input['vout'],
       	ScriptFactory::fromHex(''),
   		$input['sequence']
   	);
}
// fee
$fee = 0.00005; // It depends on # inputs, # outputs, type of scriptPubKey..
$toSpend = $inValue - $fee;
$outputValue = '0.0000900';
$changeValue = $toSpend - $outputValue;

$outputValue = ToSatochis($outputValue);
$transaction->payToAddress($outputValue,  $addressCreator->fromString($to));

$txOut = new TransactionOutput(
    $outputValue,
    ScriptFactory::scriptPubKey()->payToPubKeyHash($private_key->getPubKeyHash())
);

// Make transaction
$transaction = $transaction->get();
// Sign transaction
$signer = new Signer($transaction, $ecAdapter);
foreach ($transaction->getInputs() as $index=>$input) {
        $signer->sign($index, $private_key, $txOut);
}

echo "txid: {$transaction->getTxId()->getHex()}\n";
// Signing and get output
$hex = $signer -> get() -> getHex();
echo "raw: {$hex}\n";

}`

Hash: 9fc6c63ec94e711f99e0c3e438a0054969bbddaed116f2619368a632a2bf87a5
I decoded my transaction but everything seems fine at https://live.blockcypher.com/btc-testnet/decodetx/
Transaction Hex:
01000000020242d906a535e30fdb252efbdb64d244bd4d0b967b3891758f0f525b869cd5c6000000006b483045022100a8850a12ae48134c191beafe3b20f2296e53df446882618f83975a720a6ad66202207a1f33f31416b06646f579b9b82eb1895698838f358e69a4eb1adf286284ec0001210227b77566b2dd02f173a83d3eec49bb5efd87866bbfc3d97ac83286c13099507afeffffffac69380a9b96542e7ef800fc6e65cdefbe2fc73504416cf290b029cc5775debe000000006a47304402202884b2c82e0a3fea5bc2fa76eff494577710e682783afba8dec7dc0e9661fa8b022070e4aea86cc9a9b89bde5a7854d5d48334696e617e63e325556a8f2c09dd6f7501210227b77566b2dd02f173a83d3eec49bb5efd87866bbfc3d97ac83286c13099507afeffffff012823000000000000160014def0ed2a458563620f30a8c09d46143ec757fc1e00000000

Have you broadcast the transaction anywhere or have you just run the script here? bitcoin-php doesn't broadcast transactions for you, it's up to you.
I notice you're using smartbit as an api, those guys probably have a tx broadcast endpoint (maybe blockcypher too). Or you could use a local bitcoin node. With both of these, you'll get some feedback if your transaction is invalid or something.
Also there's bit-wasp/bitcoin-p2p-php which supports connecting to the p2p network, so you could broadcast that way, but you get ZERO feedback if the transaction is invalid.

Did this help you?

hello friend, currently I don't have a local node, I want to send transactions without using a local node, so I am checking Bit-Wasp / bitcoin-p2p-php in specific in this example:
https://github.com/Bit-Wasp/bitcoin-p2p-php/blob/master/examples/peer.txrelay.php
Is that reference example okay? or which one do you recommend

The example you linked to actually doesn't do all the work necessary to make sure it broadcast. If you have an error it'd silently do nothing, but it should really connect to some other nodes and listen for the tx.
The most common way for quick scripts is to broadcast through a block explorer. Blockstreams API, blockcypher, blockchain.info. They're usually unauthenticated, but they'll tell you if a signature was invalid.
Or if you have an electrum server you like, you could probably broadcast with that: https://github.com/Bit-Wasp/stratum-php/blob/master/src/Api/ElectrumClient.php Super old code, but it worked once ;)

Hello friend, what am I doing wrong?
It gives me the following error, however I have tried to correct it without success.

My code:
`
$from = 'mg14RzWyo3dAR95FZZDdf9hd394twa5t85';
$inputs = file_get_contents("https://api.blockcypher.com/v1/btc/test3/addrs/".$from."/full?limit=50");
$inputs = json_decode($inputs, true);
$inputs = $inputs['txs'];
$inValue = '0';
$inputs_all = array();
$ouputs_all = array();
$i = 0; while ($i < count($inputs)) {
	unset($item_input);
	$item_input = array(
		'txid' => $inputs[$i]['hash'],
		'vout' => $inputs[$i]['vout_sz'],
		'sequence' => strval($inputs[$i]['inputs'][0]['sequence']),
		'scriptPubKey' => $inputs[$i]['intputs'][0]['witness'][0]
	);
	$inValue += $inputs[$i]['inputs'][0]['output_value'];
	array_push($inputs_all, $item_input);
	unset($item_ouput);
	$item_ouput = array(
		'satochis' => $inputs[$i]['outputs'][0]['value'],
		'address' => $inputs[$i]['outputs'][0]['addresses'][0]
	);
	array_push($ouputs_all, $item_input);
	unset($item_ouput);
	$item_ouput = array(
		'satochis' => $inputs[$i]['outputs'][1]['value'],
		'address' => $inputs[$i]['outputs'][1]['addresses'][0]
	);
	array_push($ouputs_all, $item_input);
$i++; }

foreach ($inputs_all as $input) {
   	$transaction->input(
       	$input['txid'],
       	$input['vout'],
       	ScriptFactory::fromHex($input['scriptPubKey']),
   		$input['sequence']
   	);
}

`

It looks like you still haven't corrected the issue I mentioned in that other issue/PR where you shared it with me
Also, this is wrong:
'scriptPubKey' => $inputs[$i]['intputs'][0]['witness'][0]
I don't think this is based on an example from this repo, maybe take the closest one to your case, then shape that into what you need. Bitcoin stuff is extremely fragile, you need to get it all right or transactions won't work

okay, I'm going to build on the following two examples and tell you how it went.
https://github.com/camtnbikerrwc/altpayments/blob/master/AllPaymentsVirtualCurrencyWrapper.php
https://github.com/hamidteimouri/using-blockcypher/blob/master/app/Libraries/BitcoinDischargeService.php

when i try to download blockcypher a package is abandoned.
Failed to download
rgooding/protobuf-php from dist: The "https://api.github.com/repos/rgooding/Protobuf-PHP/zipball/d688d7894d65d80a38846e0b622b9a2cd7fd4d68" file could not be downloaded (HTTP/1.1 404 Not Found)
https://github.com/blockcypher/php-client/issues/115

Yea block cypher isn't kept up to date, but might not need that to broadcast, maybe you could write it in curl? Or else just pick a different explorer API.


[BRAND REQUEST] X (the "new" twitter)

Please enter the brand name.
X
Please enter the brand website.
https://twitter.com
Please enter the brand SVG. (If Applicable)
https://cdn.cms-twdigitalassets.com/content/dam/about-twitter/x/brand-toolkit/logo-black.png.twimg.2560.png
https://about.twitter.com/en/who-we-are/brand-toolkit

I would suggest adding this as a "new" brand to keep the old twitter logo as a legacy option

Agreed, it's a "new brand" so we wouldn't replace the old.

Been meaning to add this, will be added tomorrow, sometime BST time

Thanks for the suggestion @LukasL28, If you come across any other ideas for sites or apps to add to the repo, let us know and we can add them, the only real stipulation is a svg logo.
Feel free to request even if you do not have a svg logo available and we might be able to find one!