Ideation of template for organizations

- Beta -
Orgs Template

Directory Information

Org Name
Contact Info

Address
Main Number
General email address
Hours or Best Public Hour or Visiting Period ( Orientation Days for schools?)

Audience
Type of Organization
Monthly Fees if applicable
Inception?
Media Links?
Social Media Links
Website
Slack/Discord/Teams if applicable
Description
Badges <for events [thinking about something I saw at GDC]>

Example:
CPL Maker Lab
PUBLIC LIBRARY - ADULT FOCUSED MAKER SPACE - LOW COST - NO MEMBERSHIP
The Maker Lab, Chicago’s first free and publicly accessible maker space, is on the 3rd floor of Harold Washington Library Center. The Maker Lab features introductory workshops and open shop for personal projects and collaboration. We encourage you to explore the full range of making, both high-tech and hands-on.
WEBSITE
bit.ly/cplmakerlab
GPS from Google Maps
V9GC+GP
ADDRESS
400 S State St. Chicago, Illinois 60605
EMAIL
<EMAIL_ADDRESS>PHONE
312-747-4300
EVENTS
chipublib.org/makerlabevents
BEST HOURS
Open Shop
W: 1pm-8pm F|S: 10am-2pm
Free Classes
M|T|R: 1:30pm and 6pm F|S: 2pm
AUDIENCE
Adults
14+ allowed
LAUNCH
July 8th 2013
SOCIAL
Twitter: #cplmakerlab
Instagram: @cplmakerlab
BADGES
MakerSummit 2013,2014
NorthSide MiniMakerFaire


Dev

Added some sprites, a walking animation, a death trigger and the ability to walk and jump.

Cool, something new to test !
Thanks !


Use compose animations without skiko on wasmJs target

I would like to use compose animations core dependency in my wasmJs compose-runtime based application (not compose-web). I don't draw on canvas, I don't want nor need skiko and I have disabled unpacking it with compose {} dsl in gradle. But when adding org.jetbrains.compose.animation:animation-core dependency I can't build my project with this error:
Module not found: Error: Can't resolve './skiko.mjs'

It works ok when I allow generation of skiko.wasm, but I don't want to load almost 9MB of unused (?) code. The same project builds fine and works without skiko when targeting js (my animations work without skiko).
I've used webpack.NormalModuleReplacementPlugin to replace skiko.mjs with some fake, empty module. It allowed me to build my app for both dev and prod, but the development version crashes with a runtime error import object field 'org_jetbrains_skia_Bitmap__1nMake' is not a Function. The production version (processed with binaryen) works fine.

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


Import / Export POC

it's only padding at the moment, but piping is enough to show how little it will take to get some basics working

https://message-bus.glitch.me/

consider using https://github.com/gmmorris/simmerjs instead of a home rolled solution

or consider this tool https://github.com/fczbkk/css-selector-generator


DockerImageName customization feature version 0.0.4

Need to configure docker-image name like below::
DockerImageName.parse("mdillon/postgis:latest").asCompatibleSubstituteFor("postgres")

#24  should have fixed it, can you try with latest version

If I get this correctly, it should be fixed in 0.0.4, but that is not released yet. Any plans to release a new version anytime soon?

Version 0.0.4 has been released. See https://repo1.maven.org/maven2/org/testcontainers/testcontainers-jooq-codegen-maven-plugin/0.0.4/


any eta for alpine 3.3?

As it's released already since 18 Dec.

See https://github.com/docker-library/official-images/pull/1299

I was merged in and pushed. Try out the new --no-cache option!
$ docker run alpine:3.3 apk --no-cache add openssl
fetch http://dl-4.alpinelinux.org/alpine/v3.3/main/x86_64/APKINDEX.tar.gz
fetch http://dl-4.alpinelinux.org/alpine/v3.3/community/x86_64/APKINDEX.tar.gz
(1/1) Installing openssl (1.0.2e-r0)
Executing busybox-1.24.1-r7.trigger
OK: 5 MiB in 12 packages


Fix redirect syntax for upstart template.

Per #182 .
consul was not logging on Ubuntu due to incorrect
redirect syntax in the upstart script.

have this issue as well and #187 related to consul 0.7.1


Spark monad

@isnotinvain #513
also bumped up spark version, 0.9.0-incubating is too old

Thanks for doing this!
Hopefully we can get the spark platform be as well supported as the scalding platform.

@johnynek done, but I'm not sure why build failed, it's strange that it failed on summingbird-core, not summingbird-spark

You got bit by #604. Restarted it. We need to figure out why that test fails occasionally. Is it a real issue with that platform or is it a deeper problem that the job itself is non-determinisitic in online summingbird fundamentally?
When this is green we can merge.

failed again..LOL, how to restart it?


best first search

i added a new java code to implement best first search.

Please Update the Readme and Contributors List :+1:

bfs is already implemented using java so what to do. should i add :+1:

Thank you for your Contribution :+1: Close this PR


Summary data acquisition

The data scope of the keywords is the summary data of all historical performance

Hi @shenmirenliuxiansheng, I'm not sure how to address your issue based on the information provided. If there is an issue with a certain page in the documentation, please include the URL so we can take a look.


GitHub login is failing

Expected Behavior
If applicable, add screenshots to help explain your problem, or include Carbon links that recreate
your issue.
I can't log in to my account any more and i have a lot of code snippets there.
Info
Please complete the following information:
OS [e.g. macOS, Linux, Windows, iOS]:
macOS
Browser [e.g. Chrome, Safari, Firefox]:
Chrome

@mrCodeslinger were you by chance using Incognito mode? This is a known issue with Firebase login (https://github.com/firebase/firebase-js-sdk/issues/3004) that we can't currently fix at the moment.
There is a workaround, however, which is outlined in this comment: https://github.com/firebase/firebase-js-sdk/issues/3004#issuecomment-647007598

If you change the Chrome browser cookie settings from the default value of "Block third-party cookies in Incognito" to "Allow all cookies", Google authentication then succeeds in Chrome incognito:

Obviously that is not ideal, so we will look for alternatives as well.

There is also a known intermittent Firebase error, which is found here: https://github.com/firebase/firebase-js-sdk/issues/1926
(You don't need to worry about that, just posting for posterity)

Closing as solved w/ recent Firebase upgrade — will reopen if we notice the same, or similar issue.


[BUG] Messenger security: Leaked encryption key

Describe the bug
Messenger encryption key is cleartext readable everytime.
To Reproduce

Set encrytion key
Dump EEPROM using any tool requesting UART 051B command, e.g. https://github.com/Lar-Sen/Quansheng_UV-K5_Kitchen/blob/main/v2.01.31_mods/utils/eeprom_tool.py
Read encryption key at 0x0F30
Dun goofed.

Expected behavior
Genuine firmware uses EEPROM 0x0F30 offset to store hashed config password which is used as an AES key. If config password was not given since last boot ('login'), the UART command 0x51B just fails, which is expected behaviour.
In our case, as 'config password' routines were circomvented, EEPROM offset 0x0F30 should NEVER get dumped.
Fix: UART routine must send 0xFF in place of key data if block 0x0F30-0x0F3F gets requested (or just restore original 'login' process before allowing dump).
Details:

Firmware version: RC20.5
other: UV-K5(8) HW rev. 1.6

Additional context
In case of a group scenario, users must share the same encryption key.
Original firmware didn't allow 0x0F30 eeprom block to be restored. In our case, I think it's better to allow it, provided that block couldn't get dumped in any way.
...anyway, this fork is still the best in my opinion :)

Well you are wrong.
Yess, the EEPROM password is stored in plaintext, which is clearly mentioned in the Wiki:

Of course if the EEPROM password is read, it can be copied to other devices and these devices will derive it to the same encryption key, which is actually desired as it allows setting up multiple encrypted radios in bulk via CHIRP.

The solution you propose doesn't provide any additional security, considering the EEPROM itself is not encrypted, users could flash other firmware that would still allow for EEPROM dump.
What you propose (locking EEPROM read, without FW re-flashing) can already be achieved by setting the Passwd option in menu. This way serial connection is prevented until correct password is entered on boot.

It is a good exercise in terms of security though. :)
Based on your issue I've enabled Private vulnerability reporting for this repository.

edit: I don't think this case should be kept private :) You decide.

I guess you are right. Let's keep it public, to prevent duplicates.

Oh and I don't like that approach with AES key hashing.
The only proper hardening solution in my opinion would be to encrypt EEPROM with Passwd derived key. The EEPROM would have to be decrypted on each boot based on user entered key. After 3 wrong retries the EEPROM would get reset.
This would take too much space of the binary image though, so I will not be implementing that.


trigger a new build to fix cve problems

Signed-off-by: Wei Liu<EMAIL_ADDRESS>

/cherry-pick release-2.2
/cherry-pick release-2.3
/cherry-pick release-2.4

refer to https://github.com/stolostron/backlog/issues/22156

/retest

/assign @elgnay

/lgtm


LibGdx main dispatcher

Hi,
In my humble opinion, the async module misses the only feature I'd expect him to provide: A dispatcher for the LibGDX main thread.
Here is how to write it:
public val Dispatchers.LibGdx: CoroutineDispatcher get() = LibGdxDispatcher

private object LibGdxDispatcher : MainCoroutineDispatcher() {

  @ExperimentalCoroutinesApi
  override val immediate = object : MainCoroutineDispatcher() {
    @ExperimentalCoroutinesApi
    override val immediate: MainCoroutineDispatcher get() = this

    override fun dispatch(context: CoroutineContext, block: Runnable) = block.run()
  }

  override fun dispatch(context: CoroutineContext, block: Runnable) = Gdx.app.postRunnable(block)
}

And how to use it:
fun CoroutineScope.startLibGdxCoroutine() = launch(Dispatchers.Main) { // <-- We can use any coroutine builder

  // Here we are on a frame update by the LibGDX thread.

  delay(1000) // <-- Call any suspending function (no need to use the `KtxAsync.delay`)

  // Here we are back on a frame update by the LibGDX thread

  withContext(Dispatchers.Main) {
    // It is not needed in this case, but one may use `withContext` to perform an operation on a frame update of the LibGDX thread
  }
}

I'm going to close this as a duplicate of #154, but I'm still working on this. Recent weeks were pretty busy for me, but now I have a bit more free time - I want to finish the ktx-async refactor and immutable vectors merge by the end of the week.


Use Nuget package for Decompiler

Even if LanguageServer is not published to Nuget, we can use the published Decompiler from Nuget. It shaves of a few seconds on the build and we might get published under "Used By"

Good going, we'll have to remember to bump the NuGet version together with the Bicep assemblies.


Combines active ack and slot release when both are available.

Combines active ack and slot release when both are available. If completion message carries a result, process the active ack.
There are two commits in this patch. The first is semantic preserving/refactoring. The fix is in the second commit.
Closes #4614.
Description

Related issue and scope

[x] I opened an issue to propose and discuss this change (#4614)

My changes affect the following components

[ ] API
[ ] Controller
[ ] Message Bus (e.g., Kafka)
[x] Loadbalancer
[x] Invoker
[ ] Intrinsic actions (e.g., sequences, conductors)
[ ] Data stores (e.g., CouchDB)
[ ] Tests
[ ] Deployment
[ ] CLI
[ ] General tooling
[ ] Documentation

Types of changes

[x] Bug fix (generally a non-breaking change which closes an issue).
[ ] Enhancement or new feature (adds new functionality).
[ ] Breaking change (a bug fix or enhancement which changes existing behavior).

Checklist:

[x] I signed an Apache CLA.
[x] I reviewed the style guides and followed the recommendations (Travis CI will check :).
[x] I added tests to cover my changes.
[x] My changes require further changes to the documentation.
[x] I updated the documentation where necessary.

Codecov Report

Merging #4624 into master will decrease coverage by 5.77%.
The diff coverage is 88.46%.

@@            Coverage Diff             @@
##           master    #4624      +/-   ##
==========================================
- Coverage   84.55%   78.78%   -5.78%
==========================================
  Files         183      183
  Lines        8308     8309       +1
  Branches      571      589      +18
==========================================
- Hits         7025     6546     -479
- Misses       1283     1763     +480

Impacted Files
Coverage Δ

.../openwhisk/core/containerpool/ContainerProxy.scala
92.77% <ø> (ø)
:arrow_up:

...enwhisk/core/loadBalancer/CommonLoadBalancer.scala
81.41% <100%> (+0.16%)
:arrow_up:

...pache/openwhisk/core/invoker/InvokerReactive.scala
79.64% <100%> (-1.23%)
:arrow_down:

.../org/apache/openwhisk/core/connector/Message.scala
67.1% <85%> (+2.24%)
:arrow_up:

...core/database/cosmosdb/RxObservableImplicits.scala
0% <0%> (-100%)
:arrow_down:

...ore/database/cosmosdb/cache/CacheInvalidator.scala
0% <0%> (-100%)
:arrow_down:

...core/database/cosmosdb/CosmosDBArtifactStore.scala
0% <0%> (-95.89%)
:arrow_down:

...tabase/cosmosdb/cache/CacheInvalidatorConfig.scala
0% <0%> (-94.74%)
:arrow_down:

...sk/core/database/cosmosdb/CosmosDBViewMapper.scala
0% <0%> (-92.6%)
:arrow_down:

...e/database/cosmosdb/cache/ChangeFeedListener.scala
0% <0%> (-86.67%)
:arrow_down:

... and 15 more

Continue to review full report at Codecov.

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

@chetanmeh I refactored the active acker's signature/type.
@sven-lange-last we can't remove WhiskActivation - the tests in container proxy rely on it being available and removing it causes a number of issues in testing the proxy (specifically, the tests use non-blocking activations which only generate CompletionMessages and as a result there is no Activation to check as the tests do now.)

I removed WIP label as I think all comments are addressed at this point.


electron-vue Report errors

cnpm Can't find
Error: GET https://npm.taobao.org/mirrors/electron/1.7.5/SHASUMS256.txt returned 404
F:\vue\xiaopeng\node_modules_electron@1.7.5@electron\install.js:48
npm cannot connect
Can you change it to 1.7.4?

@okwangyu
You can manually set the electron version within the package.json or using cnpm i --save-dev<EMAIL_ADDRESS>


Refactor/attestation js package

Hey @nicktaras,
This pull request implements the attestation package for use in the outlet & negotiator.
Currently only the getUseTicket function is used in the outlet but it would be a good place to put some validation
functions for the client to validate the returned proof (I have started playing around with this on a separate branch).
Cheers,
Michael

@nicktaras This is ready for merge.


update GOVERNANCE.md

add blank space

Codecov Report

Merging #389 into develop will decrease coverage by 0.00%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop     #389      +/-   ##
===========================================
- Coverage    52.92%   52.91%   -0.01%
===========================================
  Files          244      244
  Lines        23062    23062
===========================================
- Hits         12206    12204       -2
- Misses        9445     9446       +1
- Partials      1411     1412       +1

Impacted Files
Coverage Δ

bfe_util/fixed_pool.go
83.33% <0.00%> (-16.67%)
:arrow_down:

bfe_websocket/server_conn.go
74.24% <0.00%> (-2.28%)
:arrow_down:

bfe_spdy/server_write_sched.go
78.46% <0.00%> (-1.54%)
:arrow_down:

bfe_spdy/frame_read.go
57.35% <0.00%> (-0.76%)
:arrow_down:

bfe_http2/server.go
71.67% <0.00%> (ø)

bfe_spdy/server_conn.go
78.53% <0.00%> (+0.88%)
:arrow_up:

...e_modules/mod_trust_clientip/mod_trust_clientip.go
46.15% <0.00%> (+3.29%)
:arrow_up:

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 a79b7b8...0016c5d. Read the comment docs.


user.has_token and client.isTrusted

In the oauth2.js, I can see user.has_token and client.isTrusted, but I cannot find those method in the user and client models. Where is these method specified?

I was wondering the same thing. How do we implement these methods?

I think that this part of code is not firing:
module.exports = function authorization(server, options, validate) {
  if (typeof options == 'function') {
    validate = options;
    options = {};
  }

I've found interesting comment
// TODO: Add an optional `immediate` callback, which can consult a
//       pre-approved decision and respond immediately, along with the
//       ability to fall back into "transaction" mode.  Currently, this
//       functionality can be achieved using later route middleware
//       after `next()`ing, but this would optimize away the need to
//       serialize the client into the session.

Eureka
      // WARNING: For security purposes, it is highly advisable to check that
      //          redirectURI provided by the client matches one registered with
      //          the server.  For simplicity, this example does not.  You have
      //          been warned.
      return done(null, client, redirectURI);
    });
  }),
  function (req, res, next) {
    if (req.oauth2.client.trusted) { // add this property to the client
      next()
    } else {
    res.render('dialog', {transactionID: req.oauth2.transactionID, user: req.user, client: req.oauth2.client});
    }
  },
  server.decision(function (req, done) {
    return done(null, {scope: req.scope})
  })
]

I have updated the code to address this.


Support setting headers per request with parameters from map

Analogous to #330 , but for headers instead of query parameters.
Proposal is to introduce a @HeaderMap parameter annotation. The annotation causes the contents of the map to be used as the header parameters for the request. The contents of the map will be additive to header parameters specified by other annotations.
For example:
@RequestLine("POST /")
@Headers({"Auth-Token: {authToken}", "Auth-Token: Foo"})
void logout(@Param("authToken") String token, @HeaderMap Map<String, Object> headers);

In this example, any calls will expand the content of headers and add it (or override if keys are identical) to the headers for the call.

Although the approach is slightly different, this feature may also address issues raised in #214 and #288

Actually, on further reading realized that this won't address #214 since in that case there's a desire to explicitly not have header parameters as any part of the method parameters.
Also, definitely open to discussion/other approaches for accomplishing this. However, much like the QueryParams annotation, in a Feign ecosystem I think this approach is fairly clean and provides the ability to handle headers more dynamically at the API level instead of having to write targets/interceptors that are conceptually more client-specific instead of API-specific

@adriancole for feedback

The problem with HeaderMap, is that it continues the slippery slope away
from templated requests and purpose-made interceptors or targets. I foresaw
a bit of this with QueryMap. Now, there are at least 4 ways to add a header
value dynamically.
I think this type should be explicitly documented for the edge case that it
solves, which is that you have a request-scoped header, and you don't have
anything like a thread local context to attach it with. If it isn't
edge-case only, a concrete example of how interceptor or target doesn't
work would help. Ex real life apis.
So, I'd update both the PR description and the javadoc on HeaderMap with
compelling reasons why we are adding this, vs deferring folks to look at
other issues.
Not only would this reduce confusion when one wonders which of the several
ways they should use, but also give sufficient background on why we
continue this deviation from api minimalism.

Thanks for the feedback -- I will look at the other options and think through this a bit more. Will then either update PR with description/Javadoc with better explanation of the case this addresses (and why it is needed despite the other available mechanisms) or close PR.

in hind sight, I think we at least have a documentation gap. Maybe a section explaining the few ways to set a header could help regardless of where this goes.

Thought about this a bit more, and opened #366 with documentation for current approaches (not sure if README is the best place, but that seems to be where most of current documentation is located -- let me know if there's a better place for this).
After writing that up, I think there is a place for @HeaderMap. It basically falls in category 1 (setting headers as part of the API), but adds a dynamic element to it. Although it may be a corner case, it provides some distinct things not offered by RequestInterceptor or Target -- it makes specifying headers part of the core API, which offers the following benefits:

Setting headers is thread-safe
Setting headers can be done cleanly on a per-request basis in a thread-safe manner
Setting headers is part of the API rather than the client, so existing client setup code (which may already have their own custom interceptors or targets) can use it seamlessly without having to add more interceptors or targets

I'll update this PR with better documentation to explain this motivation/use case. If #366 merges, I will modify the "Headers" section there to include this usage as well.

Thanks for adding rationale. One key thing is that this feature is only
needed for unknown headers, right? Known header keys can be set thread safe
etc at the moment.
So in this case, headers unknown at the time of designing the API can be
added without using things like thread local interceptors.
Mind putting some examples where an unknown header is part of the API? It
is more common in case of query parameters.
I can think of one, for example user metadata encoded as headers. Ex Amazon
S3 objects, if I'm not mistaken. You wouldn't know the range of keys up
front.
I think a solid use case like this will drive home where it is needed this,
while hopefully still encouraging templates when header keys are known.
Thanks for thinking this through.. I'll carve time tomorrow to review
everything.

Sure, will update comments. As you mentioned, metadata is an existing case for this, and exists for both AWS (x-amz-meta-*, http://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectHEAD.html) and Google Cloud (x-goog-meta-*, https://cloud.google.com/storage/docs/reference-headers#xgoogmeta).
Another use case is conditional headers. For example, for server-side encryption requests in AWS (http://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectPUT.html), if the value of x-amz-server-side-encryption is aws:kms, then x-amz-server-side-encryption-aws-kms-key-id must be set as a header value as well. This kind of conditional/dependency based on header field value is hard to express in a declarative manner even if the header field keys themselves are known.

Love the examples.

Updated PR based on docs commit that merged earlier. Let me know if there's anything else I can do for this on my end (including discussing further if necessary :)

all good. nice work!

Fixed by #362


CI should upload API logs on canceled() event

Description

When the API test fails or succeeds in the CI, the logs are uploaded as artifacts. There is a third option: when the ingestion server hangs, the status of the API test step is canceled. The logs are not uploaded in this case.
Reproduction

Check this CI run: https://github.com/WordPress/openverse/actions/runs/4479132806/jobs/7873222573

I think this can be accomplished by moving the timeout-minutes from the job level to the step level.
https://github.com/WordPress/openverse/blob/ce0fe2b9d7d6eb0e9191f036571dd7a67119838d/.github/workflows/ci_cd.yml#L248
https://github.com/WordPress/openverse/blob/ce0fe2b9d7d6eb0e9191f036571dd7a67119838d/.github/workflows/ci_cd.yml#L293
This way if the step times out, only that step will be failed and the subsequent steps of the job (which upload the logs) will continue to run.

@dhruvkb, I think that even if we move the timeout to the steps, if they don't finish in 15 minutes, the event will be canceled, not failed:

If the timeout exceeds the job execution time limit for the runner, the job will be canceled when the execution time limit is met instead. ^1

@obulat that seems right. Maybe it's more complicated then.


standards - language pragma

the standards.md document describes a set of extensions that should be enabled by default in the package.yaml/cabal file, the rest should be enabled in the files that use them only.
please enforce this across the project.

Was looking at integrating these into the mlabs-plutus-use-cases.cabal and saw this:

The following pragmata MUST be enabled at project level (that is, in package.yaml):

#24, #42 and some other tickets talk about using the .cabal file and a nix based workflow, and dropping the Stack based build. Should we modify the Standards.md to reflect this by changing package.yaml to package.cabal ?

@cstml - stack.yaml will not be necessary once we have a working nix build.
however there are probably some big refactors to the cabal file that are quite worthwhile once it isn't just generated code.


[Snyk] Upgrade: react-dnd, react-dnd-html5-backend

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade multiple dependencies.
👯♂ The following dependencies are linked and will therefore be updated together.

:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

Name
Versions
Released on

react-dndfrom 14.0.2 to 14.0.5
3 versions ahead of your current version
a year agoon 2022-01-02

react-dnd-html5-backendfrom 14.0.0 to 14.1.0
3 versions ahead of your current version
a year agoon 2022-01-02

Release notes

Package name: react-dnd

14.0.5 - 2022-01-02

14.0.4 - 2021-09-27

14.0.3 - 2021-08-13Updated
react-dnd: 14.0.3
react-dnd-html5-backend: 14.0.1
react-dnd-touch-backend: 14.1.0
Patch Updates

Fix drop operations in iframes & child windows (#3181) (thanks @ eramdam!)
Refactor TouchBackend OptionsReader (#3291)
Cleanup connected DOM elements from react-dnd internals when hook-based components unmount (#3290)
Fix issue where custom drag-sources where triggering native drops in Firefox (#3272) (thanks @ istateside)

14.0.2 - 2021-03-22Patch
This PR will throw a developer exception if a user specifies a useDrag::spec.begin method.

    from react-dnd GitHub release notes

Package name: react-dnd-html5-backend

14.1.0 - 2022-01-02

14.0.2 - 2021-09-27Patch
This PR will throw a developer exception if a user specifies a useDrag::spec.begin method.

14.0.1 - 2021-08-13Patch
Update internal hook useDragType() to align with updated typings. Check 14.0.0 release for API changes

14.0.0 - 2021-03-09This release addresses a handful of nagging liveness and ergonomic issues with the hooks API.
The liveness issues affect all hooks, and were discovered on deeper inspection of certain stress tests in the documentation. The internal useCollector() hook is used to collect props from the DnD system when things change. Prior to this update, we subscribed to updates from the DnD monitor to trigger prop collection. However, state on the react side was only accounted for on the first render. This release improves that liveness by collecting props whenever react state changes.
The ergonomics of the useDrag have been refactored. In short:

spec.type is required
spec.item can be a function or static object.
The function version of spec.item replaces spec.begin

Since the release of the hooks API, we packed type under spec.item. However, this led to nonintuitive situations where an item field was required to be specified even though items are created in the begin method.
Additionally, in the original React-DnD design, beginDrag() was optional and the type of the draggables had to be defined. If no explicit DragObject was created, an implicit object was created by the system..
The change we've made here decouples type from item, and collapses begin into item.
// Pre-v14
useDrag({
// item defined here to get a type
item: { type: BOX } },
// ...but the actual item is created here
begin: () => ({ id })
})
// v14
useDrag({
type: BOX,
item: () => ({id})
})
e.g.  useDrag({ item: { type: BOX }}) => useDrag({ type: 'BOX' })
We've also added the ability to cancel drag operations in the hooks API by returning null from begin.
// new API
useDrag({
  type: BOX,
  item: () => shouldNotDrag ? null : {id},
})

    from react-dnd-html5-backend GitHub release notes

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@m0nhawk feel free to reopen and merge


src/data/invalid/Study-include-abstract.yaml is not a Study example, it is a Database example

In order to be tested by linkml-run-examples, the first hyphen-separated token in a data file's name must the the verbatim name of the class it instantiates.
The first token of the filename in src/data/invalid/Study-include-abstract.yaml is "Study", but the file instantiates a Database. One piece of evidence for this is that the outermost key is study_set, a slot that only applies to class Database
Since the file is in the src/data/invalid path, it's not obvious that this is a problem. But we should fix this anyway, for the principle of limiting each invalid data file to one error, which is the inclusion of a abstract in this case.

I fixed this and created a PR for your review!


Explanation how to run a CLI project in pycharm community

Hi,
Just thought that you may want to add the instructions how to run a CLI pyramid project in pycharm community addition. (after running the CLI commands)
In windows it was something of this sort

Add local virtual environment to project settings / interpreter  Drive:\Full_path_to_folder\virtualenv\blueyellow\Scripts\python.exe
edit configuration for running project:
2.1. Script: Drive:\Full_path_to_folder\virtualenv\blueyellow\Scripts\pserve-script.py
2.2. Script parameters Drive:\Full_path_to_folder\blue_yellow_app\development.ini

Yep, that sounds about right. How about this?
https://training.talkpython.fm/player/course/python-for-entrepreneurs-build-and-launch-your-online-business/lecture/50410
:)

And for those of you without access:
https://youtu.be/_acAGHV4YZs

yup - looks good.
great response time!

Great, I did seem to omit windows, but hopefully the ideas and commands translate closely enough.


Support Sign in with Slack tokens

If you use "Sign in with Slack" then the token recieved can't access the
"auth.test" endpoint. Instead the identity needs to be fetched from the
"users.identity" endpoint.
This change makes the slack strategy fetch the identity in addition to
the auth wheth the "identity.basic" scope is present.
Note that the strategy always attempts to fetch the auth because
sometimes the token can access both endpoints (say if the scope has
"users:read" and "identity.basic"). The difference is that if the
"identity.basic" scope is present we don't consider an "invalid_auth"
response from the "auth.test" endpoint to be an error case.
ref: https://api.slack.com/docs/sign-in-with-slack

Thank you @ibash! Sorry for the delay in getting to your PR.
@ueberauth/developers any thoughts on this, I think we're good to merge but I'd like to give you a quick chance to offer thoughts.

Thank you @yordis and @ibash 🎉

@ibash we're always looking for contributors if you're interested in helping improve Ueberauth and it's strategies 😁

I'm always open to submitting pull requests :)

@ibash any where you think we can improve the code either through features or refactors, please do. I think we can do a lot to make the projects themselves more approachable which itself encourage more contributors 😁


Wine WOW builds don't support 32-bit gstreamer

Describe the bug
It seems wine WOW builds don't support 32-bit gstreamer. There are such messages in wine build logs:
configure: libhal 32-bit development files not found, no legacy dynamic device support.
configure: libusb-1.0 32-bit development files not found (or too old), USB devices won't be supported.
configure: gstreamer-1.0 base plugins 32-bit development files not found, GStreamer won't be supported.
configure: OSS sound system found but too old (OSSv4 needed), OSS won't be supported.
configure: libcapi20 32-bit development files not found, ISDN won't be supported.
configure: libcups 32-bit development files not found, CUPS won't be supported.
configure: libkrb5 32-bit development files not found (or too old), Kerberos won't be supported.
configure: vkd3d 32-bit development files not found (or too old), Direct3D 12 won't be supported.

Not sure about other libs in this list, but missing gstreamer causes errors when games try to play mp3 files.
Steps To Reproduce
For instance, try to run Morrowind with wine32-full and wineWow-full. With the latter it will have an error in the main menu that says that it can't play mp3 file.
Expected behavior
Wine WOW is able to run Morrowind.
Notify maintainers
@avnik @7c6f434c @bendlas
Metadata
 - system: `"x86_64-linux"`
 - host os: `Linux 5.13.5-zen1, NixOS, 21.05.20210731.11c6620 (Okapi)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.4pre20210707_02dd6bb`
 - channels(root): `"nixos-21.05.1970.11c662074e2"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:

This is still relevant. In particular, I discovered this because EA's Origin crashes after running for a while due to errors like (wine:1436525): GStreamer-WARNING **: 18:13:19.092: Failed to load plugin [...] Wrong ELF class: ELFCLASS64.

On the wiki page there is this, I don't know if it's relevant:

⚠ Glib2 and gstreamer have different header files for 32 and 64 bit, so when compiling 32 bit Wine with gstreamer support on a 64 bit system it is necessary to use PKG_CONFIG_PATH=/path/to/pkgconfig to point to the location of the 32 bit files when running ./configure. Without that, ./configure will find the 64 bit development files instead of the 32 bit ones and disable gstreamer support. (See https://www.winehq.org/pipermail/wine-devel/2016-January/111245.html)

May have a point there. Right now, we're adding both 32 and 64 bit libs into buildInputs: https://github.com/NixOS/nixpkgs/blob/f71c25b983d2724a3e98266ebee801088f504856/pkgs/applications/emulators/wine/base.nix#L66

I wonder if it's related to #207641...
Speaking of that bug (which is about the fact that binary Wine downloads are unable to use 32 bit GStreamer, when using FHS environments like Bottles)...
Some 32 bit games, when I play them in an FHS environment like Bottles, do have a working GStreamer, if I use system Wine WOW (from nixpkgs). I experience this for example with "Ultimate Spider-Man" or "Spider-Man: Shattered Dimensions".
I play them without Bottles? Crash.
I play them with Bottles? Working videos.
But not all games do this (e.g. Oblivion, which has not working audio in both cases).
(Note: this comment may be a false alarm that deserves a separate issue, since Wine on my end seems to have problems even without GStreamer, if I use it outside a FHS environment. For example, with 32 bit Wine, Ultimate Spider-Man crashes on boot anyway, while Spider-Man Shattered Dimensions has huge graphical issues)

Still relevant. It happened again (on latest unstable) with specific game on wineWowPackages.unstableFull package; however the very same game was working fine on wine 8.5, somewhere within a week timeframe before this update. I do not claim that the update caused a regression, most likely issue is about changes in dependent packages.

Bisected to 7c37217a76ffc97c7dc5535d919f22dcc71f0d9b
with error
ERROR: Caught a segmentation fault while loading plugin file:
/nix/store/24plnj748vqm2a3v7wvhsj8h6fsvabsc-gst-plugins-bad-1.22.3/lib/gstreamer-1.0/libgstva.so

@SuperSamus have you tried using wineWow 8.10 with any 32-bit game? If so, do you have any errors like that one? It's weird.

What game exactly?
I tried running Sonic Mania (which is 32 bit) on a fresh prefix, and it runs fine.
Also, the error:

GStreamer-WARNING ... : Failed to load plugin ... wrong ELF class: ELFCLASS64
Doesn't necessarily mean that something is wrong, it's possible that it tries to load the 64 bit plugin first, and then successfully loads the 32 bit plugin with no log.

Have you tried on a fresh prefix?

Game is Cyanotype Daydeam. Sadly fresh prefix does not fix it.
What bothers me is that Wine 8.05 does not have these warnings, yet 8.10 does. Nix is supposed to be all about reproducibility, so different wine versions looking for libraries in different order in weird. Especially when they have identical wrappers (literally compared them with diff, both wines point to the same gstreamer related files in the same order, then launch .wine of corresponding version)
Strace logs are also similar. I took a quick look: before crash there was load of  ~/.cache/gstreamer-1.0/registry.i686.bin, removing it didn't fix anything. There might be other environment impurities that could potentially break things.

Shot in the dark, but maybe this is a regression upstream?

Shot in the dark, but maybe this is a regression upstream?

That's unlikely, otherwise we would have seen a lot of similar reports.
Turns out root of all evil is nvidia (haha, classics). I have optimus laptop / hybrid graphics (nvidia prime), yet game has never been launched on dGPU, iGPU was used instead. But for the sake of experimenting I decided to completely remove nvidia from system config and did nixos-rebuild after that. Same warnings were printed, but game worked in the end!
So nvidia randomly breaks things on wineWow 8.10 and works on wineWow 8.05, no idea why.
At the same time nix-shell -p winePackages.unstable (pure 32-bit only wine 8.10) works fine on nvidia + intel setup.

Let's go back to the original issue, though.
The problem is that pkgconfig is bad at picking the right architecture. (As I said on https://github.com/NixOS/nixpkgs/issues/132352#issuecomment-1454751514)
I see two ways to fix this:

The dirty way is in builder-wow.sh, before starting to configure for the 32 build, to get PKG_CONFIG_PATH and prune out all 64 bit derivations. Problem is... how do I do that?

Rework how wine-wow is built. Instead of building everything in a single derivation, split wine64 in two derivations: one that stops after building (let's call it wine64Build), and the other (the actual wine64) that finishes from where wine64Build left off. This way, we can use wine64Build as a starting point for wine-wow, and have only 32 bit dependencies in the environment.
Problem is, in nixpkgs Wine wasn't set up for doing all this. For example, staging patches are obtained by overriding the derivation, meaning that wine64Build won't be patched since it's just an input. Other example, Wine uses a fully fledged builder that isn't meant to be divided in phases like this.

from https://github.com/NixOS/nixpkgs/pull/238991#issue-1767637334
This is so dirty...

oof ok. I think longer term, exporing your second proposal of re-using the 64bit build's build directory could be well worth it.
Originally, I created builder-wow.sh as a straight port for https://wiki.winehq.org/Building_Wine#Shared_WoW64 but that's been a few years back and may have been updated / superseded, so it may be worth revisiting that at some point

On the other hand, though, upstream is working to remove the need for 32 bit dependencies in the first place. When completed, that would make WoW obsolete and make this effort a bit useless.
(Info on https://www.winehq.org/announce/8.0.)


Amazon drive, overwrite?

Hey,
I'm getting a ton of 409 (duplicate name) errors using rclone and Amazon drive.
Is there anyway that rclone can get a flag to overwrite files that have the same name on Amazon Drive if they are different? Because for the life of me I can't seem to find a way to make that happen.
Thanks

Rclone is supposed to do that automatically.
However amazon drive's directory listings are very eventually consistent
which make it hard.
Do you have lots of files which differ only by case? Eg FILE .TXT and
file.txt that can cause the same problem as AD is case insensitive.

I actually am running into this issue with my media files. Typical situation is after upgrading a file, so lets say I have some series thats 720p and I replaced it with the bluray version at 1080p, but the name remains the same so plex doesn't panic, ei Series S01EXX.Whatever. The next time I sync to Amazon Drive it gives me the 409 error saying there is already something with that name.
That's my use case, am I doing something wrong?

Sound fine, but check you got the case exactly the same. If you didn't
rclone will think they are different files and amazon will give that error.

I'm going to close this now - please re-open if you find out more


New Partner Listing

Description
New layout for partner listing.
Check List

[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the BSD-3-Clause License.

Excited about this update. Let's go live!


Node.js testing framework

Add a test framework that can run assertion and BDD tests for WebAssembly #661 (including headless chrome) and C bindings #671.

@troyronda BDD tests in headless chrome is being tracked in #1238


Implement the app with the layered architecture

There should be a version of the app with the layered architecture. Idea is to demonstrate that in case of the layered architecture entities used in the persistence layer are used across all the level.
Another thing to highlight that this app is read-only.

Implemented


invalidate outdated node health reports

Describe the bug
if a healthy node went down after it had a healthy health report, the indexer will not revalidate it again since it only query up nodes.
we could explicitly require up node on the decision of a healthy node

verified by checking the database and found all healthy rows are updated in the last 5min the health indexer interval
and any previous healthy nodes that didn't respond is updated in the last interval to be unhealthy


Duplication in searching MyVault

When searching MyVault for privately saved posts, the same posts are showing twice in search results

This should be fixed unless the same post is archived twice @ericaryan

Getting lots of dupes when searching

Duplication is fixed!


Draft PR for recording verification ops in VCD

@ekiwi Updated the tests so they actually look at the VCD output.
Just for fun, I implemented the cover statement to add the cover counts into the VCD file, but I don't
have a conviction that it's the right way to go

Addresses Issue #347


Kim MB-4729 Apply Milmove Header

Description
Put in the new MilMoveHeader for the TOO.
Reviewer Notes
Given that this PR is out there: https://github.com/transcom/mymove/pull/5737/files
I'm not certain that all the css changes are needed. I might wait until the above PR gets merged in, and then adjust as necessary. Please let me know if that is a good idea or not. Regardless, I'd still like to get eyes on this PR early.
This PR does not cover putting in the header for the sign in page.
I took out the padding on all the pages so that the header can fit without there being a horizontal white bar between the MilMoveHeader and the customer header. The padding will be added back to pages on a per page basis in another story.
Setup
Add any steps or code to run in this section to help others prepare to run your code:
make office_client_run
make server_run

Code Review Verification Steps

[x] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] User facing changes have been reviewed by design.
[x] Request review from a member of a different team.
[x] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change

Screenshots
If this PR makes visible UI changes, an image of the finished UI can help reviewers and casual
observers understand the context of the changes. A before image is optional and
can be included at the submitter's discretion.
Consider using an animated image to show an entire workflow instead of using multiple images. You may want to use GIPHY CAPTURE for this! 📸
Please frame screenshots to show enough useful context but also highlight the affected regions.

Warnings

:warning:
This PR does not include changes to unit tests, even though it affects app code.

:warning:

Files located in legacy directories (src/shared or src/scenes) have
been edited. Are you sure you don’t want to also relocate them to the new file structure?
View the frontend file org ADR for more information

Messages

:book:
:link: MB-4729

  Generated by :no_entry_sign: dangerJS against 5d6d67b5fcbd037916d8e17c330a957799e53b18

Warnings

:warning:
This PR does not include changes to unit tests, even though it affects app code.

:warning:

Files located in legacy directories (src/shared or src/scenes) have
been edited. Are you sure you don’t want to also relocate them to the new file structure?
View the frontend file org ADR for more information

Messages

:book:
:link: MB-4729

  Generated by :no_entry_sign: dangerJS against 5d6d67b5fcbd037916d8e17c330a957799e53b18

@YanZ777 to answer this question:

Given that this PR is out there: https://github.com/transcom/mymove/pull/5737/files
I'm not certain that all the css changes are needed. I might wait until the above PR gets merged in, and then adjust as necessary. Please let me know if that is a good idea or not. Regardless, I'd still like to get eyes on this PR early.

I don't think you need to worry about it, it doesn't look like that PR will affect the work in this one

@YanZ777 to answer this question:

Given that this PR is out there: https://github.com/transcom/mymove/pull/5737/files
I'm not certain that all the css changes are needed. I might wait until the above PR gets merged in, and then adjust as necessary. Please let me know if that is a good idea or not. Regardless, I'd still like to get eyes on this PR early.

I don't think you need to worry about it, it doesn't look like that PR will affect the work in this one


The app blocks Ctrl-R hotkey

When app is running Ctrl-R hotkey doesn't work system-wide. Browsers, terminal, etc.
Linux Mint 19.3 Cinnamon

When app is running Ctrl-R hotkey doesn't work system-wide. Browsers, terminal, etc.
Linux Mint 19.3 Cinnamon

@sabian Ctrl+R hotkey is for app reload which is being disabled on production.
Can you give some use cases why you need that hotkey? Thank you.

Browsers - page reload
Terminal - reverse search through history
Text editors and IDE - text replace

Browsers - page reload
Terminal - reverse search through history
Text editors and IDE - text replace

@sabian I get it. But I disabled it on production due to the fact that if I enabled it, the users of the app including me can easily break the Pomodoro rules which is not what I want.

@roldanjrCodeArts9711  couldn't you disable only on app?

@roldanjrCodeArts9711 couldn't you disable only on app?

I'm sorry for that @jedsonmelo .
I'm currently working for the new version of the app and all issues here I will try to solve.
If you like the app, use it of just install it for the mean time in order for you to be updated when I release the new version of it.

That new version looks pretty amazing. Though for now you could just swap the dev usable hotkeys/blocked hotkey combos to enable and disable on blur and unblur.
  let blockShortcuts = [
    {
      key: "CommandOrControl+R",
      callback: () => isDev && win.reload()
    },
    {
      key: "CommandOrControl+Shift+R",
      callback: () => isDev && win.reload()
    },
    {
      key: "CommandOrControl+Alt+Q",
      callback: () => isDev && app.quit()
    }
  ];

  win.on("focus", () =>
      blockShortcuts.map(({ key, callback }) =>
          globalShortcut.register(key, callback)
      ));
  win.on("blur", () =>
      blockShortcuts.map(({ key, }) =>
          globalShortcut.unregister(key)
      ));

I can make a pr with the basic changes as I have tested them so far and there seem to be no issues though they are pretty small changes but make the little application useable for devs who may need those keybinds and don't seem to introduce the issues you brought up unless I am missing a major oversight.

That new version looks pretty amazing. Though for now you could just swap the dev usable hotkeys/blocked hotkey combos to enable and disable on blur and unblur.
  let blockShortcuts = [
    {
      key: "CommandOrControl+R",
      callback: () => isDev && win.reload()
    },
    {
      key: "CommandOrControl+Shift+R",
      callback: () => isDev && win.reload()
    },
    {
      key: "CommandOrControl+Alt+Q",
      callback: () => isDev && app.quit()
    }
  ];

  win.on("focus", () =>
      blockShortcuts.map(({ key, callback }) =>
          globalShortcut.register(key, callback)
      ));
  win.on("blur", () =>
      blockShortcuts.map(({ key }) =>
          globalShortcut.unregister(key)
      ));

I can make a pr with the basic changes as I have tested them so far and there seem to be no issues though they are pretty small changes but make the little application useable for devs who may need those keybinds and don't seem to introduce the issues you brought up unless I am missing a major oversight.

Yes please, since I'm very busy right now. Thank you for that. @sekwah41 👍


Coverage improvement

Description
As a user, I would like to have multiple code coverage indicators in the projects:

unit tests
integration tests
As a developer, I would like to have additional tools related to coverage:
history
warnings/errors upon breaching certain values of coverage (e.g. below 100% for unit tests and 50% for integration tests)

Tools available for coverage measurement (to be check as the first):

https://github.com/marketplace/coveralls (currently used)
https://github.com/marketplace/codecov
https://github.com/marketplace/codacy
https://github.com/marketplace/reportportal-io-ai-powered-test-automation-reporting

TODO:

analyze these tools and check their features
potentially switch to another tool if it provides requires features such as:

multiple coverage jobs
customizable shields with coverage report
statements coverage analysis
history how the coverage was changing in the project

Testing strategy

the coverage is measured for testing commit and pull request

Acceptance Criteria

Another tool configured (if any better found and proves their functionalities)

shields added to the main page
integrated with github repository so the coverage is automatically measure at each commit
warnings about breaching the coverage (100% threshold for unit tests; 50% threshold or 5% drop for integration tests)

Coverals and Travis CI information (shields) removed from the main page (coverage report)
Coverals integration kept for now (until the new tool proves that is much better)

After brief investigation, it seems that https://github.com/marketplace/codacy has the most desired features for this project and I would like to have it checked as the first one as it provides:

code coverage measurement
static code analysis with many security check

CodeCov is going to be used as it provides flags feature (the way to mark unit/integration/any other type of tests). It has everything that is required by us without additional firecrackers. We are more than good though.


caddy: build only with go 1.6

Things done

[x] Tested using sandboxing (nix-build --option build-use-chroot true or nix.useChroot on NixOS)
Built on platform(s)

[x] NixOS
[ ] OS X (fails because of broken stdenv https://github.com/NixOS/nixpkgs/issues/14704)
[x] Linux (tested on debian 7)

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip" (nox explodes (https://github.com/madjar/nox/issues/43), but should be fine. no pkgs depend on this)
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

caddys readme suggests:

Note: You will need Go 1.6 or newer.

@angus-g @joachifm

:+1: ready to merge

Looks good to me. Just wondering if it should be disabled = isGo14 || isGo15 to be inline with the way terraform does it. (Probably a minor point)

@angus-g net_go14 does it this way. maybe we don't need that line at all because the version is set by go16Packages .


more precise esbuild target

Fixes #1140.

Are you seeing a difference in the generated files?

Yes.


[BUG] ORDER old sintax v1.1.2

In version 1.1.1 work old sintax ORDER
['ORDER'=>'id DESC']

after update on 1.1.2 work only new sintax

Yes, we don't support this syntax anymore. Split the order sorting keyword to make the code looked cleaner.
"ORDER" => [
	"id" => "ASC"
]


get_zarr returns incorrect data from 3D + 2D MM datasets

Here's a minimal demonstration of the issue
>>> from iohub.reader import imread
>>> reader = imread('/hpc/projects/compmicro/rawdata/other/NIC QLIPP/2022_12_01 PtK cells/FOV1_1')

>>> reader.get_zarr(0)[0,-1,:,500,500] # get the Z profile over the last channel
array([28992, 48564, 22054,     0,     0,     0,     0,     0, 11040,
       19283, 20553,  8202,  8224, 21536, 30821, 10356, 11824, 11317,
       12320,  8236,   631, 10535,  8202,  8224, 15904, 15934, 28704,
       29804, 29486, 28520, 10359,  8233,  8992, 25632, 25455, 25972,
       29811,  8250, 21291, 18763,   224], dtype=uint16)

>>> reader.get_zarr(0)[0,-1,:,500,500] # repeated call gives a different result!
array([21184, 48542, 22054,     0,     0,     0,     0,     0,  2570,
       25939,  8293, 27713, 28531, 11530, 11565, 11565, 11565,  2605,
       27750, 24943,   631, 28528, 25975,  8306,  8250, 28528, 25975,
        8306, 30054, 25454, 26996, 28271, 29728, 24936,  8308, 29296,
       28015, 29807, 29541, 26912,   224], dtype=uint16)

>>> reader.get_array(0)[0,-1,:,500,500] # get_array gives the expected result
array([  0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,
         0,   0,   0,   0,   0,   0,   0, 631,   0,   0,   0,   0,   0,
         0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,
         0,   0], dtype=uint16)

Notes

This dataset is a 3D + 2D dataset from MM...only the 2D channel fails on repeated get_zarr calls
To see the correct result, use get_array, open the dataset in MM, or open with napari's builtin reader
I tested this issue on the converter branch with the new imread function, and I also confirmed that it was inherited from the WaveorderReader.

Symptoms:

recorder view uses get_zarr (currently the WaveorderReader version...with the same behaviour) and behaves erratically when you scroll through Z in napari
Tagging @ieivanov because this issue affects the spindle data from the NIC. This issue is not blocking (scripts can use get_array for now), but it is an strong inconvenience since it blocks many of the napari viewing conveniences that we're used to.

A bit more context here - this dataset has several 3D channels (ZYX) and one 2D channel, i.e. one image of a single z-plane placed at z=n_slices//2 index in the metadata. You can get that if you uncheck "acquire z-stack" (or something similar) for a given channel in the MDA.

It's likely because the array is initialized as 'empty' instead of 'zeros':
https://github.com/czbiohub/iohub/blob/e96e3ccdca4d2396a358c847a90e314c7dfc7665/iohub/multipagetiff.py#L269-L273
And Zarr docs notes:

The contents of an empty Zarr array are not defined. On attempting to retrieve data from an empty Zarr array, any values may be returned, and these are not guaranteed to be stable from one access to the next.

A note to our future selves that being deterministic is the important. Also filling Zarr arrays with zeros (fill_value: 0) doesn't write any chunks with zarr>=2.11, so the need for zarr.empty() should be rare now.


functionResult messages missing 'name' parameter with OpenAI

Adding message of type "functionResult" did not work in OpenAI chat because the parameter 'name' is required.
I could not test the fix with other models.

Hi @kaeldric , can you provide any integration and unit tests?

hey @kaeldric, thanks for your contribution!
If you can add test that would be amazing or maybe some example code in the doc to show the usage?

Hi all! I wrote some tests based on my current usage, I don't know if those work for you.
About the documentation, what do you think about the Integration/Chat/OpenAIChatTest.php function?
I can try to elaborate on that with the idea of providing additional context to the assistant with the result function, maybe checking the result function value.

@kaeldric maybe we can use CalledFunction now it has been introduced?


Fix date format assumption for GroupResourceAccessTokenEvent.CreatedAt

Hey, unfortunately when introducing #1916 I mixed up the CreatedAt dates in the fixtures. Sorry about that, I'm very confused how I managed that myself… probably while testing around. With this PR the fixtures really match the examples from the current docs.
Somewhat unexpectedly, even though both GAT and PAT resource access token event types belong to the same webhook, they have different date formats for the same field.

GAT: "created_at": "2024-01-24 16:27:40 UTC"
PAT: "created_at": "2024-02-05T03:13:44.855Z"

I searched for other places in the code where a format like 2024-01-24 16:27:40 UTC occurs and found (among others) this which I used as a reference:
https://github.com/xanzy/go-gitlab/blob/2c4b565c47917bc633bc2b0521802a0630b76f83/event_webhook_types.go#L832-L833
Hope that this is the correct way! Let me know if it's not – and again, sorry.

Hmm... Yeah the inconsistencies around how time is used in the API is quite frustrating. In this case I guess it would make sense to first open an issue with GitLab to see if it's a bug there which they need to fix instead?

Good idea, I'll create an issue (if there hasn't been one already) and report back

In this case I guess it would make sense to first open an issue with GitLab to see if it's a bug there which they need to fix instead?

Thanks again for the hint, turns out there was more to it 😃 I updated the PR with the necessary links and info.
I think this is ready now!


Metric to track effectiveness of header recency estimation

We introduced the notion of header recency, which just checks if the header is recent via isRecent func. In case of the current subjective header is not recent, we forcefully re-request a new head. We need to know its effectiveness by checking if blockTime+blocktime/2 is big enough not to cause unnecessary requests for the actual real head.

related to #93


Recommended videos do not load

Recommended videos do not load

A redesign needs to happen for this. For some reason, the API call does not return the videoId as part of the result.


Function to get EraCollapse

Collapses treatment eras if the gap between them is smaller than the specified eraCollapseSize.
If an individual receives the same treatment for a longer period of time (e.g. need of chronic treatment), one is likely to need reﬁlls. As patients are not 100% adherent, there might be a gap between two subsequent event eras. Usually, these eras are still considered as one treatment episode and the eraCollapseSize deﬁnes the maximum gap within which two eras of the same event cohort would be collapsed into one era (i.e. seen as continuous treatment instead
of a stop and re-initiation of the same treatment).

done in #37


"zapi repl" should be fixed or removed

While verifying #1306 I tried the repl mode of zapi, as I'd never tried it in its days of being the default zapi mode. As of zapi commit 85c80a4, it doesn't seem usable, as it appears to be trying to return binary ZNG the same way zq does, but I don't see options to change the output mode (-t, while mentioned in the error response, is not available).
$ zapi -s hello repl
hello> count() by _path
writing binary zng data to terminal; override with -B or use -t for text.

Also FWIW, the help text looks to be a copy of zapi help new at the moment.
$ zapi help repl
NAME
    repl - enter read-eval-print loop

...
DESCRIPTION
    The repl command takes a single argument and creates a new, empty space
    named as specified.

I don't get the impression users are reaching for this mode right now so it's surely not a priority. However, at some point we should clean this up so it works or just remove it. I'd be fine with removing, personally, since zapi get seems to cover us pretty well.

The repl is gone thank goodness.


[Feature] XML Device Types define Endpoint Composition

Feature description
ZAP utilizes the data model XML and has recently incorporated support for Parent Endpoints.
For ZAP to store Endpoint Composition into the database, it requires the Endpoint Composition to be specified in the Device Type XML.
For instance, the XML should accurately represent the specifications regarding Endpoint Composition. Notably, the current XML lacks any mention of the Temperature Controlled Cabinet being mandatory for a Refrigerator Device Type.

Referencing the "old XML" here and the "new XML" here, it's evident that we need the Device Type to be defined as either "Tree" or "FullFamily" if the Device Type includes Endpoint Composition.
Platform
all
Platform Version(s)
No response
Anything else?
No response

@bzbarsky-apple it makes sense based on previous discussion to do something like following:
Example 1
<endpointComposition>
         <type>fullFamily</type>
         <endpoint>
                    <deviceType> name of device type </deviceType>
         </endpoint>
</endpointComposition>

OR
Example 2
<endpointComposition>
         <endpoint>
                    <deviceType> name of device type </deviceType>
         </endpoint>
         <endpoint>
                    <deviceType> name of device type </deviceType>
         </endpoint>
</endpointComposition>

ZAP can parse the XML in this case and know

This Device Type has Endpoint Composition
This Device Type is fullFamily or not by the "type"
If the "type" is not "fullFamily" then it is "tree" like in Example 2

Alternatively we could put "type" for tree as well like:
Example 3
<endpointComposition>
         <type> tree </type>
         <endpoint>
                    <deviceType> name of device type </deviceType>
         </endpoint>
         <endpoint>
                    <deviceType> name of device type </deviceType>
         </endpoint>
</endpointComposition>

I might be out of date or missing some context, but If something along these lines is added to the XML, ZAP can parse and add to the database per Device Type

It's logical to assign an attribute to an endpoint XML tag to indicate whether it's optional. In the example below, the first endpoint is marked as mandatory (true), while the second one is not (false), making it optional. Despite not being mandatory, the presence of the second endpoint in the table implies that it's allowed.
Something along these lines makes sense to me:
<endpointComposition>
         <endpoint mandatory=true>
                    <deviceType> name of device type </deviceType>
         </endpoint>
         <endpoint mandatory=false>
                    <deviceType> name of device type </deviceType>
         </endpoint>
</endpointComposition>

If there are Conformance rules like how there are with "features" we could add something like
      <optionalConform>         <notTerm>           <orTerm>             <feature name="LT"/>             <feature name="DF"/>           </orTerm>         </notTerm>       </optionalConform>
Regarding Device Type or Id, from a ZAP perspective either could work but let me double check and get back to you tomorrow.

It makes most sense for ZAP to consume the Device Type ID rather than the name

That seems pretty reasonable.


Cambodia, Laos, Northern Vietnam should belong to Asia/Bangkok instead

See recent discussions on tz mailing list

Did you mean to close this issue right away? I haven't followed that entire thread, but it seems like this applies only to times before the year 1975 (see note in tz database). Also, in this project there was some dicsussion of whether or not to include zones that are links (https://github.com/evansiroky/timezone-boundary-builder/issues/16) and I think it makes sense to not try to keep track of all the links and instead just use the zones for each nation states. It makes things easier too if a country decides to change their time which would require disassociating the boundary building process of combining linked areas. So I guess since this affects only data from prior to 1975, I guess it's fine to keep this issue closed and not act on anything here, but do feel free to reopen if needed.

The tricky thing here is Asia/Hanoi which have more data in the backzone tab and not just simply a link


[DevTools] Allow Configure Inspect Hovered Control KeyBinding

Is your feature request related to a problem? Please describe.
When you have multiple keyboard layouts on Windows 10-11, the "CTRL-SHIFT" key combination is associated with the action of switching keyboard layouts. This does not allow you to use Inspect Hovered Control because it is binding to the same key combination.
Describe the solution you'd like
Allow configure InspectHoveredControl KeyBinding
Describe alternatives you've considered
No response
Additional context
No response

The main issues that caused me to punt on mutability of hotkeys (and why they weren't implemented in #15700 :

There's no settings store for DevTools. This means in-app changes only last until the next debugging launch. You could configure in code, but that effects your entire team.
There's no dialog system in DevTools, so that needs implemented or a workaround. In-place edits might be enough, but I do have other feature ideas where a small input dialog would be very useful. Any dialog needs to hidden from the DevTools Logical/Visual Trees, which https://github.com/AvaloniaUtils/DialogHost.Avalonia would support (being an overlay), but this doesn't warrant bringing in an external dependency, IMO.
Not sure if the quality / naming is good enough for HotKeyConfiguration to be made public, so I left this part malleable for any future implementer.

There's no settings store for DevTools. This means in-app changes only last until the next debugging launch. You could configure in code, but that effects your entire team.

To solve this problem I load DevToolsOptions from appsettings.development.json

Hi @maxkatz6,
Can I do a PR? Should I make this public or implement this?


Shopify Checkout Throttling and Queue

This repository is missing two critical features required for large Shopify stores:

Checkout-level throttle
Shopify limits the amount of checkouts that can be created on the Storefront API per minute. If an API client exceeds this throttle, then a 200 Throttled error response is returned. Shopify recommends designing your app to be resilient to this scenario. For example, you could implement a request queue with an exponential backoff algorithm.

/throttle/queue
Shopify redirects users in the checkout flow to /throttle/queue if the store is under high traffic.

Without these features, two things will happen. The API silently fails when creating a checkout session, meaning that addToCart requests also silently fail. Also, during the checkout flow, the user will be redirected to a nonexistent URL.

This is an interesting subject. If a store is facing this issue during sales then bots may likely be involved.
Not only does Shopify Plus have a throttle but also a checkpoint option to solve a captcha before receiving a checkout url.
Obviously, some bots can still get around this checkpoint. It’s an uphill battle and Shopify Plus is constantly adding patches to bot squash and handle traffic.
Question is: During these types of sales do you want to be responsible for scaling the site to handle this amount of traffic/bots or allowing Shopify by using a theme?

If a store is facing this issue during sales then bots may likely be involved.

Lot's of shopify plus stores hit peaks of more than 4000 concurrent users, particularly merchants that have product releases or drops. I would say this is something the vercel commerce team needs to address pretty quickly. There are work arounds that you can do in the existing project to resolve this issue that don't involve a queue. But it would be better if the core did actually use cart instead of checkout.

Referencing this here:
https://github.com/vercel/commerce/issues/430

This is an interesting subject. If a store is facing this issue during sales then bots may likely be involved.

I actually created this issue because I manage https://ludwig.gg, and ran into these issues yesterday during a merch release. Especially since by default, the repository creates a cart session upon the first useCart call, it doesn't take too much traffic to trigger throttling. Perhaps if there isn't an existing cart, the framework should wait until the first add, remove, or update request to actually create the cart session.

Question is: During these types of sales do you want to be responsible for scaling the site to handle this amount of traffic/bots or allowing Shopify by using a theme?

The reason I shifted to this framework was to avoid using themes because of their limitations. I will be in contact with Shopify Plus to find out if it's feasible to re-implement their checkout queue, or add a single redirect for the /throttle/queue page (which is undocumented, as far as I can see)

@ottomated, I might be able to help you with this issue as my team has solved it. There’s only a few lines of code to change to stop useCart() initialising a cart immediately on page view and only triggering it on add to cart. Happy to collaborate here.

@ottomated just created a PR with your suggestion to create a checkout only on the fist cart interaction, not the very first visit of the store.
I started also to implement the Cart API instead of Checkout, i will make a PR with that too when is finished.
@balakedev would be nice for the community to create a PR when you have a fix or an improvement so we all can benefit from it :)

Hey there! Thank you for opening this issue. We have decided to take Next.js Commerce in a new direction and will be closing out current PRs and issues due to this change. Please see this PR for more details: https://github.com/vercel/commerce/pull/966


add unzip again (fixes #184)

Earlier versions of this project included unzip,
and some project using this S2I based image relied on that.
Recent versions, after the change from the jboss to the centos
base, lost unzip, therefore breaking downstream projects.
This puts it back explicitly.

@rhuss OK for you, or any very strong reason why not to re-add unzip back again?

I'm fine with that. Could you please fix the conflicts, then you can merge it.

I'm fine with that. Could you please fix the conflicts, then you can merge it.

done


if T0 missing in des file, get "limit on number of axes" error message

Reported by Ansley B Manke on 3 Apr 2002 19:17 UTC
Occurs when a second des file specified, without a D_T0TIME in the
$BACKGROUND_RECORD section.  If a time axis matches a previous one, the status
flag isn't set to OK in tm_get_like_line.F.  So a previous status setting is
seen in gt_get_time_axis.F.  That was not-OK if time origin T0 hasn't been set
in the descriptor files.   The second descriptor file is not used.
(fix in ACM checkins for v5.41)
Bug occurs back to v4.91
See ~ansley/ans_ferret/users/jin/two_des.jnl
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/381

Comment by<EMAIL_ADDRESS>on 5 Nov 2003 22:25 UTC
lower the priority, reassign to Ansley

Comment by<EMAIL_ADDRESS>on 8 Jun 2007 22:23 UTC
Lower the Priority of this bug


The 'test-strict' and 'test-nonstrict' projects do not build on Windows (VS2013 Update 2)

There are about ~40 errors per project, but they are essentially all the same: Some macro syntax is apparently not supported in Visual Studio. For example here:
#define WITH_QUOTES 12
, {.name= "with quotes"
  ,.type= HTTP_REQUEST
  ,.raw= "GET /with_\"stupid\"_quotes?foo=\"bar\" HTTP/1.1\r\n\r\n"
  ,.should_keep_alive= TRUE
  ,.message_complete_on_eof= FALSE
  ,.http_major= 1
  ,.http_minor= 1
  ,.method= HTTP_GET
  ,.query_string= "foo=\"bar\""
  ,.fragment= ""
  ,.request_path= "/with_\"stupid\"_quotes"
  ,.request_url= "/with_\"stupid\"_quotes?foo=\"bar\""
  ,.num_headers= 0
  ,.headers= { }
  ,.body= ""
  }

It complains "syntax error: }" on the ,headers={} line and the '}' is squiggly red. This is an example error, there are a few others where it complains about syntax error ','.
Steps to reproduce:
have python on your path
svn co http://gyp.googlecode.com/svn/trunk build/gyp --revision 1831
"path to http-parser"> "path to gyp.bat" --depth 1
open solution in Visual Studio and click "build"

@indutny... any reason to keep this open?


test: add limit connection e2e tests

added e2e tests to test connection limit
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #2508 into master will increase coverage by 1.83%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2508      +/-   ##
==========================================
+ Coverage    62.8%   64.63%   +1.83%
==========================================
  Files         199      199
  Lines       10038     9753     -285
  Branches     2032     1980      -52
==========================================
  Hits         6304     6304
+ Misses       3454     3168     -286
- Partials      280      281       +1

Impacted Files
Coverage Δ

...fy-appsync-simulator/src/schema/directives/auth.ts

...mplify-appsync-simulator/src/mqtt-server/client.ts

...ages/amplify-appsync-simulator/src/schema/index.ts

packages/amplify-appsync-simulator/src/index.ts

...psync-simulator/src/velocity/util/general-utils.ts

...fy-appsync-simulator/src/data-loader/none/index.ts

...ages/amplify-appsync-simulator/src/server/index.ts
0% <0%> (ø)

...sync-simulator/src/velocity/util/dynamodb-utils.ts
0% <0%> (ø)

...amplify-appsync-simulator/src/server/operations.ts
0% <0%> (ø)

...sync-simulator/src/velocity/value-mapper/mapper.ts
0% <0%> (ø)

... and 2 more

Continue to review full report at Codecov.

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


Add managedSources to packageSrc / mappings

Problem:
When using scalatest / scalactic for dotty projects, in IDE, we can't jump to scalatest / scalactic sources.
This PR fix that

@ohze Fyi I have cherry-pick your commit(s) into this branch here for the upcoming 3.2.0:
https://github.com/scalatest/scalatest/tree/feature-3.2.0-with-dotty-improvements

@ohze Fyi changes included in this new PR for 3.2.0 https://github.com/scalatest/scalatest/pull/1827

@ohze Closing this as this is merged and released as 3.2.0.


Make plots that are publicly viewable

We have plots like workshops over time, learners over time, etc. that are accessible to logged in users.
Is it possible to have similar views that are publicly viewable?  (still keeping the underlying source data private)
If that's something we can do, I'll follow up more scoping out what I'm thinking about.

Closing this in favor of exploring it in redash.


Read nested XML tags

Hi,
Is it possible to somehow read xml structure with nested tags like
<book>     <id>1</id>     <book>       <id>2</id>     </book>     <book>       <id>3</id>     </book> </book>
Specifying xpath would be great option.. Or maybe some additional parameters like level or rootTag for read function?
Thanks!

Yeap, this'd be an option. Maybe it'd be great if we have this support in a clean and sensible way.

Now, it's fixed. This can be read and manually filtered by DataFrame operations.

Yes you can select things like "book.id" although not XPath expressions


python310Packages.itanium-demangler: remove whitespaces

Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

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

[ ] Fits CONTRIBUTING.md.

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

8 packages built:

python310Packages.angr
python310Packages.angrcli
python310Packages.angrop
python310Packages.itanium-demangler
python311Packages.angr
python311Packages.angrcli
python311Packages.angrop
python311Packages.itanium-demangler


Facing fatal Internal Error with FPDCODataInterface.cpp when removing configuration/output parameters in Python Measurement with LabVIEW UI

Open a Python Measurement with LabVIEW UI in Instrument Studio using the gPlugin
For the First time it opens as Expected.
Close the Instrument Studio
Then remove any one  Configuration Parameter both in the measurement and in the LabVIEW UI.
Reopen the Instrument and try Launching the same measurement with one less input parameter.  Facing the below error or instrument studio crash.

Observation :

This is resolved After Unchecking this option which was discussed to be a potential fix for https://github.com/ni/measurement-services-labview/issues/26

AB#2270677

Was fixed as noted in the comments above.


Update dry-run to dry-run=client

Migrate to --dry-run=client.
W0401 00:09:10.499551      90 helpers.go:535] --dry-run is deprecated and can be replaced with --dry-run=client.

This merged will broken when kubectl >= 1.8, --dry-run should be --dry-run=true
Please see [[link]].

This merged will broken when kubectl >= 1.18, --dry-run should be --dry-run=true
Please see [[link]].

Thanks for raising @jetthaisean.
We plan on making a fix.

Check the version and use --dry-run=client for 1.18 or higher, otherwise --dry-run=true
Roll back this change back until --dry-run=true is removed from kubectl


Extract constructor options as interface

No functional change, only extracting the constructor options as an exported interface to simplify for clients that need a type to refer to.
For example, a client wanting to pass a subset of options currently would have to use constructs such as:
Pick<ConstructorParameters<typeof OpenAPI.OpenAPIBackend>[0], 'ajvOptions'>

but can now use
Pick<OpenAPI.Options, 'ajvOptions'>

Good stuff! Thank you ❤


Add UI tests to Dual View sample

Includes changes related to project reorganization in addition to UI tests
I'm not sure how well the zoom in/zoom out tests work in MapImageTest.kt (sometimes they drag instead of zooming), so we can take those out if you agree!

I would suggest we test the button clicking (switch between restaurant and map) instead of the image zooming and dragging.


The size of emoji's icon is too small

Thank you so much for the awesome extension.
Just a quick question, is it possible to make the icon bigger on the search bar?

Like other plugins

Hello @pokk
This is because pillow library generates icons on the fly without any margin trimming. I will think of a system to let you control size of the icon. I personally prefer it smaller than other plugins but I totally understand you prefer bigger icons.

@pokk should be fix with v1.2.4. Change the padding to a small value, and refresh your API.

@BenjaminOddou
Thank you very much for your quick response. This is functioning flawlessly and is precisely what I needed!


copy font with different defaultLayerName or missing "default.public"

When copying a font where the default layer name is different and "default.public" is not available (due to a rename), copy will raise assert len(order) == len(self._layerOrder) as the length of the new empty class has a different default layer.
will make a PR that adds a fix by changing the name of the default layer in the newly created empty font.
self.defaultLayer.name = source.defaultLayerName

to reproduce
from fontParts.fontshell import RFont

f = RFont()
f.defaultLayer.name = "hello"

f.copy()

Closed by #630


[xorstr] Update to fix GCC warnings and compilation error

What does your PR fix?
https://github.com/JustasMasiulis/xorstr/issues/25

Which triplets are supported/not supported? Have you updated the CI baseline?
No changes.

Does your PR follow the maintainer guide?
Yes.

LGTM


Run in background so the logfile is written to

Actually, we should continue to log to stdout and stderr, as logs should be collected from the container by a process on the host.


Project Selection

Hello!
I found another bug, it happens when you try to select a project from the list. He loads the project normally, but does not have feedback from the selection to the user.
It does not have the selection effect.

hi @danielmalencar
I found it too.
I am fixing it.

I fixed it now.
please try to test again.

Perfect


benchmarks.qps_json_driver.quit Flake

https://grpc-testing.appspot.com/job/gRPC_performance_pull_requests/7801/testReport/

Hasn't happened in a while and the link contentes are gone. Closing


Highlights wrong e in line line - 'except oserror as e'

highlights the 'e' in except rather than 'as e'
this will be a issue with how the regex is performed

Fixes in pull request #10


Feature requests

persistent IMEI number
let ppl config privkey, rather than generating a new pair
Get back to the main menu from Device Registration submenu
what is different between  'Publish to IoTT Portal' and 'Publish to IoTeX Blockchain'? Should we remove one?

updated


crash on crypto:hash

I tried to  use a binary for ubuntu and got the following error:
Internal Server Error
The server encountered an error while processing this request:
[{webmachine_util,escape_quotes,
[{error,
{error,undef,
[{crypto,hash,
[sha,
<<"\n\n  \n    \n    \n    \n    \n    \n\n    \n\n\n    \n    \n    \n\n    \n  \n  \n\n\n\n    \n    \n\n    \n  \n\n">>],
[]},
{re_wm_static,hash_body,1,
[{file,"src/re_wm_static.erl"},{line,114}]},
{re_wm_static,generate_etag,2,
[{file,"src/re_wm_static.erl"},{line,87}]},
{webmachine_resource,resource_call,3,
[{file,"src/webmachine_resource.erl"},{line,186}]},
{webmachine_resource,do,3,
[{file,"src/webmachine_resource.erl"},{line,142}]},
{webmachine_decision_core,resource_call,1,
[{file,"src/webmachine_decision_core.erl"},{line,48}]},
{webmachine_decision_core,decision,1,
[{file,"src/webmachine_decision_core.erl"},{line,543}]},
{webmachine_decision_core,handle_request,2,
[{file,"src/webmachine_decision_core.erl"},{line,33}]}]}},
"""],
[{file,"src/webmachine_util.erl"},{line,342}]},
{webmachine_decision_core,decision,1,
[{file,"src/webmachine_decision_core.erl"},{line,545}]},
{webmachine_decision_core,handle_request,2,
[{file,"src/webmachine_decision_core.erl"},{line,33}]},
{webmachine_mochiweb,loop,2,[{file,"src/webmachine_mochiweb.erl"},{line,72}]},
{mochiweb_http,headers,5,[{file,"src/mochiweb_http.erl"},{line,96}]},
{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,239}]}]
mochiweb+webmachine web server

Same here, any ideas?

Hello @eshubin @kri5, The downloadable binaries are likely out of date, but the {error,undef [{crypto,hash error points to issues with open ssl not being installed either on the system that it was built on, or the system it's running on. Your best bet at getting it running until we upload new binaries would be to compile it now from source by first installing erlang with crypto enabled http://docs.basho.com/riak/latest/ops/building/installing/erlang/ and then running make rel. That should give you the rel/riak_explorer directory with the executable at rel/riak_explorer/bin/riak_explorer.

@eshubin @kri5 I just uploaded new builds, could you try again to see if you're still getting the crypto issues?
http://riak-tools.s3.amazonaws.com/riak_explorer_darwin_amd64.tar.gz for mac or
http://riak-tools.s3.amazonaws.com/riak_explorer_linux_amd64.tar.gz for ubuntu (14.04)

New one works, thanks


feat: upgrade to TypeScript 5

Prerequisites

[X] I have read the Contributing Guidelines.
[X] I agree to follow the Code of Conduct.
[X] I have searched for existing issues that already include this feature request, without success.

Describe the Feature Request
Update the required TypeScript version to 5
Describe the Use Case
As of now, this plugin is not compatible to @stencil/core 3.3.x. @stencil/core 3.3.x. introduced a minimum requirement for TypeScript 5.
See: https://github.com/ionic-team/stencil/blob/main/package.json#L125
Describe Preferred Solution
No response
Describe Alternatives
No response
Related Code
No response
Additional Information
No response

I opened a merge request for this: https://github.com/stencil-community/stencil-eslint/pull/92

I opened a merge request for this: #92

Hopefully this can be merged soon, waiting for this MR.

Solved on #97.
Thanks for your contributions! 🙏


Release v2.4.0 containing various a11y fixes

Sorry for goal hanging - all credit for this release to @colinbm  and @36degrees.
This just bumps the version number. I don't think it will be a breaking change for most users, so I figured a minor version bump was fine. Happy to change it if people think it's time for 3.0.

Also feel free to close this if there are other changes we want in the next release that haven't merged yet.


[FEATURE REQ] Ability to skip handler execution in ServiceBusProcessor with PeekLock and Prefetch

Library name
Azure.Messaging.ServiceBus
Please describe the feature.
Currently the ServiceBusProcessor always executes the processing handler. With PeekLock and Prefetch it is though possible that the message has already exceeded the peek lock duration when the processing handler is called. In such a scenario the event handler logic would be executed only to then actually figure out the lock has already been lost.
It would be great if there would be a mode when the event handler execution is skipped and the message abandoned when the peek lock is already over. Given that is a breaking change in behavior, I guess this should be opt-in on the processor options.
Although you could argue invoking the handler in such a case really doesn't make much sense since the only outcome is the message lock has already been lost

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

Interesting, is the idea that you would want to key off of the LockedUntil property @danielmarbach?
I assume the workaround is to do something like:
async Task ProcessMessage(ProcessMessageEventArgs args)
{
  if (args.Message.LockedUntil < DateTimeOffset.UtcNow)
  {
    return;
  }
  // do stuff if the lock is still valid
}

@JoshLove-msft yep exactly. The workaround is rather simple like you  showed. I was just thinking that the processor could take care of this since it is a higher level abstraction

That's a good idea, especially for the misconfigured consumer that gets to the messages well after they have lost their lock token.
I'd suggest one addition to the processor - an event indicating what message has been skipped due to a lost lock token. When an event about skipped processing messages is raised, it could be locked to shed light on how bad of a problem it is and help instrument the configuration/code.


Update README to add git submodule instructions for vagrant workflow

The vagrant workflow was missing the instructions for pulling in dependencies before running ant which was resulting in a build error understandably:

BlocklyCompile:
     [java] Exception in thread "main" java.lang.IllegalArgumentException: File not found at: /vagrant/appinventor/blocklyeditor/../lib/closure-library/closure/goog

Can one of the admins verify this patch?


Can you add this icons like things theme

I like your theme. I am using Tokyo Hack theme with VSCode. Your theme looks like this. Congratulations. You've worked so hard.
Can you add this icons like things theme?
- [k] key
- [w] win
- [u] up
- [d] down
- [D] draft pull request
- [P] open pull request
- [M] merged pull request

@alitekdemir Thanks for the kind words and suggestion. Much appreciated.
Please check the new theme version (version 3.7.0) and let me know if it's working well for you. I added the functionality you suggested.

Please check the new theme version 3.7.1. I had to adjust the new checkbox icons to resize correctly when changing font size.

I was only able to check now due to an illness, so I apologize for the delay. I just saw it, and I'm genuinely impressed! You guys are amazing, this speed and efficiency are incredible. Your commitment to open source and the way you value your work inspire me. Thank you!

I hope you are doing well @alitekdemir. I wish you a fast recovery.
I added you on the "Thanks for the suggestions" section of the readme file.
If you have other suggestions that could be useful to improve the theme for you and others. Please let me know, if possible, I will do my best to implement it.
Thanks again for the words and for suggesting new features. Much appreciated.


research on notification : plugin

research the filter and intercepter in plugins;
the workflow of index state management in plugins (the interaction with core service and nofications)


add/edit footnotes

As a content editor, I want to add a new or edit an existing footnote and associate it with any other kind of record in the system so that I can document evidence related to assertions made elsewhere in the data.
As part of this, please also test add/create source type and add/create bibliography (which are required to create footnotes).

This looks good to me. I expanded the note for Bertha Edel.

Wanted to clarify this one.  Most records in the system have a general 'notes' field for adding whatever notes you need.  In addition to that, we have a footnote system that will let you document things in a more scholarly way.  For example, you can use this to document the source that you used to confirm someone's identity or address (e.g., for the link and note in the XML for Kaopeitzer, you can now cite the book that lists the Chinese student's name).
There is a whole section for footnotes on the main admin page, where you can define your source types, add bibliographies, and then associate footnotes from those items with other records in the systems.  I've also added footnotes directly to the person and address edit forms, because I was guessing those are the kinds of records you are most likely to footnote at this point.  You should see it if you scroll down to the bottom of the edit page.

Excellent -- thanks -- this is a good system.

@elspethgreen did anyone test adding footnotes? I don't see any in the test site.


Bug 2155403: Adding labels for Linux only and Windows only next to the "SSH" and "Sysprep"

📝 Description

Add a brief description

🎥 Demo
Before:

After:

/retest

lgtm

/lgtm


Logbook and command broken

When opening up the logbook or white (specifically white) command essence, the screen becomes blank. I don't know if this is due to conflict with other mods, but the issue stopped when I disabled the mod.

Edit: the issue with command essence no longer exists but the logbook entry issue does.
Edit: I believe the issue with command essence may be caused by a different mod, https://thunderstore.io/package/Sivelos1/SivsItems/, as someone using that mod has reported that problem.

to add more info this is most likely a mod conflict seeing as this happen with thinkinvis tiller mod and sivsitems when using this mod

Fixed!


[bug]: 'thisweek' doesn't work in the date parser

The documentation lists thisweek as an option for task filtering, as do the help pages. There are also lastweek and nextweek options. These are wonky in terms of what's considered to be next or last week, but they're accepted. However, thisweek results in the following:

This is a strange thing to overlook, but it should be relatively easy to fix, given that the other week options are in place. It'd also be nice to have thismonth, nextmonth and lastmonth parameters.

I am looking into implementing this in my fork, Ultodo, but here is how I worked around it:
I have an alias:
_yesterday='echo Thu | tr '''[:upper:]''' '''[:lower:]''
that gets me the abbreviated day name in lowercase...
Then another alias:
alias week="ultralist l duebefore:$(_yesterday)"
This is a bit convoluted, but I needed yesterday because using today results in showing the 7 days up to today, since it uses closest monday. Using yesterday gets us this week.
I hope to implement thisweek soon so that aliases are not needed.
Thanks

@sottey will your fix make lastweek cover the previous 7 days? Because I think it'd be kind of odd -- a week is normally thought of as the set of 7 different consecutive days of the week (Monday - Sunday or Sunday - Saturday) depending on locale and convention, not any 7 days.
It makes more sense to have the week start on Monday -- then thisweek is any day between the most recent (including today) Monday and the closest upcoming (including today) Sunday, lastweek is the week starting the Monday before most recent, and nextweek is the week starting the Monday after the closest upcoming Sunday.
Take a look at my fix at #259 ; I've also added the monthly options -- and by comparison, this will make weekly ones standout -- nobody thinks "last month" as the 30 days before today -- it's assumed to be the calendar month, regardless of where in the current month we are.

Hi @ltrubov ,
Yeah, that was what I did. I feel like "7 days from the most recent past Monday" makes the most sense. Your work in the input_parser was more elegant than mine so I incorporated it, thanks!
LOVE the month stuff you did. I have incorporated that as well. Thanks!


Dynamic Modal not working with vue3

Version
vue-final-modal: v3.4.3
vue: v3.2.20
OS
Mac
Steps to reproduce
Using $vfm.show(dynamicModalOptions, params) with vue3 shows the following warnings and no modal is shown. The same code was working for vue3 with combat. But after transitioning to vue3 it's not working anymore.
runtime-core.esm-bundler.js:6568 [Vue warn]: Invalid VNode type: undefined (undefined)
and
Unhandled error during execution of mounted hook
What is Expected?
No warnings and modal is shown
Link for reproducing
https://codesandbox.io/s/sharp-yalow-uiu82

https://codesandbox.io/s/adoring-turing-9ygwv
a lot of differences

in main.js you must add component
in app.vue no need to import and register modals-container
in simple-modal.vue no need to import and register vue-final-modal

Thanks a lot! It was indeed the problem that I imported and registered vue-final-modal and the modals-container unnecessarily.


Add nuget package output details to paket pack output

It turns out to be useful for certain scenarios in our case, to know the details of the nuget package generated by the paket pack in a CI setting. So we propose to add the details to the output.

thx

You are welcome


Update README.md

I've updated the python subscriber path according to the real path in the
Description
Please explain the changes you've made
Issue reference
We strive to have all PRs being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #[issue number]
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[x] The quickstart code compiles correctly
[x] You've tested new builds of the quickstart if you changed quickstart code
[x] You've updated the quickstart's README if necessary

@dairlair this change has no file, is that intentional?

@dairlair - can you provide you changes, otherwise we will close this PR. Thanks

Closing. Please reopen if you add files.


rp2040: I2cDevice

This was a cavalcade of race conditions, confusing interrupts, and pain, but I'm pretty sure it's ready to go.
I'll whip up a use example soon-ish and put that in another PR.

Looks good overall! i'd do just a few changes:

It should be called i2c slave (in the HALs we use the vendor names, and that's the name Raspberry Pi uses in the datasheet and SDK)
i'd split it into two top-level modules i2c and i2c_slave, so docs are less cluttered, for example if you look at i2c you see only the stuff needed for using i2c in master mode whcih is what most people do. Also this way it matches embassy-nrf

Renamed and split per suggestion. I also added a simple use example and did a little cleanup.
Ps. Sorry about the git noise.


Make use of generics in the standard library where possible.

We need to review the existing standard library and refactor it to use generic functions wherever possible/applicable.
Moving forward, we should be doing this as standard practice when adding stdlib functionality.

Since the creation of this issue, generics have been introduced in the standard library extensively, so I'm going to close this issue.