About the competition evaluation indicators and the rules of the competition

Thank you for answering my last question. I noticed that the accuracy evaluation index in the official website of the competition comes from the relevant code of TAP-Vid's evaluation_datasets.py. However, the STIRMetrics code does not provide the corresponding evaluation method, but only provides the calculation of epe and chamer. In addition, TAP mainly calculates points within threshold. I want to know when there will be specific code and the accuracy index of RAFT, CSRT and other models instead of epe value. In addition, I also want to know when the deadline for submitting the entire competition code is?Thank you for your reply. I hope you can contact me at any time if you have any questions！

Hi, of course! We are planning to have the deadline for submission in early September. As for accuracy code using a TAP-based threshold metric, expect it to be available by next week.


[refactor][broker ] PIP-301 Part-2: Add BrokerTimeAverageDataResources

Motivation
See pip: https://github.com/apache/pulsar/pull/21129
Modifications
Add  BrokerTimeAverageDataResources
Verifying this change

[x] Make sure that the change passes the CI checks.

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
https://github.com/AnonHxy/pulsar/pull/46

Codecov Report

Merging #21353 (6b18411) into master (1a352f1) will increase coverage by 39.73%.
Report is 11 commits behind head on master.
The diff coverage is 88.88%.

@@              Coverage Diff              @@
##             master   #21353       +/-   ##
=============================================
+ Coverage     33.49%   73.22%   +39.73%
+ Complexity    12257     3817     -8440
=============================================
  Files          1636     1888      +252
  Lines        127789   140193    +12404
  Branches      13963    15402     +1439
=============================================
+ Hits          42798   102658    +59860
+ Misses        79372    29468    -49904
- Partials       5619     8067     +2448

Flag
Coverage Δ

inttests
24.20% <55.55%> (+0.05%)
:arrow_up:

systests
24.74% <66.66%> (?)

unittests
72.53% <88.88%> (+40.52%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Files
Coverage Δ

.../pulsar/broker/resources/LoadBalanceResources.java
100.00% <100.00%> (ø)

...roker/loadbalance/impl/ModularLoadManagerImpl.java
81.57% <81.81%> (+13.92%)
:arrow_up:

... and 1530 files with indirect coverage changes


Move URLs from env to devfile

/kind feature
Which functionality do you think we should add?

[ ] odo url create should create endpoint entries into the devfile instead of creating URLs in the env file.
[ ] https://github.com/openshift/odo/pull/3665 will remove the secure flag temporarily. It should be restored and the attribute should be stored against the endpoint parameter secure
[ ] should provide option to select the path of the url
[ ] odo url list and odo url delete should list endpoints (with proper states) and delete from the devfile respectively.

Why is this needed?
This will help keep URLs in one place i.e the devfile and reduce confusion.

[ ]  odo url create should create endpoint entries into the devfile instead of creating URLs in the env file.

Some information will still need to be stored in env.yaml. Not all information can be stored in devfile. host and kind will still need to be in env.yaml.
This means that URL information will be divided into two parts. Generic, and environment specific. Generic will be in devfile.yaml env specific in env.yaml.
Odo will need a reliable way to pair endpoints information from devfile.yaml to additional info that is stored in env.yaml.

Odo will need a reliable way to pair endpoints information from devfile.yaml to additional info that is stored in env.yaml.

I think we can use the URL name as the endpoint name. We can match the names and get rest of the info from the env yaml.

We cannot use the exact endpoint name as the URL name.
For example, I have two nodejs devfile components, and currently the endpoint is defined as
      endpoints:
        - name: http-3000
          targetPort: 3000

It won't allow me to push the second project, because route/ingress name 3000-tcp already exist in the current namespace
Suggest to use <endpoint name>-<component name> as the URL name.
OR we can use endpoint name as URL name, but append the component name at the end when creating route/ingress

Suggest to use - as the URL name.
OR we can use endpoint name as URL name, but append the component name at the end when creating route/ingress

OK but we need to make sure that the original name is shown back to the user during odo url list.
The command odo url create should only create the endpoint in the first container to avoid confusion.

/priority high

The command odo url create should only create the endpoint in the first container to avoid confusion.

@mik-dass What about adding a flag to allow users to specify the container?
I'm not sure how I feel about always creating the endpoint in the first container, because it limits the user's ability to add endpoints to multiple containers (without re-ordering their devfile manually)

This issue has dependency on
https://github.com/openshift/odo/pull/3702 - APIs to modify devfile entry
https://github.com/openshift/odo/pull/3665 - url creation using devfile endpoint entry

The command odo url create should only create the endpoint in the first container to avoid confusion.

devfile parsing generate an array to store endpoint entries, the order is not guaranteed. Propose to make --container a required flag if devfile contains more than one containers.

The command odo url create should only create the endpoint in the first container to avoid confusion.

devfile parsing generate an array to store endpoint entries, the order is not guaranteed. Propose to make --container a required flag if devfile contains more than one containers.

I'm not sure about that. The problem that I have with --container is that there is no way to list containers with odo from the command line. So we are forcing the user to read devfile.yaml.
I agree that there are legitime uses for --container but I don't want to complicated users' life if we don't have to. If there is no container with dedicatedPod it won't matter where the endpoint is defined, as all containers will end up in the same Pod with shared network namespace.
What if we do compromise.

If there is a container that has dedicatedPod: true odo url create will error out with a message explaining that you need to use --container flag.
If there is no container with dedicatedPod: true  odo will create the endpoint on the first container. --container will be optional even if there multiple containers. If user really wants to create an endpoint for a specific container it will be possible.

Blocked by PR #3702

This issue has dependency on
#3702 - APIs to modify devfile entry

@yangcao77 Why is this blocked by #3702 ?

Blocked by PR #3702

this PR was merged
/remove-status blocked

@yangcao77 It might be a better idea to handle to handle list and describe in a different PR. I can see an existing issue https://github.com/openshift/odo/issues/3615 for them. Once the URLs are moved, somebody can pick up one of them and finish it in parallel. This will break our existing tests but we can comment them out for now.

I have this issue and #3615 implemented already, but I'm still working on unit tests and integration tests for it.
In case you want to review the PR beforehand, I have created a draft PR:
https://github.com/openshift/odo/pull/3857
@mik-dass @girishramnani @kadel


chore: Revert controler runtime 0.19.3 to 0.19.2

Description
Changes proposed in this pull request (what was done and why):

Changes refer to particular issues, PRs or documents:

Traceability

[ ] The PR is linked to a GitHub issue.
[ ] The follow-up issues (if any) are linked in the Related Issues section.
[ ] If the change is user-facing, the documentation has been adjusted.
[ ] If a CRD is changed, the corresponding Busola ConfigMap has been adjusted.
[ ] The feature is unit-tested.
[ ] The feature is e2e-tested.

This PR was for test purposes and will be closed


Workerd SSR issues

Hello!
I opened an issue in the nuxt-icon module recently about this problem.
It uses the loadIcon() method from @iconify/core which causes problems when rendering our sites on Cloudflare Workers.
There is a limitation in the worker runtime where promises created in one request, cannot be referenced in another.
My guess is when multiple workers start/render in the same region, and request the same icons they will end up awaiting promises that were created in another context.
When this happens it results in a fatal error in the Worker itself, and there is no way to catch that in the application.
This is relatively rare, but we experienced more than 250 failed requests daily because of this on a high traffic site.
I made a minimal reproduction for that issue: https://github.com/zsilbi/nuxt-icon-workerd
Then I added a seperate test that calls only the loadIcon() method once in a worker wihout Nuxt, but this way the worker instantly throws an error on every request:
✘ [ERROR] A hanging Promise was canceled. This happens when the worker runtime is waiting for a Promise
from JavaScript to resolve, but has detected that the Promise cannot possibly ever resolve because all code
and events related to the Promise's I/O context have already finished.

My current workaround is to use the icons only on the client side, but I hope there is a solution to this.
Thanks,
zsilbi

Icon is not rendered on server side anyway, it is rendered only when component is mounted, so using it as client only component does not change anything. It behaves that way precisely because of SSR to avoid breaking hydration as it is designed to be a client only component.
Solution is to switch to iconify-icon package instead of @iconify/vue. It is a web component, which solves SSR shenanigans.
See https://github.com/nuxt-modules/icon/issues/139


handle bad privateCert

trap exceptions thrown by signRequest which can occurr when an invalid
privateCert is passed to the saml object. Instead of throwing an
exception pass the error along via the supplied callback
added spec to check that the callback his hit with the error condtion when
calling requestToUrl on the saml object
Address issue: https://github.com/bergie/passport-saml/issues/230

I ran into this issue today. Thanks for the patch.


Broken shares since anniversary update

First, thank you for this fantastic product. I just upgraded to 14393 (the Windows 10 anniversary update) and upgraded all my desktops to 1.6.1 with the current ini, and my connections are all working. However, I'm now having trouble with my network shares on every desktop. Although File Explorer still shows all mapped drives, they now appear with a red X in the icon. CMD net use shows no mapped drives (or that the drive is unavailable), yet attempting to remap one of the drives returns system error 85 and says the local name is already in use. Copying files seems to work fine, and executing msi's from File Explorer works, but trying to run a program from a mapped drive in File Explorer now results in "Windows cannot access " with error code 0x800704b3 (invalid network path). This is a new behavior that only started after the upgrades. Any help is appreciated.
UPDATE
Turning off ProtectionMode fixes the problem (after a reboot). I'm not sure why this is a problem all of a sudden since ProtectionMode has been turned on by default since Vista. I doubt this is an optimal solution, so I'm still looking forward to a response.
ProtectionMode key:

HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\ProtectionMode=dword:00000000

/UPDATE

It works, thank you!

I have the same issue and the ProtectionMode works.  However I still get red Xs by all of the network shares until I use them.  But I am able to access them without problems.  But I have seen this issue before with other versions of Windows.

Closed as solved. If not - reopen it.


search.java issues

would like to solve this issues #301 and #302.

This is a nonsense pull request. Please review the wiki contributing  page before submitting further pull requests.


OS#16244108: Small refactor of Parser::CreateCallNode and Parser::CreateSuperCallNode

https://microsoft.visualstudio.com/OS/_workitems/edit/16244108
The uninitialized field was introduced by https://github.com/Microsoft/ChakraCore/pull/3917. The only read of the field is in EmitArgList, and if it ends up "true" instead of the default "false" an extra defensive load will be emitted for the constructor parameters so not a security/correctness concern.

It looks like this has had some semantic changes; the "hello world" test we run on release builds is failing with
11:23:56 SyntaxError: Declaration outside statement context
11:23:56 	at code (hello.js:6:13)


Add setup/teardown for port forwarding via firewalld

Not quite working yet, but firewalld accepts the config, and that's good enough for me to push this.

Stripping WIP, this is working, remaining work is on the firewall side

validate is also not happy

@mheon What is the state here, you have lint issues.

Mostly focused on other PRs (getting iptables working w/ firewalld in the picture), but this can still go in despite that. I'll clean up the lint issues and get this ready for merging this afternoon.

Now allows iptables backend on systems with firewalld, and makes iptables the default unless explicitly overidden

If tests go green, this is ready

Tests are complaining because of a string compare. Let me fix...

Repushed. @Luap99 @baude PTAL

This is ready

Will this work with firewalld 1.1? E.g. should include a version check for firewalld and use the firewalld code when >= 1.1?

It should, but 1.1.0 has not been released yet, and I don't want to add a check for something that doesn't exist yet and thus can't be tested.

@mheon There are few block_on I am fine if its intentional but if netlink part is not dependent on firewall stuff then we should have any reasons to block but if its vice-versa then I think its good.

@mheon There are few block_on I am fine if its intentional but if netlink part is not dependent on firewall stuff then we should have any reasons to block but if its vice-versa then I think its good.

This is already explained by @mheon in above comment.

Anyone want to merge?

LGTM @baude PTAL

/lgtm


NON-CRITICAL: Playground Settings > Disable Definition Files breaks many plugin tabs

Page URL: https://www.typescriptlang.org/play?
Issue: Disable Definition Files breaks many plugin tabs
Step 1: Enable plugins, Preitter, Format on Save, (I also have TypeScript Json Schema)

Step 2: Observe the plugin menu and that everything works

Step 3: Go to Settings and disable Definition Files, And refresh the page

Step 4: Observe Prettier Tab is visible but unselectable,
Step 5: Observe Format on Save is missing

Something about "process is not defined" in tsWorker.js

The team doesnt track non-critical issues on this repo anymore, but it sounds like you want to raise this (or fix it) on the prettier plugin repo anyway as that plugin doesn't seem to handle that setting elegantly.


Fails to install on windows using node V4.2.4 and npm v3.2.1

Fails installing hiredis so not sure if I should report it there or here:

gyp info it worked if it ends with ok
gyp verb cli [ 'C:\\Program Files\\nodejs\\node.exe',
gyp verb cli   'C:\\Users\\kturner\\AppData\\Roaming\\npm\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js',
gyp verb cli   'rebuild' ]
gyp info using<EMAIL_ADDRESS>gyp info using<EMAIL_ADDRESS>| win32 | x64
gyp verb command rebuild []
gyp verb command clean []
gyp verb clean removing "build" directory
gyp verb command configure []
gyp verb check python checking for Python executable "python2" in the PATH
gyp verb `which` failed Error: not found: python2
gyp verb `which` failed     at F (C:\Users\kturner\AppData\Roaming\npm\node_modules\npm\node_modules\which\which.js:78:19)
gyp verb `which` failed     at E (C:\Users\kturner\AppData\Roaming\npm\node_modules\npm\node_modules\which\which.js:82:29)
gyp verb `which` failed     at C:\Users\kturner\AppData\Roaming\npm\node_modules\npm\node_modules\which\which.js:93:16
gyp verb `which` failed     at FSReqWrap.oncomplete (fs.js:82:15)
gyp verb `which` failed  python2 [Error: not found: python2]
gyp verb check python checking for Python executable "python" in the PATH
gyp verb `which` failed Error: not found: python
gyp verb `which` failed     at F (C:\Users\kturner\AppData\Roaming\npm\node_modules\npm\node_modules\which\which.js:78:19)
gyp verb `which` failed     at E (C:\Users\kturner\AppData\Roaming\npm\node_modules\npm\node_modules\which\which.js:82:29)
gyp verb `which` failed     at C:\Users\kturner\AppData\Roaming\npm\node_modules\npm\node_modules\which\which.js:93:16
gyp verb `which` failed     at FSReqWrap.oncomplete (fs.js:82:15)
gyp verb `which` failed  python [Error: not found: python]
gyp verb could not find "python". guessing location
gyp verb ensuring that file exists: C:\Python27\python.exe
gyp ERR! configure error
gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable.
gyp ERR! stack     at failNoPython (C:\Users\kturner\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\lib\configure.js:401:14)
gyp ERR! stack     at C:\Users\kturner\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\lib\configure.js:356:11
gyp ERR! stack     at FSReqWrap.oncomplete (fs.js:82:15)
gyp ERR! System Windows_NT 10.0.10240
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\kturner\\AppData\\Roaming\\npm\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Users\kturner\repos\rns-node\node_modules\hiredis
gyp ERR! node -v v4.2.4
gyp ERR! node-gyp -v v3.2.1
gyp ERR! not ok
npm verb lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
npm verb lifecycle<EMAIL_ADDRESS>PATH: C:\Users\kturner\AppData\Roaming\npm\node_modules\npm\bin\node-gyp-bin;C:\Users\kturner\repos\rns-node\node_modules\hiredis\node_modules\.bin;C:\Users\kturner\repos\rns-node\node_modules\.bin;C:\ProgramData\Oracle\Java\javapath;C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Intel\iCLS Client\;C:\Program Files\Intel\iCLS Client\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Windows Live\Shared;c:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\IBM\Client Access\Emulator;C:\Program Files (x86)\IBM\Client Access\Shared;C:\Program Files (x86)\IBM\Client Access\;C:\Program Files (x86)\GnuWin32\bin;C:\Program Files\TortoiseSVN\bin;C:\Program Files\TortoiseGit\bin;C:\Program Files\010 Editor;C:\Program Files (x86)\Skype\Phone\;C:\Program Files\nodejs\;C:\Program Files (x86)\Heroku\bin;C:\Program Files (x86)\git\cmd;C:\Program Files (x86)\Git\cmd;C:\Users\kturner\AppData\Local\Pandoc\;C:\Program Files (x86)\Microsoft VS Code\bin;C:\Users\kturner\AppData\Roaming\npm
npm verb lifecycle<EMAIL_ADDRESS>CWD: C:\Users\kturner\repos\rns-node\node_modules\hiredis
npm info lifecycle<EMAIL_ADDRESS>Failed to exec install script
npm verb unlock done using C:\Users\kturner\AppData\Roaming\npm-cache\_locks\staging-b3da145b0915bc0d.lock for C:\Users\kturner\repos\rns-node\node_modules\.staging
<EMAIL_ADDRESS>C:\Users\kturner\repos\rns-node
└── (empty)

npm verb stack Error<EMAIL_ADDRESS>install: `node-gyp rebuild`
npm verb stack Exit status 1
npm verb stack     at EventEmitter. (C:\Users\kturner\AppData\Roaming\npm\node_modules\npm\lib\utils\lifecycle.js:232:16)
npm verb stack     at emitTwo (events.js:87:13)
npm verb stack     at EventEmitter.emit (events.js:172:7)
npm verb stack     at ChildProcess. (C:\Users\kturner\AppData\Roaming\npm\node_modules\npm\lib\utils\spawn.js:24:14)
npm verb stack     at emitTwo (events.js:87:13)
npm verb stack     at ChildProcess.emit (events.js:172:7)
npm verb stack     at maybeClose (internal/child_process.js:818:16)
npm verb stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
npm verb pkgid<EMAIL_ADDRESS>npm verb cwd C:\Users\kturner\repos\rns-node
npm ERR! Windows_NT 10.0.10240
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\kturner\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "install" "busmq" "--save" "--verbose"
npm ERR! node v4.2.4
npm ERR! npm  v3.5.2
npm ERR! code ELIFECYCLE

npm ERR<EMAIL_ADDRESS>install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the hiredis package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs hiredis
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls hiredis
npm ERR! There is likely additional logging output above.
npm verb exit [ 1, true ]

npm ERR! Please include the following file with any support request:
npm ERR!     C:\Users\kturner\repos\rns-node\npm-debug.log
npm ERR! code 1

I think I am stuck.  I can install Python 2 but then it fails to build hiredis due to a dependency on c++11 :(

Can you try cloning hiredis repo and building it? If it fails then open an issue there.
Which version of python 2 are you using?
Alternatively, you can clone node-busmq, remove hiredis from the deps in package.json and rebuild.
It should work without hiredis as well.

I prefer your second option and I am happy to try it.   Will there be any negative impact on your solution without hiredis?
By the way, I installed Python 2.7.11

Shouldn't be anything too significant. hiredis is used for improved parsing for the protocol transfer, so it depends on how much data you're planning on transferring.
If you can update when you get it working without hiredis, I'll close the issue.

When you say "rebuild it" what do you mean exactly?
I have cloned the git repo into node_modules/busmq, renamed the .git folder, removed the hiredis dependency and then run npm install (successfully).  Is that it?

yep, that should do it.

OK - it works fine.
I have a question - although perhaps not relevant to this log.
Is it possible to enqueue messages with a key, such that a consumer can only pick up messages with that key?
The scenario is that a client can send a message.  Any number of several consumers might pick up the message.  The response must only be available to the original client.   Possible?

This is currently not a built-in feature.
However, a simple solution would be that every client creates a unique "response" queue that only he will be consuming from. The message the client sends will contain the response queue name, and the responder will simply push the response to the correct queue.
Makes sense?

Yes this was exactly my intention. My only concern was whether or not queue creation was an expensive process, as it will be happening hundreds of times a minute across the system. As an aside, due queues expire after a period of inactivity, or after a restart?

creating queues is more expensive than just using them. I haven't performed any benchmarking through, so I suggest you test it out.
queues expire after a defined the TTL passes without any clients attached to the queue. As long as there is at least one client attached, the queue will not expire. Restart does not expire the queues.


DOCS-439: MinIO Console refresh

Closes #439
Summary
Refresh the Console docs with new screenshots
Remove as many extraneous screenshots as possible to reduce burden of maintenance
Update a few tutorials that were making reference to outdated screenshots
Remove unused images entirely
use optipng to optimize new screenshots
See #minio-docs for the staged view.

Bucket-versioning.rst
Line 291 and following. This is the "enable versioning" set of instructions through the CLI, but it refers to "suspend". Likely a copy/paste error.

Bucket-versioning.rst
Lines 258-259 and lines 306-311 should be the same. They discuss null version ID for objects created while versioning is disabled.
Consider making them the same note. Maybe a footnote that's referred to from both places?

Also Fixed #464 .


Set macos-13 runner

Just for testing

Closing because did not improve anything and 13 is still beta


Disallow graphiql and storybook in robots.txt

Coverage decreased (-0.007%) to 94.648% when pulling 76ca56d3136b06957579ef9baa2185c76e0bd4b0 on cody-docs-robots-txt into ac7e64fa469f98fcafc77c9537c93339266846d3 on main.


Add Vijay as a contributor

Current Behavior
@vijcheru is a new community contributor.
Desired Behavior
A profile for @vijcheru should be created and visible on /community.

@vijcheru is up! Haha! 💥


Add automatic light/dark option for the colorblind theme

The normal themes already have a variant which automatically chooses light/dark mode based on the browser.
This PR adds the same variant, but for the colorblind themes.

I don't like these theme names but it's not the fault of this PR as it's consistent.

@silverwind offtopic, but: That is the scientific name after all.
It may not be the most descriptive one, but it at least explains exactly what it is intended for…


add different port option

Can you please add an option that the api can run on another port.
i would like to run carlaviz behind a reverse proxy and https without having to release port 8080.

Sure, that should be simple.
By the way, this application also needs to export port 8081 to let the frontend communicate with backend as well. If you want to use the drawing functionality, it also needs 8089 port. I am thinking of adding a config file to change these settings.

thank you very much.
normal white you solve this by a subdir
e.g.
hostname/ = gui
hostname/api = communication to backend
hostname/draw_api = drawing communication
you only have to open one port, in my case port 443, so that I can run everything encrypted and without certificate errors via https

Although this is an old issue, I think we can resolve this by adding reverse proxy. Port customization is added in https://github.com/mjxu96/carlaviz/pull/62


ASN.1 encoder/decoder replacement

Issue created from the old "Forthcoming features" section of the roadmap as per OMC vote.
The current ASN.1 code needs an overhaul/rewrite.

There are a few possibilities:

Switch to an imperative style, as BoringSSL uses
Use a script to generate calls to the existing macros
Use a script to generate imperative calls


Icon request: Handshake

URL for the brand / site / app
https://handshake.org/
Logo resources for the icon
https://handshake.org/images/landing/logo-dark.svg
Anything else?
No response

Here you go!
https://github.com/aegis-icons/aegis-icons/blob/master/SVG/Handshake.svg
https://github.com/aegis-icons/aegis-icons/blob/master/SVG/.Variations/Handshake bg.var.svg

:question: How to add icon(s) to Aegis?
:star: Support this project by giving a star! Just adding like to this comment is also appreciated.


It is not possible to use values from value converters in expressions

I'm submitting a feature request

What is the expected behavior?
It should be possible to use converted values just like any other value in expressions.

What is the motivation / use case for changing the behavior?
Please find below some self-explanatory (I hope) examples that are possible with Angular filters. In Aurelia, all of them throw Parser Error.

${ (myEntity.children | activeOnly).length }
${ (myEntity | isEntityActive) ? 'ACTIVE' : 'INACTIVE' }
<span if.bind="!(myEntity | isActive)">`
${ (myEntity.title | inCurrentLanguage) || 'No title' }

In the mean time, you could use some trickery, like:
<p ref="myP" is-active="${myEntity | isEntityActive}">
   ${ myP.isActive ? 'ACTIVE' : 'INACTIVE' }
</p>

I don't see us making this change to the parser any time soon. The solution from @fabioluz (and other similar ideas) is our recommendation currently.  We've talked about adding a let attribute to the templating language to make this a bit easier at some point in the future.


Add function to see all marked messages across folders

Checklist

[X] I have used the search function to see if someone else has already submitted the same feature request.
[X] I will describe the problem with as much detail as possible.
[X] This issue only contains a request for one single feature, not multiple (related) features.

App version
6.000
Problem you are trying to solve
As user I want to see all with star marked messages unified in one view. That should be done across folders and accounts. But with filter functions I can specify the displayed messages.
Related question: https://forum.k9mail.app/t/how-to-see-all-marked-messages/4740
Suggested solution
Add below the "unified inbox" a new "all marked messages" button. When the button is tapped, the interface should show all marked messages from all accounts and folders together. In the top menu there should be filter options, that are saved permanently.
Screenshots / Drawings / Technical details

This functionality can be achieved once the following features have been added:

#4513
#3398


nixos/plymouth: Add label plugin and a font to the initrd

Motivation for this change
This allows Plymouth to show the “NixOS 21.03” label under the logo at startup like it already does at shutdown.
Fixes #59992.
Increases the compressed initrd size by about 5 MB when Plymouth is enabled, since /etc/plymouth/plugins/label.so depends on rather more libraries than you’d like. Maybe this is fine since Plymouth is opt-in. We might be able to trim this by using a copy of Cairo compiled against fewer backends? A more minimal version of the label plugin was proposed at https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/45.
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Nice! This has been bugging me for literally years.
I wonder if the font should be controlled by some option. What determines the font that gets used during shutdown? Should we try and make sure it's the same one?

I'd be fine with using the label-ft patches in plymouth, however... there is a PR that fixes this and overhauls a lot of plymouth https://github.com/NixOS/nixpkgs/pull/84158. But the issue with it is it aspires to do slightly too much in one PR (mostly the commonFunction pieces breaking things)
I'm planning on fixing up that PR and then subsequently defaulting to the bgrt theme. Flicker free boot is blocked on https://github.com/NixOS/nixpkgs/pull/74842 and that is a long ways to being ready.

I am however interested in why https://github.com/NixOS/nixpkgs/pull/84158/commits/3128d14a710efbf6cdfc3f3347b65e34291c5aaa is different from what you have...

The difference is that 3128d14a710efbf6cdfc3f3347b65e34291c5aaa (#84158) uses the label-ft plugin via a patch (6502fffaddbc9e30a2cb5b38ecb3131d1f04144e) that’s still not merged upstream (https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/45). Plus side: it uses Freetype directly, so it can get away without pulling in 5 MB of libraries and needing a fontconfig configuration. Minus side: there seems to have been no upstream activity toward merging that for 4 years.

@jtojnar Does your reservation on using those patches still stand from https://github.com/NixOS/nixpkgs/pull/84158#discussion_r407623151 with this in context? If so, I'd defer to that decision and merge this with a font option

5 MB increase does not sound that bad to me so I would still prefer the upstream label solution over unmerged patches. But initrd maintainers will have final say. We can try to slim down cairo as suggested above it they see it as a problem.

Okay, I added an option for the font file.
It’s a little weird in that the theme actually decides which font to request from Fontconfig, and this option only affects which font file is made available to Fontconfig during boot to satisfy this request. During shutdown, the normal system Fontconfig configuration and fonts are used.
I set the default as DejaVu Sans because it has the privileged position of being our Fontconfig fallback font:
https://github.com/NixOS/nixpkgs/blob/9816b99e71c3504b0b4c1f8b2e004148460029d4/pkgs/development/libraries/fontconfig/default.nix#L87
If the user adds noto-fonts to config.fonts.fonts, they’ll actually get Noto Sans during shutdown because that’s what our default breeze theme specifies. Those users can configure boot.plymouth.font = "${pkgs.noto-fonts}/share/fonts/truetype/noto/NotoSans-Regular.ttf" for a matching font during boot.


Fix the user agent entry to avoid nested parens.

Description
Fixes the user agent entry to avoid nested parens.
The full user agent was like PyDatabricksSqlConnector/2.0.2 (dbt-databricks/1.2.0 (dbt-cloud)), but we should avoid nested parens.
The full user agent after the fix will be like PyDatabricksSqlConnector/2.0.2 (dbt-databricks/1.2.0; dbt-cloud).

Thanks! merging.


[9.x] Adds compileOld function

This PR makes accessing the old input value easier like so,
Old version
<input type="text" name="name" class="form-control" value="{{ old('name', 'defalut_value') }}">

New version
<input type="text" name="name" class="form-control" value="@old('name', 'defalut_value')">

Echo() is prone to XSS, the output of old() function must be escaped

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.


linter-flake8 not doing anything

I did pip install flake8 and apm install linter-flake8, but nothing comes up in Atom. I'm on a Mac. I noticed a lot of fixes about changing the executable path, but I have no idea how to change that/get that correct if that's the issue

same problem

@linjonathan2001 , and @amclouds your problem  will be fixed after following my steps in this link;  Fix-Linter-flak8.


I can't authenticate when it involves microsoft azure

Fatal error: Uncaught exception 'League\OAuth2\Client\Provider\Exception\IdentityProviderException' with message 'Bad Request' in /Applications/MAMP/htdocs/adobesignwp/wp-content/plugins/Gravity2PDF/lib/vendor/stevenmaguire/oauth2-microsoft/src/Provider/Microsoft.php:57 Stack trace: #0 /Applications/MAMP/htdocs/adobesignwp/wp-content/plugins/Gravity2PDF/lib/vendor/league/oauth2-client/src/Provider/AbstractProvider.php(644): Stevenmaguire\OAuth2\Client\Provider\Microsoft->checkResponse(Object(GuzzleHttp\Psr7\Response), Array) #1 /Applications/MAMP/htdocs/adobesignwp/wp-content/plugins/Gravity2PDF/lib/vendor/league/oauth2-client/src/Provider/AbstractProvider.php(560): League\OAuth2\Client\Provider\AbstractProvider->getResponse(Object(GuzzleHttp\Psr7\Request)) #2 /Applications/MAMP/htdocs/adobesignwp/wp-content/plugins/Gravity2PDF/class/gravity_merge_integrations.class.php(155): League\OAuth2\Client\Provider\AbstractProvider->getAccessToken('authorization_c...', Array) #3 [internal function]: Gravity_Merge_Integrations->setO in /Applications/MAMP/htdocs/adobesignwp/wp-content/plugins/Gravity2PDF/lib/vendor/stevenmaguire/oauth2-microsoft/src/Provider/Microsoft.php on line 57

This package is for Microsoft Live. Azure support is provided with a different package.
https://github.com/thenetworg/oauth2-azure


Makefile Doesn't Build Protocols

"Nothing to be done for 'proto'", and yet if you manually go in and build each protocol, you get a rebuild.
This is probably b/c of the way we use bash in the loop.
TODO/RESOLVE: Update to wildcard schema rules, like when we extract uttu.

Forced it w/ a phony rule.


Start migrating lists that are ready from FlatList to FlashList

Problem
While FlatList is suitable for typical use cases, our goal is to achieve the highest level of app performance, especially when dealing with extensive lists, such as Chats, Threads, Workspaces, Reports, and specific Money Threads.
Solution
To address this performance challenge, switch from FlatList to FlashList. By making this transition, we anticipate a significant performance improvement of approximately 2x.
Next Steps
Some lists are ready to migrate to FlashList, some are not (e.g. ChatList). @roryabraham can you list the ones ready to migrate out here?
[LISTS READY TO MIGRATE TO FLASHLIST]
Then let's work through the list of lists and get them migrated.

Hi, I am Adam from Callstack, an expert contributor group. I’d like to work on this :)

@roryabraham to confirm: any payments due here?

Nope

This has been split up so I'm closing it out


Slurm adaptor incompatible with Cartesius

as reported by @benvanwerkhoven, the slurm version on the Cartesius is no longer compatible with Xenon:
Caused by: nl.esciencecenter.xenon.IncompatibleVersionException: slurm adaptor: Slurm version 14.11.6-Bull.1.0 not supported by Slurm Adaptor. Set xenon.adaptors.slurm.ignore.version to ignore
at nl.esciencecenter.xenon.adaptors.slurm.SlurmSetup.checkVersion(SlurmSetup.java:70) ~[xenon-1.1.0-beta.1.jar:na]
at nl.esciencecenter.xenon.adaptors.slurm.SlurmSetup.(SlurmSetup.java:47) ~[xenon-1.1.0-beta.1.jar:na]
at nl.esciencecenter.xenon.adaptors.slurm.SlurmSchedulerConnection.getConfiguration(SlurmSchedulerConnection.java:311) ~[xenon-1.1.0-beta.1.jar:na]
at nl.esciencecenter.xenon.adaptors.slurm.SlurmSchedulerConnection.(SlurmSchedulerConnection.java:262) ~[xenon-1.1.0-beta.1.jar:na]
at nl.esciencecenter.xenon.adaptors.slurm.SlurmSchedulerConnectionFactory.newSchedulerConnection(SlurmSchedulerConnectionFactory.java:16) ~[xenon-1.1.0-beta.1.jar:na]
at nl.esciencecenter.xenon.adaptors.scripting.ScriptingJobs.newScheduler(ScriptingJobs.java:109) ~[xenon-1.1.0-beta.1.jar:na]
at nl.esciencecenter.xenon.engine.jobs.JobsEngine.newScheduler(JobsEngine.java:49) ~[xenon-1.1.0-beta.1.jar:na]

See also #236

Also incompatible with slurm on DAS-5

Wrong button, sorry!

With the ignore property passed to newScheduler instead of newXenon and the addition of a line to ignore in the output of "scontrol show config" the SlurmAdaptor is working again on Cartesius.

With the ignore property passed to newScheduler instead of newXenon and the addition of a line to ignore in the output of "scontrol show config" the SlurmAdaptor is working again on Cartesius.

We still need to "officially" start supporting the version of Slurm on the Cartesius and DAS-5. The "ignore version" is only a temporary workaround, not an actual fix.

I will test the Cartesius version next.

Cartesius version work. Like DAS5 there are several timing issues which are essentially bugs in the test themselves. For example, we should wait for output files to appear before trying to read them.
Some of these issues in the test where fixed, but others may pop up later...
Also added a few slurm jobs states that we had not seem before. We should also be ready for slurm 15 now.


Can't start receiving notifications?

The error refers to "The attribute cannot be written.". Have you tried subscribing to notifications for another characteristic? Is the device paired?

I got this error because of a mistake I made on the device. I have an ESP32-C3 and forgot this line when setting up the Bluetooth server:
pCharacteristic->addDescriptor( new BLE2902() );

Without that descriptor GattCharacteristic.WriteClientCharacteristicConfigurationDescriptorAsync would fail on Windows with System.Exception: The attribute cannot be written
A more complete example:
static BLEServer *s_pServer = NULL;
static BLECharacteristic *pCharacteristic = NULL;

BLEDevice::init( "My Device" );
s_pServer = BLEDevice::createServer();

BLEService *pService = s_pServer->createService( SERVICE_UUID );

pCharacteristic = pService->createCharacteristic(
    CHARACTERISTIC_UUID,
    BLECharacteristic::PROPERTY_READ |
        BLECharacteristic::PROPERTY_NOTIFY );

// Without this descriptor, the client might error "The attribute cannot be written."
// After adding this I had to change the UUID and forget and re-pair the device, so
// no cached connection info was used:
pCharacteristic->addDescriptor( new BLE2902() );

pCharacteristic->setValue( "Hello world!" );


Fix typo in playerdata/quickstart

"medthod" to "method"

Thank you @felipesflisboa for submitting a change to the docs.


refactor(all): better discover-ability, files re-org

This PR focuses on re-organizing files and classes to make it easier to discover. Along with linting fixes and big function breakdown, such as _buildNavigationPlan in navigation-plan.ts
Another refactoring target was to have more local variables over long property chain access with verbose name, this should help greatly with minification.
After this, the focus will be fixing bug and incorporating existing PRs
@EisenbergEffect @davismj @fkleuver
Also add an overload for NavigationInstruction.prototype.addViewPortInstruction to accept an options object, to open a path for future feature related to static view model. It looks like this
  /**
   * Adds a viewPort instruction. Returns the newly created instruction based on parameters
   */
  addViewPortInstruction(initOptions: ViewPortInstructionInit): /*ViewPortInstruction*/ any;
  addViewPortInstruction(viewPortName: string, strategy: ActivationStrategyType, moduleId: string, component: any): /*ViewPortInstruction*/ any;
  addViewPortInstruction(
    nameOrInitOptions: string | ViewPortInstructionInit,
    strategy?: ActivationStrategyType,
    moduleId?: string,
    component?: any
  ): /*ViewPortInstruction*/ any;

@bigopon I'm confused as to why we're still targeting master and not develop.

@EisenbergEffect i forgot that. Switched target

Excellent. Thanks! @bigopon Is there also a templating-router PR we need to merge for that release? Is it targeting the correct branch?

The PR is here https://github.com/aurelia/templating-router/pull/88 .

Thank you :)


Default value of a filter type is not true, but is checkbox.selected()

This fixes the exclusive setting of maximizer having checkboxes ticked wrongly

Can you make a regression test for this?


Machines not visually connecting with other mods' pipes

The Mekanism machines dont seem to visually connect with cables near them. This only happened when logging in again on a Server, not when placing them. Found this already at the induction Matrix with a cryo-stabilzed Fluxduct (Thermal Expans
ion) at the induction port and at the Solar Evaporation Valve with a Transfer Pipe (Extra Utilities). The bug is only visually, the induction Matrix still gets power from the cable and the solar Evaporation plant still gets in water.

This should be fixed for v9.


feat(glog): add log rotation support for short-running process

1.add file pattern matching detection for log rotation and backup file limitation:
before this commit:
log rotation is not working on short-running process
2.backup file limitation will working on all files matching pattern:
before this commit:
access-{y-m-d}.log will generate log like:
access-2023-05-19.log
access-2023-05-18.log
the limitation only working on rotation files like "access-2023-05-19.xxxxxxxxxxxx.log" , not counting the "access-2023-05-18.xxxxxxxxxxxxx.log"

@xuyue86 你这样改动确实能解决日志文件滚动的问题，但会额外引发性能问题，因为每一次写日志都会触发滚动逻辑。

We have this condition，I think it will only triggered the first time when calling print.
if !l.config.rotatedHandlerInitialized.Val() && l.config.rotatedHandlerInitialized.Cas(false, true) { 			l.rotateChecksTimely(ctx) 			intlog.Printf(ctx, "logger rotation initialized: every %s", l.config.RotateCheckInterval.String()) }

Codecov Report
Patch coverage: 70.68% and project coverage change: -0.05 :warning:

Comparison is base (aa8eabd) 78.88% compared to head (b0d0e9b) 78.83%.

:exclamation: Current head b0d0e9b differs from pull request most recent head 18bd3fa. Consider uploading reports for the commit 18bd3fa to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2658      +/-   ##
==========================================
- Coverage   78.88%   78.83%   -0.05%
==========================================
  Files         631      631
  Lines       51784    51790       +6
==========================================
- Hits        40848    40828      -20
- Misses       8913     8938      +25
- Partials     2023     2024       +1

Flag
Coverage Δ

go-1.15-386
78.85% <70.68%> (?)

go-1.15-amd64
78.84% <70.68%> (-0.07%)
:arrow_down:

go-1.16-386
78.84% <70.68%> (?)

go-1.16-amd64
78.87% <70.68%> (-0.01%)
:arrow_down:

go-1.17-amd64
78.86% <70.68%> (-0.05%)
:arrow_down:

go-1.18-386
?

go-1.18-amd64
78.81% <70.68%> (-0.03%)
:arrow_down:

go-1.19-386
?

go-1.19-amd64
78.85% <70.68%> (-0.06%)
:arrow_down:

go-1.20-386
?

go-1.20-amd64
78.82% <70.68%> (-0.06%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

os/glog/glog_logger_rotate.go
61.23% <70.17%> (-2.12%)
:arrow_down:

os/glog/glog_logger.go
73.33% <100.00%> (-2.97%)
:arrow_down:

... and 2 files with indirect coverage changes

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


Wrong text:  Linux container

https://docs.microsoft.com/en-us/azure/app-service/app-service-web-tutorial-dotnetcore-sqldb#create-a-web-app
You’ve created an empty web app in a Linux container, with git deployment enabled.
This is the Windows documentation

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

ID: 00961883-36eb-f736-b906-73d4c35e69b0
Version Independent ID: 3a2fd493-9682-eedf-fad1-571b9391cd46
Content: Build a .NET Core and SQL Database web app in Azure App Service
Content Source: articles/app-service/app-service-web-tutorial-dotnetcore-sqldb.md
Service: app-service-web
GitHub Login: @cephalin
Microsoft Alias: cephalin

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

Hey @evertonmc - Thank you for reporting this! We have removed the callout text and the change will reflect after our next merge; and this issue will auto-close. Again, thank you for your contribution!


Develop

[feat(adaptesr): implement Axios adapter for HTTP requests]

[feat(core): create movie entity and associated hook]

[feat: add use-cases for fetching popular, top-rated, and upcoming movies]

[feat: add pagination support to movie fetch functions and pass as Fla…]

[feat: add movie details fetching and display components]

[feat: loading animations]

[1.1.0]

review code in progress


[x] fix broken images on artificial-intelligence page

Figure: Broken tech card image
[x] fix broken images on chinafy page

Figure: Broken tech card images
[x] fix broken images on hololens page

Figure: Broken tech card images
[ ] fix broken images on kubernetes page

Figure: Broken tech card images
[x] fix broken images on mobile application development page

Figure: Broken tech card images

Figure: Broken tech card images

Figure: Wrong logo on tech card
[x] fix broken images on remote work page

Figure: Broken tech card images

Figure: Broken tech card images

Figure: Broken tech card images
[x] fix broken images on windows desktop apps page

Figure: Broken tech card images
[x] fix broken images on scrum page

Figure: broken image
[x] fix broken images on pay per click page

Figure: broken image
[x] fix broken images on remote work page

Figure: broken image

[x]  fix broken images on chinafy page

Figure: Broken tech card images

For Chinafy, the page doesn't actually have Images on it. I've updated the Tech component to allow components without Images

It seems like we must define a width and height for the Image in the technology component, which ends up with the stretched out images. It isn't ideal


get JSON representation of binlog's WriteRowsEvent

Hello :)
I'm trying to push mysql binlog events into a postgres table (weird, I know :)).
To do that I'd like to get a JSON representation of the before and after values.
Here is the current code: https://github.com/docteurklein/pgpim/blob/master/rust/src/main.rs#L74
Any idea how to do that?
I wonder if impl TryFrom<BinlogRow> for Row
would do the trick, since Row seems to be serializable in json?
If so, how would you use this API?
Thanks for reading :)

Hi.
It's unclear which layout will be convenient. I'd suggest you to write your own to_json and from_json functions.

Thanks for the fast answer :) I'm quite inexperienced in rust, any hint or example to point me to?


Can't push on GitBlit after enabled verify Committer

Hi,
Just integrated the LDAP with GitBlit and it synced the users too. Then disabled Local Users and enabled the verify committer for the repository.
After that, I set up the new Username and Email globally and committed my code. The Author and Committer are the same, But it doesn't let me push it on the GitBlit server.
It shows me this error message:
 ! [remote rejected] ... (Sorry, the account ... does not have an email address set for committer verification!) error: failed to push some refs to 'https://myrepository.git'
Do you have any idea how can I fix it?
Thanks

Have you set the correct value for the realm.ldap.email property to map the email attribute from LDAP?
Have you checked in Gitblit in the users page if the email addresses for the user(s) are set?

Thank you so much @flaix
I just set up the value for realm.ldap.email and it works.


change-preview-window resets change-preview

Checklist

[X] I have read through the manual page (man fzf)
[X] I have searched through the existing issues
[X] For bug reports, I have checked if the bug is reproducible in the latest version of fzf

Output of fzf --version
0.51.0 (brew)
OS

[ ] Linux
[X] macOS
[ ] Windows
[ ] Etc.

Shell

[X] bash
[X] zsh
[ ] fish

Problem / Steps to reproduce
Hello, is it expected behavior for
fzf --bind 'start:change-preview(echo hello)' --bind 'enter:change-preview-window(30%)'

to make the preview completely disappear on pressing enter?

No, it looks like a bug. Let me look into it.

Should be fixed now. Thanks for the report.

Thank you so much!


Add UT infrastructure

@bjcbATibm @zhangleiIBM Do you have interest to implement this item?

I think this feature is needed.

I just upload my UT code, but just in case my local code lost. Still need to fill many codes.


Running yarn upgrade breaks tests

Not sure which major bump caused breaking change, but onlick-has-focus test fails on line 13 for src/util/isElementInteractive.js. I'm guessing this is a babel breaking change?

Looking into it


Updated imports break compatibility with older versions of tensorflow

This does seem to break compatibility with tensorflow 1.12. Downgrading to 0.3.5 (before this pull request) seems to fix this.
It would be nice to have the imports change dynamically.
Originally posted by @lambdaloop in https://github.com/jgraving/DeepPoseKit/pull/39#issuecomment-609100884

Latest pip version should (hopefully) fix this @lambdaloop Reopen if you're still having problems.


Document required packages for installation

First, thank you for this app! It is awesome, and I am using it now. A challenge that I faced had when installing this was figuring out what packages (php and otherwise) were required. Not sure if it was because I was using a minimal build, but it would be great if you could list them in the instructions. Here is what I installed to make it work:

php-cli
libapache2-mod-php <-- I am not sure if this is needed
php-mbstring
php-mimetype
php-curl
Composer
unzip <- install with "apt install unzip"

That’s a good point, I mentioned some of those in my video’s description https://youtu.be/uzAqgjElc64


scanner not working in ios device

Hi there. I am having problems using this package with ios devices. It does not work for google chrome in ios device at all. It works in safari but only accesses the camera that to camera gets stuck after allowing permission.

@shah-pooja Hi, Google chrome in iOS is just a wrapper for webkit webview. Meaning it is version of safari which doesn't have access to camera. So you need the use qrcodescan.in in safari app.

Closing the issue!. Hope i have answered your question.


Fix #2095, Automatic suppression of flooding events

Checklist (Please check before submitting)

[x] I reviewed the Contributing Guide.
[x] I signed and emailed the appropriate Contributor License Agreement to<EMAIL_ADDRESS>and copied<EMAIL_ADDRESS>
Describe the contribution

Fix #2095

Testing performed
CI
Expected behavior changes
Squelches flooding events (configurable)
System(s) tested on
CI
Additional context
Still a work in progress, needs coverage and functional cleanup
Third party code
None, update suggestion from NASA/JSC context.
Contributor Info - All information REQUIRED for consideration of pull request
Jacob Hageman - NASA/GSFC
Ping @jhnphm

@jhnphm - this is planned for CCB on 8/3.  Could you review the recent minor changes?  Thanks for putting this together!


Add option to change screen mode

Add option to change the screen between header and full mode.

With this option, we don't need the fullscreen branch anymore.


Can't get the latest macOS builds to work

When I try the version at /current I get:
~ > /Users/dbmrq/Downloads/biber --help
Attempt to reload DynaLoader.pm aborted.
Compilation failed in require at /loader/HASH(0x10089eb48)/XSLoader.pm line 121.
Compilation failed in require at /loader/HASH(0x1008cdb90)/IO/Handle.pm line 269.
BEGIN failed--compilation aborted at /loader/HASH(0x1008cdb90)/IO/Handle.pm line 269.
Compilation failed in require at /loader/HASH(0x1008cdc20)/IO/Seekable.pm line 101.
BEGIN failed--compilation aborted at /loader/HASH(0x1008cdc20)/IO/Seekable.pm line 101.
Compilation failed in require at /loader/HASH(0x1008cdb00)/IO/File.pm line 133.
BEGIN failed--compilation aborted at /loader/HASH(0x1008cdb00)/IO/File.pm line 133.
Compilation failed in require at -e line 162.

When I try the version at /development I get:
~ > /Users/dbmrq/Downloads/biber --help
Can't load '/var/folders/xk/81hr0f0n4hz_n1kwjp6lt70r0000gn/T/par-64626d7271/cache-82ce96a9b579ca7d831ec5498c59bb9c4087cc21/79628e8f.bundle' for module XML::LibXML: dlopen(/var/folders/xk/81hr0f0n4hz_n1kwjp6lt70r0000gn/T/par-64626d7271/cache-82ce96a9b579ca7d831ec5498c59bb9c4087cc21/79628e8f.bundle, 1): Library not loaded: /opt/local/lib/libxml2.2.dylib
  Referenced from: /var/folders/xk/81hr0f0n4hz_n1kwjp6lt70r0000gn/T//par-64626d7271/cache-82ce96a9b579ca7d831ec5498c59bb9c4087cc21/79628e8f.bundle
  Reason: Incompatible library version: 79628e8f.bundle requires version 12.0.0 or later, but libxml2.2.dylib provides version 10.0.0 at /loader/HASH(0x10188cc08)/DynaLoader.pm line 197.
 at /loader/HASH(0x10190b820)/PAR/Heavy.pm line 123.
BEGIN failed--compilation aborted at /var/folders/xk/81hr0f0n4hz_n1kwjp6lt70r0000gn/T/par-64626d7271/cache-82ce96a9b579ca7d831ec5498c59bb9c4087cc21/inc/lib/XML/LibXML.pm line 156.
Compilation failed in require at /var/folders/xk/81hr0f0n4hz_n1kwjp6lt70r0000gn/T/par-64626d7271/cache-82ce96a9b579ca7d831ec5498c59bb9c4087cc21/inc/lib/XML/LibXML/Simple.pm line 17.
BEGIN failed--compilation aborted at /var/folders/xk/81hr0f0n4hz_n1kwjp6lt70r0000gn/T/par-64626d7271/cache-82ce96a9b579ca7d831ec5498c59bb9c4087cc21/inc/lib/XML/LibXML/Simple.pm line 17.
Compilation failed in require at /var/folders/xk/81hr0f0n4hz_n1kwjp6lt70r0000gn/T/par-64626d7271/cache-82ce96a9b579ca7d831ec5498c59bb9c4087cc21/inc/lib/Biber/LaTeX/Recode.pm line 16.
BEGIN failed--compilation aborted at /var/folders/xk/81hr0f0n4hz_n1kwjp6lt70r0000gn/T/par-64626d7271/cache-82ce96a9b579ca7d831ec5498c59bb9c4087cc21/inc/lib/Biber/LaTeX/Recode.pm line 16.
Compilation failed in require at /var/folders/xk/81hr0f0n4hz_n1kwjp6lt70r0000gn/T/par-64626d7271/cache-82ce96a9b579ca7d831ec5498c59bb9c4087cc21/inc/lib/Biber/Utils.pm line 19.
BEGIN failed--compilation aborted at /var/folders/xk/81hr0f0n4hz_n1kwjp6lt70r0000gn/T/par-64626d7271/cache-82ce96a9b579ca7d831ec5498c59bb9c4087cc21/inc/lib/Biber/Utils.pm line 19.
Compilation failed in require at /var/folders/xk/81hr0f0n4hz_n1kwjp6lt70r0000gn/T/par-64626d7271/cache-82ce96a9b579ca7d831ec5498c59bb9c4087cc21/inc/lib/Biber/Internals.pm line 8.
BEGIN failed--compilation aborted at /var/folders/xk/81hr0f0n4hz_n1kwjp6lt70r0000gn/T/par-64626d7271/cache-82ce96a9b579ca7d831ec5498c59bb9c4087cc21/inc/lib/Biber/Internals.pm line 8.
Compilation failed in require at /loader/HASH(0x10188d748)/parent.pm line 16.
BEGIN failed--compilation aborted at /var/folders/xk/81hr0f0n4hz_n1kwjp6lt70r0000gn/T/par-64626d7271/cache-82ce96a9b579ca7d831ec5498c59bb9c4087cc21/inc/lib/Biber.pm line 5.
Compilation failed in require at script/biber-darwin line 17.
BEGIN failed--compilation aborted at script/biber-darwin line 17.
~ >

Previous versions work fine. :/

Which bitness? I think you might be trying the 32-bit version on a 64-bit platform.

Same kind of trouble with Linux build (on a 64-bit platform):
$ wget https://sourceforge.net/projects/biblatex-biber/files/biblatex-biber/current/binaries/Linux/biber-linux_x86_64.tar.gz
[...]
$ tar xvfz biber-linux_x86_64.tar.gz
biber
$ biber -v
Attempt to reload DynaLoader.pm aborted.
Compilation failed in require at /loader/HASH(0x2439060)/XSLoader.pm line 118.
Compilation failed in require at /loader/HASH(0x250c488)/IO/Handle.pm line 269.
BEGIN failed--compilation aborted at /loader/HASH(0x250c488)/IO/Handle.pm line 269.
Compilation failed in require at /loader/HASH(0x250c518)/IO/Seekable.pm line 101.
BEGIN failed--compilation aborted at /loader/HASH(0x250c518)/IO/Seekable.pm line 101.
Compilation failed in require at /loader/HASH(0x250c3f8)/IO/File.pm line 133.
BEGIN failed--compilation aborted at /loader/HASH(0x250c3f8)/IO/File.pm line 133.
Compilation failed in require at -e line 162.

This is very strange, I just downloaded exactly what you did using the same commands and it is fine for me. Which linux are you using? My build servers are 10.10.

I'm using Linux Mageia 6.

My build servers are 10.10.

I'm not sure what you mean by this.
Anyway, just like dbmrq, the previous versions used to work like a charm (if I remember well, the previous one which worked was downloaded 3 days ago).

Sorry, I meant Ubuntu.10.10. I try to build on an older distribution for maximum compat. Just to be sure, you are using the 64-bit version on 64-bit OS?

Sorry, I meant Ubuntu.10.10.

No problem. Linux Mageia is a .rpm flavor Linux distribution (just as Red Hat or Fedora), not a .deb flavor one (like Debian or Ubuntu).

Just to be sure, you are using the 64-bit version on 64-bit OS?

Yes.

Can you paste the output of ldd biber here?

$ ldd ./biber
        linux-vdso.so.1 (0x00007fff0ad92000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fb1fdcc1000)
        libnsl.so.1 => /lib64/libnsl.so.1 (0x00007fb1fdaa8000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007fb1fd8a4000)
        libm.so.6 => /lib64/libm.so.6 (0x00007fb1fd5a4000)
        libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00007fb1fd356000)
        libutil.so.1 => /lib64/libutil.so.1 (0x00007fb1fd153000)
        libc.so.6 => /lib64/libc.so.6 (0x00007fb1fcda0000)
        /lib64/ld-linux-x86-64.so.2 (0x00007fb1fdede000)

I just installed a fresh Mageia 6 virtualbox vm and downloaded the bib linux 64-bit 2.8 version from Sourceforge and it works fine for me - biber -v returns the version number as usual.

I'm trying the 64 bit binaries in a 64 bit mac (using macOS High Sierra), but I also tried the 32 bit build just to be sure and the results are the same. The 64 bit build of version 2.7 works, on the other hand. This is the output of otool -L:
~ > otool -L /Users/dbmrq/Downloads/biber
/Users/dbmrq/Downloads/biber:
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 125.2.10)
	/usr/lib/libutil.dylib (compatibility version 1.0.0, current version 1.0.0)

Well, very puzzling! But I'm not the only one facing this problem...

Interestingly enough, the 32-bit version of biber works as expected on my 64-bit Linux box.

Weird. Can you check with file the actual bitness of biber is correct as labelled?

Can you check with file the actual bitness of biber is correct as labelled?

@plk If this is for me, I don't understand what you mean.

I mean run file biber and see what is returned.

[ 32 bit version:]

$ file biber
biber: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 2.6.15, BuildID[sha1]=b10f6bbbae72bd9d81188eca2f9fdd9f5a1550c0, stripped

[ 64 bit version:]

$ file biber
biber: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.15, BuildID[sha1]=9f41ca39557c67d096f2512299f1986b35848cff, stripped

Hmm, all looks fine.

But, for the 64 bit version, still:
$ biber -v
Attempt to reload DynaLoader.pm aborted.
Compilation failed in require at /loader/HASH(0x1898070)/XSLoader.pm line 118.
Compilation failed in require at /loader/HASH(0x196b498)/IO/Handle.pm line 269.
BEGIN failed--compilation aborted at /loader/HASH(0x196b498)/IO/Handle.pm line 269.
Compilation failed in require at /loader/HASH(0x196b528)/IO/Seekable.pm line 101.
BEGIN failed--compilation aborted at /loader/HASH(0x196b528)/IO/Seekable.pm line 101.
Compilation failed in require at /loader/HASH(0x196b408)/IO/File.pm line 133.
BEGIN failed--compilation aborted at /loader/HASH(0x196b408)/IO/File.pm line 133.
Compilation failed in require at -e line 162.

The one here:
https://www.dropbox.com/s/f5l2dq8a4uh7sz5/biber?dl=0
works fine on my Ubuntu 10.10 and Mageia 6 64-bit VMs. Can you try it?

@dbmrq - I will try to rebuild and upload again later - I can't reproduce this currently - if I download from SF and run on my 10.13.1 OSX machine.

Works fine:
$ biber -v
biber version: 2.7

@dbitouze - are you sure you are calling the right one? It should return version 2.8.

are you sure you are calling the right one? It should return version 2.8.

Sorry, I forgot to run chmod u+x biber. So, unfortunately, it doesn't work:
$ md5sum ./biber
8557dc229734e519a44bb11621ecc8ed  biber
$ ./biber -v
Attempt to reload DynaLoader.pm aborted.
Compilation failed in require at /loader/HASH(0x2681070)/XSLoader.pm line 118.
Compilation failed in require at /loader/HASH(0x2754498)/IO/Handle.pm line 269.
BEGIN failed--compilation aborted at /loader/HASH(0x2754498)/IO/Handle.pm line 269.
Compilation failed in require at /loader/HASH(0x2754528)/IO/Seekable.pm line 101.
BEGIN failed--compilation aborted at /loader/HASH(0x2754528)/IO/Seekable.pm line 101.
Compilation failed in require at /loader/HASH(0x2754408)/IO/File.pm line 133.
BEGIN failed--compilation aborted at /loader/HASH(0x2754408)/IO/File.pm line 133.
Compilation failed in require at -e line 162.

I would like to highlight that, by default, there is no file /opt/local/lib/libxml2.2.dylib in macOS 10.13.1 as far as I can tell. That is why I get the same error message as @dbmrq (which is particularly problematic since the TeX Live Utility included in MacTeX already distributes biblatex 3.8, which seems to require biber 2.8).
The problem might be connected to dist/darwin_x86_64/build.sh, which specifies the library mentioned above, but not really sure.

Quick followup:
The library exists, of course, in the following location:
user@machine:~ > find /usr/lib -iname "libxml2.2.dylib"
/usr/lib/libxml2.2.dylib

This lib shouldn’t even need to exist on the machine as it’s packed with biber.

Can you try this again? I have updated libxml2 on my OSX 64-bit build server, rebuilt XML::LibXML and re-packed biber. Just pull it from SourceForge in about an hour to allow some replication time

A new version already showed up here for me (at least the site says it's from 10 minutes ago), but I still get that second error on both the 32 and 64 bit versions:
Can't load '/var/folders/xk/81hr0f0n4hz_n1kwjp6lt70r0000gn/T/par-64626d7271/cache-99866aded8e2c9e6afeefe400744441b75961bd9/79628e8f.bundle' for module XML::LibXML: dlopen(/var/folders/xk/81hr0f0n4hz_n1kwjp6lt70r0000gn/T/par-64626d7271/cache-99866aded8e2c9e6afeefe400744441b75961bd9/79628e8f.bundle, 1): Library not loaded: /opt/local/lib/libxml2.2.dylib
  Referenced from: /var/folders/xk/81hr0f0n4hz_n1kwjp6lt70r0000gn/T//par-64626d7271/cache-99866aded8e2c9e6afeefe400744441b75961bd9/79628e8f.bundle
  Reason: Incompatible library version: 79628e8f.bundle requires version 12.0.0 or later, but libxml2.2.dylib provides version 10.0.0 at /loader/HASH(0x100914020)/DynaLoader.pm line 197.
 at /loader/HASH(0x10100ec38)/PAR/Heavy.pm line 123.
BEGIN failed--compilation aborted at /var/folders/xk/81hr0f0n4hz_n1kwjp6lt70r0000gn/T/par-64626d7271/cache-99866aded8e2c9e6afeefe400744441b75961bd9/inc/lib/XML/LibXML.pm line 156.
Compilation failed in require at /var/folders/xk/81hr0f0n4hz_n1kwjp6lt70r0000gn/T/par-64626d7271/cache-99866aded8e2c9e6afeefe400744441b75961bd9/inc/lib/XML/LibXML/Simple.pm line 17.
BEGIN failed--compilation aborted at /var/folders/xk/81hr0f0n4hz_n1kwjp6lt70r0000gn/T/par-64626d7271/cache-99866aded8e2c9e6afeefe400744441b75961bd9/inc/lib/XML/LibXML/Simple.pm line 17.
Compilation failed in require at /var/folders/xk/81hr0f0n4hz_n1kwjp6lt70r0000gn/T/par-64626d7271/cache-99866aded8e2c9e6afeefe400744441b75961bd9/inc/lib/Biber/LaTeX/Recode.pm line 16.
BEGIN failed--compilation aborted at /var/folders/xk/81hr0f0n4hz_n1kwjp6lt70r0000gn/T/par-64626d7271/cache-99866aded8e2c9e6afeefe400744441b75961bd9/inc/lib/Biber/LaTeX/Recode.pm line 16.
Compilation failed in require at /var/folders/xk/81hr0f0n4hz_n1kwjp6lt70r0000gn/T/par-64626d7271/cache-99866aded8e2c9e6afeefe400744441b75961bd9/inc/lib/Biber/Utils.pm line 19.
BEGIN failed--compilation aborted at /var/folders/xk/81hr0f0n4hz_n1kwjp6lt70r0000gn/T/par-64626d7271/cache-99866aded8e2c9e6afeefe400744441b75961bd9/inc/lib/Biber/Utils.pm line 19.
Compilation failed in require at /var/folders/xk/81hr0f0n4hz_n1kwjp6lt70r0000gn/T/par-64626d7271/cache-99866aded8e2c9e6afeefe400744441b75961bd9/inc/lib/Biber/Internals.pm line 8.
BEGIN failed--compilation aborted at /var/folders/xk/81hr0f0n4hz_n1kwjp6lt70r0000gn/T/par-64626d7271/cache-99866aded8e2c9e6afeefe400744441b75961bd9/inc/lib/Biber/Internals.pm line 8.
Compilation failed in require at /loader/HASH(0x100914b60)/parent.pm line 16.
BEGIN failed--compilation aborted at /var/folders/xk/81hr0f0n4hz_n1kwjp6lt70r0000gn/T/par-64626d7271/cache-99866aded8e2c9e6afeefe400744441b75961bd9/inc/lib/Biber.pm line 5.
Compilation failed in require at script/biber-darwin line 17.
BEGIN failed--compilation aborted at script/biber-darwin line 17.

😢
Very weird that you can't reproduce it. Is it possible that the wrong version of libxml2 is getting bundled somehow, even if you have the right version on your system?

Same error messages here.

Also I just saw someone else with the same problem here: https://tex.stackexchange.com/q/399831/102699

I can reproduce now if I rename the /opt/local/lib/libml2.2.dylib on my machine. This may be a PAR::Packer problem as it seems not to be finding the packed libxml2 for some reason.

Maybe this helps: I linked version 2.9.7 of libxml2.2.dylib (from Homebrew) into /opt/local/lib and the error messages now says:
Can't load '/var/folders/xx/h56tdp5962x89fds2mx9hc0w0000gn/T/par-7761676e6572/cache-284893d39de4293722d6902cdc883227c86ae2be/35543de4.bundle' for module XML::LibXML: dlopen(/var/folders/xx/h56tdp5962x89fds2mx9hc0w0000gn/T/par-7761676e6572/cache-284893d39de4293722d6902cdc883227c86ae2be/35543de4.bundle, 1): Library not loaded: /opt/local/lib/libiconv.2.dylib
  Referenced from: /var/folders/xx/h56tdp5962x89fds2mx9hc0w0000gn/T//par-7761676e6572/cache-284893d39de4293722d6902cdc883227c86ae2be/35543de4.bundle
  Reason: Incompatible library version: 35543de4.bundle requires version 9.0.0 or later, but libiconv.2.dylib provides version 7.0.0 at /loader/HASH(0x1018586b0)/DynaLoader.pm line 197.
 at /loader/HASH(0x1018f1ec8)/PAR/Heavy.pm line 123.
[...]

So libxml2 isn't the only library not bundled properly… there's at least libiconv too, but something else would probably show up if we linked that one as well.
So it does look like a problem with the packer. And it wasn't happening with version 2.7. Maybe using an older version of PAR::Packer could work?

That's rarely a good idea. I am currently updating my build OSX VM.

Can you try this again? I have updated libxml2 on my OSX 64-bit build server, rebuilt XML::LibXML and re-packed biber. Just pull it from SourceForge in about an hour to allow some replication time

This one (from biber-linux_x86_64.tar.gz):
$ md5sum ./biber
9af21dc10092321c5bc8187149daaf2d  ./biber
$ ./biber -v
biber version: 2.8

works like a charm on my Linux 64 bits box.

Ok, then I think the linux issue is fixed. OSX is still a problem.

It seems that TeX live are reverting back to 3.7 for the time being (see http://tug.org/pipermail/tex-live/2017-November/040777.html and http://tug.org/pipermail/tex-live/2017-November/040779.html). Should we ask MikTeX to do the same?

Yes, there are some very low-level issues with PAR::Packer and OSX. I have them fixed on Linux but it is not clear what is happening on OSX. Am in discussion with the PAR::Packer author.

Do you want me to ask the MikTeX maintainer at https://github.com/MiKTeX/miktex-packaging/issues, or would you rather discuss it with him himself?

Can you do it? I am deep in the guts of library path with the PAR::Packer author. Something has changed in the way macports delivers/compiles shlibs it seems.

On to it.

I have confirmed with the PAR::Packer maintainer that this is a bug in the packer module (possibly caused by recent macport compilation flags for some library updates). We have tested a fix which solves the issue and expect to release shortly.

Please get 2.8 again from SF, I believe that this is now resolved.

It works! 🍾
Thank you for your work on this!

Are there still some issues left or can we expect Biber to reach CTAN soon?

@moewew - Should be there today I think - I just provided a re-packed dist to CTAN people who are happy now and we agreed on how this will be handled in future.

Brilliant!


How does this crate fit into the usb-audio rust ecosystem

From conversations in https://github.com/btrepp/rust-midi-stomp/pull/1 with @perlindgren
Figured it might be better to discuss this in it's own issue.
Ultimately the summary is that to me it makes sense that this crate, or future versions of it, fit in nicely with the rest of usb audio devices. With most of the usb spec, this really should just be an extra 'feature' as part of the audio class, that you can choose to use or not.
What I'm unclear of at the moment, is the current state of audio devices in rust. I can't seem to find any groups about this in the embedded rust pages, but I think perhaps one exists. Does anyone have any links to repositories or groups?. From there I would also be curious as to whether there should be a 'reference' platform for boards. This was developed against the bluepill, but targeting a common board would help with investigating issues/development
In regards to aligning with other midi-implementations, I am for this. The implementation of codes here exists because others didn't at the time. It seems the normal rust community has published a few nifty crates since then.

In regards to aligning with other midi-implementations, I am for this. The implementation of codes here exists because others didn't at the time. It seems the normal rust community has published a few nifty crates since then.

#11 updates this library to use shared types from https://github.com/rust-midi/

USB audio is one of the more complicated things to implement. There are even two standards: UAC1 and UAC2. For UAC2, a high speed device is required, which most MCUs today don't feature without an external PHY. I'm also not aware of a mature implementation in Rust for these classes, especially with having a working synchronisation endpoint recognized by all major host platforms.
What I can tell from having a look at the descriptors of some devices in my studio setup is that most manufacturers keep MIDI and audio as separate class interfaces, even if the device can do both. This is understandable as both are very different and having them in the same USB specs is somewhat unfortunate fact.
Regarding the types: I would really keep them of this crate and let the user choose an external one he likes. Imagine you have a synthesizer that features not only USB MIDI but also regular DIN MIDI (or maybe even Bluetooth MIDI). In that case, you likely want to have the same types for all transport mechanisms because they essentially carry the same messages (for MIDI 2.0, it's a different topic). Having the types in one of those libaries would make the other ones depend on exact the same version on it, a similar situation of what we currently have with usb-device.
With external crate like wmidi, it's a one liner to convert from raw data:
let message = wmidi::MidiMessage::try_from(bytes)?;

I'm quite sure, you could do the same with the midi-types crate, avoiding all the dependency hassle.

Setting aside types.
One of the reasons I made this issue was https://github.com/rust-embedded-community/usbd-midi/blob/b433d0f4a5d223b11c5f06c837132df2d39ce46e/src/midi_device.rs#L107.
You can see ultimately while we are 'just doing midi', even as it's own device (and you can easily have multiple devices in a usb device), it always felt a little dumb to make an 'audio class' device, and then not really do anything audio-ish, nor even be related to other classes that do audio things.
It probably does have relation to other crates, maybe ultimately a sub or library crate of some bigger tool-kit. This also probably highlights that the MidiDevice code isn't the best, it's workable, but it didn't really have a great 'design' haha.

You can see ultimately while we are 'just doing midi', even as it's own device (and you can easily have multiple devices in a usb device), it always felt a little dumb to make an 'audio class' device, and then not really do anything audio-ish, nor even be related to other classes that do audio things.

This is a personal view, but I think at the time USB MIDI came into the game, the USB implementors forum had to decide how to handle it. They essentially had 2 two options: create an own class for it or integrate it into another. They decided for the latter, probably because MIDI is kind of niche compared to the other things in USB universe. But I admit that I also was a little bit surprised when I first saw it under the audio class.  With that in mind, I don't think there's something wrong with not doing audio in the audio class device.

Ah I don't have any issues with how the spec is implemented, it's probably just around user expectations :).
With midi being a subclass of audio, when looking at libraries you might expect to see say usb-audio, and the various sub classes, eg looking for midi, but you won't find it. Currently it's all different crates.
In practical matters, it doesn't really matter though, just that if you were implementing something that did both, it would appear as maybe more devices that it needed to :).
Pretty minor in the scheme of things though.


[migrate] Custom index with pg_trgm gets removed immediately and causes drift

Problem
I am creating a migration script with npx prisma migrate dev --create-only:
My migration.sql file:
CREATE EXTENSION IF NOT EXISTS pg_trgm;

DROP INDEX IF EXISTS index_on_profile_name_trigram;
CREATE INDEX index_on_profile_name_trigram ON "Profile" using gin (name gin_trgm_ops);

Then I am running npx prisma migrate dev.
Two outcomes:

Prisma-migrate detects a drift and empties my database content (Drift detected: Your database schema is not in sync with your migration history.)
Prisma-migrate creates a second migration file that removes the index again.

Auto-generated migration.sql:
-- DropIndex
DROP INDEX "index_on_profile_name_trigram";

Suggested solution
Both "outcomes" described above should not happen.
Instead prisma-migrate should only apply my migration script.
Alternatives

Deleting the automatically generated migration.sql file everytime I add a new migration
Also it will detect a drift everytime, and require me to import my database content again
This is very inconvenient.

Additional context
I have asked around in the slack channel and got asked to create this PR:

Hi @0xsven ! Thanks for the issue. Have you tried adding @@index([name]) to the model? We want to support the full variety of postgres indexes in the future, but adding @@index([name]) on the model should at least prevent migrate from dropping it, for now.

I tried doing this. Adding @@index([name]) and then modifying the migration to create a gin index instead of the regular index, and this seems to be working.

Happy to read you found a workaround @jackbravo  — of course it's not ideal, but we are planning to enrich what you can say about indexes in the Prisma schema relatively soon (I can't give dates, but I think it's high on the list of priorities).

To anyone who is having same issue, this worked for me
@@index([columnName(ops: raw("gin_trgm_ops"))], type: Gin)

and manually adding CREATE EXTENSION statement in the migration file before index creation.

Quick question: What happens if you db pull when this index is already present, either with the schema you already have or a new, empty one? Would be interesting to know if this index is picked up, and if so how.

I just took a look at this again, and can confirm that manually modifying the migration that adds the index to also activate the extension should be enough to properly use pg_trgm and the gin_trgm_ops operator class:

Create a minimal schema:generator client {
  provider = "prisma-client-js"
}

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

model Profile {
  id   Int    @id
  name String
}

Create an initial migration with npx prisma migrate dev
Now add the index to Profile in the schema file:model Profile {
  id   Int    @id
  name String

  @@index([name(ops: raw("gin_trgm_ops"))], type: Gin)
}

Use npx prisma migrate dev --create-only to create a migration you can edit before it is executed
Add the CREATE EXTENSION command to the generated migration:-- CreateIndex
CREATE EXTENSION IF NOT EXISTS pg_trgm;

CREATE INDEX "Profile_name_idx" ON "Profile" USING GIN ("name" gin_trgm_ops);

Execute the modified migration file with npx prisma migrate dev
Observe how everything succeeded, and npx prisma db pull does not modify the Prisma schema file, and how npx prisma migrate dev does not create any migration that drops an index or similar.
So from my perspective this is all resolved. Do you agree @jackbravo?

Going to close the issue for now 🚀


Differentiation between energy system and supply system

Description of the issue
We have the parallel subclasses of system:

energy system: An energy system is a system of spatially extended linked energy sources and sinks.
supply system: A supply system is a system that connects producers and consumers.

None of these have axioms and the definitions are somehow overlapping. Maybe one is the parent of the other? E.g. would an electricity supply system that transports electrical energy from electricity producers to electricity consumers be an energy system or a supply system or both?
Ideas of solution
If you already have ideas for the solution describe them here
Workflow checklist

[ ] I discussed the issue with someone else than me before working on a solution
[ ] I already read the latest version of the workflow for this repository
[ ] The goal of this ontology is clear to me

I am aware that

[ ] every entry in the ontology should have a definition
[ ] classes should arise from concepts rather than from words

Are there supply systems that we want to cover in the OEO, which aren't energy systems?
Are there energy systems that we want to cover in the OEO, which aren't supply systems?

I'd answer these questions as follows:
(1) maybe yes; (2) probably no.
If you agree with my ansers, we could make energy (supply) system a subclass of supply system.

@l-emele do you agree? It would be a small change and could be implemented before the next release.

I agree with making energy system a subclass of supply system. I also think, we should add energy supply system as alternative term to energy system.


Add freeze column to datatable

Description
Minimal implementation of a freezeColumn prop for DataTable,  which freezes the first column on the left and allows you to scroll the other columns.
If rowNumbers are shown, these are not frozen - they will scroll away, leaving only the first column of the table frozen on the left.

Checklist

[x] For UI or styling changes, I have added a screenshot or gif showing before & after
[x] I have added a changeset

To Do

Fix issue with white background in Firefox - overrides the border of the cells
Fix issue with edges of white background on mobile - interferes with header bottom border
Test on Windows and multiple browsers

Why is the white background needed?

Why is the white background needed?

when you scroll horizontally, the content from the right columns will pass behind the frozen column - you can see it underneath if you don't set the background

Need to revisit this - would be a great feature to have, but it seems like the table needs to be aware of the width of the columns, which will require some thought


Miscellaneous type hint fixes

I was checking my contributions to the previous version of robotFramework were still functional in the RF 7.0 beta. I noticed some small issues.

Fixed a couple of instances of overzealous find-and-replace
Fixed some missing imports
Added some missing type arguments to Generic classes

Looks good now. Thanks for the fixes!


[Bug] Encoding error on src with Cloudinary url

Bug Report
Describe the bug
I use on component CldImage this src:
https://res.cloudinary.com/dcrteccot/image/upload/v1683130473/tour/1/No usada 2.jpg
and I got this response that brokes the image:
https://res.cloudinary.com/dcrteccot/image/upload/c_limit,w_300/f_auto/q_auto/v1683130473/tour/1/No%2520usada%25202?_a=BAVAS0DV0

Steps To Reproduce the error

Use CldImage component
Add on src prop "https://res.cloudinary.com/dcrteccot/image/upload/v1683130473/tour/1/No usada 2.jpg"

Screenshot or Video Recording

Additional context
I think this is an issue related to a second encoding of the Cloudinary Image

thanks @gastMor for the report
it looks like this is actually an issue with a dependency i'm using for URL creation: https://www.npmjs.com/package/@cloudinary/url-gen
I'll see what I can do to mitigate this, but have been able to reproduce
as far as usage is concerned so i can better understand the use case, is that URL coming back to your programmatically with the encoding already on the URL?

im thinking a solution here could be proactively decoding the public ID of any passed in value with the idea being the dependency re-encodes it. this would prevent the double encoding. if there are no encoded characters, it would be harmless
going to think on it a bit more to see if any special cases come up before moving forward with this

hey @gastMor if you get to trying this, please let me know if you notice any issues!


vue not detected on https://myanimelist.net/

Version
5.0.0-beta.3
Browser and OS info
chrome 71
Steps to reproduce
https://myanimelist.net/
What is expected?
vue detected
What is actually happening?
vue not detected

@Francismori7 its nota bout debugging, its about detecting.

The endpoints that report vues versions are disabled in production. Imagine a vulnerability is found in version 2.5.14 and people are able to tell you are using that version, you're done most likely.
This is expected behavior

@Francismori7 you are telling some nonsense :)  Open any site that run vue e.g. vuepeople.org, my.nintendo.com and u will see thats its detected and vue dev tools not work due to production build  e.g.
"Vue.js is detected on this page. Devtools inspection is not available because it's in production mode or explicitly disabled by the author."

It is correctly detected on the initial load:

Maybe it is only in use for that modal?


Fix PngWriter init after batch_size removal

This should update web script to address changes in PngWriter after batch_size init parameter was removed

This is superseded by PR #231


small tweaks

Just a couple of tweaks from running it just now! https://batch.hail.populationgenomics.org.au/batches/492792
I didn't actually check with multiple output formats but I noticed the instructions were inconsistent between comma / space separated! And I find it more intuitive if the VDS object is actually called .vds but you may disagree!

@Alexander-Stuckey used this PR to fix a couple of minor typos as well!


Throws Uncaught Error: Cannot find module './stream-api'

The error Uncaught Error: Cannot find module './stream-api' is thrown when I open the imdone task-board in version2.0.13.

Looks like there might have been a problem when you installed.  This error is coming from a dependency of imdone-atom.  Try uninstalling the package and installing again.

Reinstalled the package and the error is no more. Thanks 👍🏽

Atom 1.11.2; Ubuntu Linux  16.10
I have got the same error:
Error: Cannot find module './stream-api'
    at Module._resolveFilename (module.js:339:15)
    at Function.Module._resolveFilename (/usr/share/atom/resources/app.asar/src/module-cache.js:383:52)
    at Function.Module._load (module.js:290:25)
    at Module.require (module.js:367:17)
    at require (/usr/share/atom/resources/app.asar/src/native-compile-cache.js:50:27)
    at readdir (/home/username/.atom/packages/imdone-atom/node_modules/imdone-core/node_modules/chokidar/node_modules/readdirp/readdirp.js:52:25)
    at FSWatcher.<anonymous> (/home/username/.atom/packages/imdone-atom/node_modules/imdone-core/node_modules/chokidar/lib/nodefs-handler.js:355:5)
    at FSWatcher.NodeFsHandler._handleDir (/home/username/.atom/packages/imdone-atom/node_modules/imdone-core/node_modules/chokidar/lib/nodefs-handler.js:406:18)
    at FSWatcher.<anonymous> (/home/username/.atom/packages/imdone-atom/node_modules/imdone-core/node_modules/chokidar/lib/nodefs-handler.js:455:19)
    at FSWatcher.<anonymous> (/home/username/.atom/packages/imdone-atom/node_modules/imdone-core/node_modules/chokidar/lib/nodefs-handler.js:460:16)
    at FSReqWrap.oncomplete (fs.js:82:15)

Uninstalling and reinstalling of the package did not help. The stack trace is from after the reinstall.


Fails with type unions

Interface
interface Foo {
    id: number | null;
}

fails the validation by saying Error: Foo.id should be number
Validator file
...
properties: {
    id: {
        type: 'number',
    },
}
...

I am also having the same issue.
Additionally, if I use annotations to assign the type the Validator file out puts an extra set of quotes outside the brackets.
export interface Foo {
  /**
   * @TJS-type ['array', 'null']
   */
  foo?: Array<string> | null
}

Validation output:
  foo: {
     type: "['array', 'null']"
  },

This seems like a dealbreaker...

This seems like a dealbreaker...

@Jewcub I guess you can do that. I decided not to use this tool because of the basic functionality it offers.


Will Schematron move from GoogleCode?

Is there a plan for Schematron to move away from GoogleCode before GoogleCode
closes
(http://google-opensource.blogspot.ie/2015/03/farewell-to-google-code.html)?

Personally, I'd like to see it become an 'Organization' on GitHub since I have
or use multiple GitHub projects that keep a copy of the Schematron XSLT files,
and it would be simpler if there was one Schematron that could be included as a
submodule.

There's already a lot of Schematron on GitHub as it is:
https://github.com/search?utf8=%E2%9C%93&q=schematron

Regards,

Tony Graham.

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 3 Jun 2015 at 8:26

Moved now


Upload IZX Token

@Alexorro follow requirements: https://github.com/TrustWallet/tokens#requirements

@dakson111 Is this image for contract 0x2ad180cbaffbc97237f572148fc1b283b68d8861 ?

its for SWDC
0x4619DF2Ca5795834eDdA178610b6aDB46ACF47A9

@dakson111 Added here https://github.com/TrustWallet/tokens/commit/a57db4c6fcd9db641e99ee699692d773d216fb3c


[BREAKINGCHANGE] OAuth & OIDC /token endpoint should respect the oauth 2.0 RFC

Description
This PR is a WIP following the idea that we should be able to use classic oauth libs to authenticate to Perses.
It went from a robotic use cases that we have in Amadeus where we want to use client credentials flow and we would like to use the clientcredentials package from oauth2 golang library.
I think it's legit and particularly if somebody want to request perses API with another language than go.
Screenshots

Checklist

[ ] Pull request has a descriptive title and context useful to a reviewer.
[ ] Pull request title follows the [<catalog_entry>] <commit message> naming convention using one of the
following catalog_entry values: FEATURE, ENHANCEMENT, BUGFIX, BREAKINGCHANGE, DOC,IGNORE.
[ ] All commits have DCO signoffs.

UI Changes

[ ] Changes that impact the UI include screenshots and/or screencasts of the relevant changes.
[ ] Code follows the UI guidelines.
[ ] Visual tests are stable and unlikely to be flaky.
See Storybook
and e2e docs for more details. Common issues
include:

Is the data inconsistent? You need to mock API requests.
Does the time change? You need to use consistent time values or mock time utilities.
Does it have loading states? You need to wait for loading to complete.

I think overall the changes looks reasonable to me and respecting the RFC is indeed a good thing.
It would be great to have some tests here, just to be sure everything is working fine as it took us around 2 release to have something stable on the auth aspect (in the backend or in the CLI)


feat: Basic File implementation

Added some basic File classes to support file reading and writing. Added the following classes:

java.io.File
java.io.FileReader
java.io.FileWriter
java.util.Scanner

This should provide the basic File reader and writing needs that are crucial for plugin development.
Example file reading implementation:
import { ServerCommands } from "@customrealms/core";

ServerCommands.register("/log-properties", () => {
  const serverPropsFile = new java.io.File("server.properties");
  const propsScanner = new java.util.Scanner(serverPropsFile);

  while (propsScanner.hasNextLine()) {
    const nextLine = propsScanner.nextLine();
    console.log(nextLine);
  }
});

Example file writing implementation:
import { ServerCommands } from "@customrealms/core";

ServerCommands.register("/write-file", () => {
  const file = new java.io.File("test-document.txt");
  const writer = new java.io.FileWriter(file);
  writer.write("This is some example text!");
  writer.close();
});

You're free to merge this whenever you're ready 🚀

You're free to merge this whenever you're ready 🚀

I don't have write access to the repository :o

Oh, I thought you would be able to merge an approved PR. I'll look into that later, but merge this one myself 👍


Handling "undefined" value fields in the data dictionary

The data dictionary has several Value property entries showing the Value Set column as undefined. However, it's not the value set that is undefined, it's the field itself. This may or may not be intended.
I suggest we move the undefined note to the Data Type column. I suspect, however, that the intent of marking certain elements as undefined would be to determine where vocabulary bindings are missing. See issue #TBD for more details on that feature.

OBE.


Eject function hangs subsequent connections

When clicking the 'Eject' button the amp does not become available for connection again.
Connection to the amp is currently only broken on server stop.

The issue was the SparkListener maintaining the connection. It is now stopped properly and the configuration in memory emptied ready for a new connection.

The issue was the SparkListener maintaining the connection. It is now stopped properly and the configuration in memory emptied ready for a new connection.


fix bug that rel.metadata not exists

?

To be specific, this changed in a newer version of Mongoid. Merging it, if even on a branch, would be appreciated.

Are you looking for someone to maintain this repo?

D'oh! This tripped me up again with a different project.
I can see there are a lot of forks with this change (or similar) applied. We'd all really appreciate it if this could be merged and a new RubyGems release be made.

@calfzhou Thanks, sorry it took so long to get this merged!

@Benjamin-Dobell Just pushed a new version which fixes this issue and another one (the gem would remove some other errors on embedded field, e.g. error produced by validates :field, presence: true). Sorry it took so long, it will be better from now on.


Add MessagePackIgnoreAttribute to exclude properties. Issue #55

This is solving our problems with property fields getting serialized; please merge and publish so we can deploy it properly through NuGet. Thanks!

Is this PR ask me that this feature should be in 0.5.x instead of 0.6?

Yes, please.

I merge this PR locally and release as 0.5.11.


Build Dialect Object

There are currently 2 section markers in the corpus: text_id and line. But several texts have the same text_id feature. This causes problems when selecting nodes with a certain reference:
T.nodeFromSection(('A36',))

This returns only 1 node, despite the fact there are two A36 texts.
Proposal: Introduce a large dialect object that will enclose the texts. dialect can then be a sectional feature, so that one can select a given text like this:
T.nodeFromSection(('Barwar', 'A36',))

Especially since dialects will be used frequently it would be helpful to model them as their own object. We can also annotate dialect objects with features such as coordinates or other useful information.
The database would have the following embedding:
dialect
    text
        paragraph
            line
            prosa
                sentence
                    word
                        morpheme
                            char

Although originally I thought to record the dialect as main object, I realized that the text_ids refer to a specific publication, not a dialect. So far, all available texts of a dialect have been published in one publication, containing texts in one dialect, but will that always be true?
An alternative could be (as suggested in a comment in generate_TF.ipynb) to record publication as main object, which has as a feature the dialect (or, allowing for multi-dialect publications, we could leave that to text).
On the other hand, as long as there is a mechanism to prevent multiple publications of one dialect using the same text_ids, I see no problem using dialect as main object above text, with publication being a feature of text.

Indeed this may be an indicator that we ought to prefer title over text_id, and consider, as you say, that the text_id is simply derived from the publication. I expect that a feature like text_id may become more and more irrelevant when texts are added from the website.
So what we could do is a sectioning like this:

{dialect}, {title}, {line}

A stylized version as will be printed through the app would look like this:

Barwar, The Monk and the Angel, 1

And then, if we have title conflicts we can add version numbers to the title itself as appropriate. e.g. (2)

That seems all right. It certainly looks much prettier than e.g. HOS_Barwar_2008, A1:1.

But this way, the first text called e.g. Village life will stay without number, and from the second one they will be numbered from Village life (2) -- as numbering the first one would require renaming it on adding the second one.

Agreed. That is a source text (i.e. master text) issue.

Done. The issue with duplicate titles will need to be solved in the source texts however.


bulkexport performance test

ResourceTypes
DB2
PostgreSQL

Patient+Careplan
630.5/Second
720.6/Second

6
151.10

8
185.67

there was an performance issue causing Patient and Group export to be near 10 resources/second and this shows we've improved on that a lot


added definitions for react-input-calendar

hello! Added definitions for react-input-calendar

react-input-calendar/react-input-calendar.d.ts
check list

[ ] is collect naming convention?

https://www.npmjs.com/package/react-input-calendar
http://bower.io/search/?q=react-input-calendar
others?

[ ] has a test file? (react-input-calendar/react-input-calendar-tests.ts or others)
[ ] pass the Travis-CI test?

thanks mate!