Multi-Party Document Sharing - Notarization & Confidentiality

Problem
A simplified picture of supply chain looks like this:

Figure1 - Full Picture
The arrows show the direction and flow of data from upstream to downstream parties. Usually there is at least one authority/auditor interested in the full picture but members are usually aware of the communication with their direct business partner. However, in some scenarios they are interested in some degree of (limited) visibility in n-tier supply chain information. e.g. in which markets my goods end up being sold or where do my raw materials come from?
Having heterogeneous systems of records and communication channels result in

low/no transparency on the supply chain of products and materials
isolating material traceability information in separate systems, un-shareable with involved participants

What we try to enable is the possibility to

Record and build graphs of product genealogy relationships
Seamless tracking of all sourced materials securely and verifiable
Maintaining confidentiality by sharing transaction information only with the participants directly involved in a transaction

e.g. In a product level, a desired visibility of a manufacturer could be:

Figure2 - Product's genealogy graph with limited n-tier visibility
where a manufacturer has full visibility on all the information shared with his/her direct partners but limited visibility on downstream.

Must be noted that sharing any information is optional and requires consent from all the involved parties and the data owner

Notarization
To manage the versioning of a document (contract, ...) we can simply notarize its hash and in case of any change, notarize the new hash by nullifying the latest hash. Needless to say the document itself will remain in local (private) systems of records accessible only by its owner.
Notarization of a document is a mapping between the document's hash and its owner's identifier. The identifier could be a  public key or address (asymmetric cryptography).
E.g. if the hash of our document is 0xaaaaaaaaaa and the owner is identified as 0x11111111, then the notary will persist the mapping between this document and its owner.
Adopting UTXO data structure, a notarization transaction includes some inputs and some outputs. Inputs will be the existing documents intended to be replaced by new documents provided in the outputs.
Notarizing a new document will be used when it will be a root of relationship graph. Inputs will be empty, and the outputs will include the document hash and its owner.
{
  inputs: [],
  outputs: [
    {
      hash: 0xaaaaaaaaaa,
      owner: 0x11111111
    }]
}

Notarizing change of ownership is used to transfer the ownership of document to a new owner. The existing notarized document’s hash will be included in the inputs and the outputs must include the new owner. This transaction must carry the signature from the current owner. The output hash might be the same as input or differ.
{
  inputs: [
    0xaaaaaaaaaa
  ],
  outputs: [
    {
      hash: 0xaaaaaaaaaa,
      owner: 0x22222222	// new owner
    }]
}

Notarizing a new version of existing document will notify everyone about a new version of the existing document. The current version must be replaced by the new version.
{
  inputs: [
    0xaaaaaaaaaa
  ],
  outputs: [
    {
      hash: 0xccccccccc,	// hash of new version of the document
      owner: 0x11111111
    }]
}

Notarizing granting access is a way to enable other parties to grow the graph of relationships. Let’s say we have a product ready to ship. The owner of the product must be able to grant access to the shipping company to attach shipping documents without losing the ownership on the product itself. This type of notarization generates an output which is a placeholder for future documents owned by another entity while keeping the ownership of the current document preserved.
{
  inputs: [
   0xaaaaaaaaaa
  ],
  outputs: [
    {
      hash: 0xaaaaaaaaaa,
      owner: 0x11111111
    }, {
      hash: 0xbbbbbbbbb,	// the placeholder
      owner: 0x33333333
    }]
}

Later on, the other entity can use Notarizing new version to attach the relevant document to the graph.
{
  inputs: [
    0xbbbbbbbbb
  ],
  outputs: [
    {
      hash: 0xqqqqqqqq,	// replacing the placeholder by real document’s hash
      owner: 0x33333333
    }]
}

Since all notarization transactions happen on a common notary, anyone is able to observe and build the graph independently. But no sensitive information will be available. To get the original document, either the source can proactively send it to the relevant partner(s) or partner(s) can request this when they observe any change on the notary. When necessary, even this relationship could be hidden behind ZKP shielding and document hashes will be shared off-chain. However, to nullify an old version, that hash could be marked publicly as a burnt hash without revealing any extra information.
Integrated Document Relation
The notarization concept allows independent documents to be linked externally. Meaning the relationships are not part of the document itself but on a higher level. An alternative approach could be having these relationships as part of the document itself.
e.g.
{
  documentType: "mainContract",
  relevantDocs: {
    orderItems: 0xa1a1a1a1,       // placeholder for line items document
    shippingDoc: 0x12345,       // placeholder for shipping document
  }
}

Placeholder is a random hash which will be changed in the future to the hash of real document containing the exact data.

In any cases, if a document requires confirmation from counterparts, the notarization object can be proposed by any of them but must be signed by all.

Visibility
Once a document is notarized, we should be able to share different parts of it with different parties without revealing more than its needed. To do so, we breakdown the document to a list of flat key/value pairs, list all the keys in the first leaf in a Merkle tree, list all the values in the same order as their keys appear in the first leaf, add nonces to prevent any brut-force attempt and use the Merkle tree root hash as the document hash to be notarized.
To get rid of nested keys, we merge the sub-key and its main-key with a . delimiter as main-key.sub-key.
from
{
  main-key: {
    sub-key: value
  }
}

to
{
  main-key.sub-key: value
}

All the keys will be concatenated using , delimiter in one string and will be used as the first leaf in the Merkle tree. This prevents having more than one leaf with the same key or more than a value for the same key. We assume the delimiter doesn't occur in the main string, otherwise must be replaced or escaped properly.
Values will be listed as the next leaves in the same order that their keys appear in the first leaf.  The list of ordered tree leaves will look like this:
[
  "0": "Buyer,Seller,Product.Name,Price"
  "1": "Alice",
  "2": "Bob",
  "3": "CoolestProduct",
  "4": "1000euros"
]

Each leaf will receive an independent random nonce and the Merkle tree root will be calculated and notarized.
At this stage, anyone with access to the main data can share different parts of the same Merkle tree and receiving parties are able to verify that they are talking about the same notarized document, although they might not see all the information. There will be only a single notarization transaction and receiving parties can also re-share different views without any need to have another separate notarization transaction. This also enables all the counterparts to be aware of any changes that might be applied to the notarized document and request the exact changes. If they are authorized to see the changes, they will receive the exact changed data, otherwise only enough hashes from the Merkle tree to validate that their relevant information has been kept intact.

First, this should get the award for this quarter's most well-written, clear explanation of a complex topic.  Outstanding writeup.  I'm keen to hear what others think, but I found myself quite interested in the notion of how to not only keep the data private, which this pattern clearly handles, but also preventing a powerful ML/AI approach from developing classifiers from large amounts of ongoing activity on the ledger, assuming the ledger is public or the attacker has access to a node.  This is where I expect there is nice synergy with the shield/verifier/merkle trie approach in the baseline spec could help this pattern for notarized information compartmentalization.

I found this infographics from a HBR article which was informative. If useful to add, a citation to the source may be needed. [https://hbr.org/2020/05/building-a-transparent-supply-chain].
hbr-supplychain blockchain - addendum 1 - R2003F_GAUR_CAPTURING.pdf

Notorization & Confidentiality can be addressed with VC. When specific use cases related to visibility will be surfaced, issue can be reopened.


fix: hardware wallet console errors

What it solves
Resolves #3762
How this PR fixes it
As hardware wallets cannot themselves change network, shouldSwitchNetwork now returns false when they are detected.
How to test it
Open the wallet connection modal and choose Ledger/Trezor. Observe no error in the console.
Screenshots

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

2 of 3 (66.67%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 35.573%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/logic/wallets/utils/network.ts
2
3
66.67%

Totals

Change from base Build<PHONE_NUMBER>:
0.02%

Covered Lines:
3554

Relevant Lines:
9043

💛  - Coveralls

Look goods. No errors when connecting with trezor and ledger.


How to open GSImageViewerController in landscape mode (depending on current orientation).

I would like to open an image depending on the device's current orientation. For example if device is in landscape mode image should rotate. Now it is showing in portrait mode only and not rotating in landscape mode.

You can inherit GSImageViewerController and try to modify it.

Late in the party! I'm still happy to help you guys.
Use supportedInterfaceOrientationsFor application delegate and add the following code in the AppDelegate file.
func application(_ application: UIApplication, supportedInterfaceOrientationsFor window: UIWindow?) -> UIInterfaceOrientationMask {
    if isLandscape {
        return UIInterfaceOrientationMask.all
    }else{
        return UIInterfaceOrientationMask.portrait
    }
}

Add this line to your GSImageViewerController file
override func viewDidLoad() {
    super.viewDidLoad()
    isLandscape = true
}

override func viewWillDisappear(_ animated: Bool) {
    isLandscape = false
}

And don't forget to add a global variable in the app delegate file
var isLandscape = false


[GSSoC'23] Back to Top arrow button

Issue Description:
I would to create a back to top arrow button for the website.
Expected Behavior:

Responsive for any type of devices.
Moving arrow animations.
Hovering with neon light effect.
Best user experience with smooth functioning.

Current Behavior:

No arrow button present.

Additional Information:

Helpful for the user to reachout to the head of the website in one click.
Provide best experience.

Labels:
It is a enhancement or a new feature.

@sahil-sagwekar2652 please assign this task to me to work under GSSoC'23 program


Hide/Show filter buttons

Hi Norm!
Here's a short video that shows the hiding/showing of the filter buttons based on whether a filter has been applied. Can that be integrated into KTL in any way so I can apply it to all views?
https://www.loom.com/share/40a880fd6f014e8180f035c5dbdd945d
Here's the code:
/* Hide / Show KTL filter buttons */
$(document).on('knack-view-render.view_12114', function () {
console.log('view_12114 has rendered. Setting up dynamic filter visibility.');
// Function to check the filter status and toggle visibility
function toggleFilterControlVisibility() {
const currentURL = window.location.href;
// Determine if filters are active
let isFilterActive = currentURL.includes('filters=') && !currentURL.includes('filters=%7B%7D');

// Select the filterCtrlDiv
const filterCtrlDiv = $('.filterCtrlDiv');

if (filterCtrlDiv.length > 0) {
  console.log('filterCtrlDiv is present.');
} else {
  console.log('filterCtrlDiv not found.');
}

// Always hide the Stop Filter button
const stopFilterButton = $('#kn-report-view_12114-1_Stop_filterBtn');
stopFilterButton.css({
  display: 'none',          // Hide from layout
  visibility: 'hidden',     // Ensure it’s not visible
  pointerEvents: 'none',    // Disable interactions
  width: '0',               // Collapse width
  height: '0',              // Collapse height
  overflow: 'hidden'        // Prevent any content from spilling out
});
console.log('Stop Filter button is fully hidden.');

// Toggle visibility of the Save Filter button based on filter status
const saveFilterButton = $('#kn-report-view_12114-1_Save_filterBtn');
if (isFilterActive) {
  saveFilterButton.css({
    visibility: 'visible',  // Show the button
    opacity: '1',           // Ensure it's fully visible
    backgroundColor: 'transparent', // Remove yellow background
    border: 'none'          // Remove the border
  });
  console.log('Save Filter button is visible with updated styling.');
} else {
  saveFilterButton.css({
    visibility: 'hidden',   // Hide the button but keep it in the DOM
    opacity: '0'            // Make it fully transparent
  });
  console.log('Save Filter button is hidden because no filters are applied.');
}

}
// Initial check on render
toggleFilterControlVisibility();
// Monitor changes to the DOM (filters being added/removed)
const targetNode = document.querySelector('#kn-report-view_12114-1');
const config = { childList: true, subtree: true };
const observer = new MutationObserver(() => {
console.log('DOM mutation detected. Rechecking filter status.');
toggleFilterControlVisibility();
});
if (targetNode) {
observer.observe(targetNode, config);
console.log('MutationObserver attached to #kn-report-view_12114-1.');
} else {
console.log('Failed to attach MutationObserver. Target node not found.');
}
});

Hi @gstark1234,
I've made an update that does what you need: hide the filter buttons unless there's an active filter.
You need to override the default behavior by adding these lines of initialization in your code:
ktl.userFilters.setCfg({
    autoHideButtons: true,
})

Add them inside the window.ktlReady function, somewhere between the two //KTL Setup tags.
See here for details:  https://github.com/cortexrd/Knack-Toolkit-Library/wiki/Customizing-Features#customizing-features-1

You can test the Beta code for now.
Don't forget to remove your own code to see the actual effect!
One last detail: the pink [X] button is useful when you have a complex filter with several fields, and you want to clear them all at once.
Norm

I've also added the flag to have monochrome buttons, based on your code sample.
ktl.userFilters.setCfg({
    autoHideButtons: true,
    monochromeButtons: true,
})

Beta code has been updated.
Norm

Thank you, Norm!
I removed my code and added yours. The code worked at hiding/showing the
buttons - GREAT! THANK YOU!!
An odd thing also happened after implementing the new code - my table that
is on the same page changed from no outer border (pre-KTL update) to an
outer border (post-KTL update). Not sure if it matters, but this table's
filtering is affected by _ft on the 1st pivot table on the same scene.
Here's an image of what I'm talking about - you can also see that this
table is impacted by the change, as the save buttons are visible in the 1st
image but not in the 2nd image. Any idea why that happened?  Thank you
again for your help!!!!!
PRE-KTL UPDATE
[image: image.png]
POST KTL UPDATE
[image: image.png]
On Sun, Nov 17, 2024 at 9:20 PM Cortex R&D Inc. @.***>
wrote:

I've also added the flag to have monochrome buttons, based on your code
sample.
ktl.userFilters.setCfg({
autoHideButtons: true,
monochromeButtons: true,
})
Beta code has been updated.
Norm
—
Reply to this email directly, view it on GitHub
https://github.com/cortexrd/Knack-Toolkit-Library/issues/409#issuecomment-2481791103,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BKDMEXWVBE3ZD5ZIAMTXX3D2BFFGDAVCNFSM6AAAAABR33JV7GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBRG44TCMJQGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

@gstark1234,
Glad you like it.
About your issue with borders appearing..., unfortunately I can't see any image.
I think you made a typo with _ft.  There's no such keyword.
Try again,
Norm

Thank you again, Norm! Your responsiveness is amazing!
How long do I need to keep it in beta to preserve the new filter options?
Also, here's a short video to show you the table border quirk:
Filter options / table borders - Watch Video
https://www.loom.com/share/690fe9b30a42492da88f99c01732c2cc
https://www.loom.com/share/690fe9b30a42492da88f99c01732c2cc?utm_medium=gif
On Mon, Nov 18, 2024 at 11:32 PM Cortex R&D Inc. @.***>
wrote:

@gstark1234 https://github.com/gstark1234,
Glad you like it.
About your issue with borders appearing..., unfortunately I can't see any
image.
I think you made a typo with _ft. There's no such keyword.
Try again,
Norm
—
Reply to this email directly, view it on GitHub
https://github.com/cortexrd/Knack-Toolkit-Library/issues/409#issuecomment-2484686362,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BKDMEXWCFMP6CUXWX66ECDT2BK5ODAVCNFSM6AAAAABR33JV7GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBUGY4DMMZWGI
.
You are receiving this because you were mentioned.Message ID:
@.***>

Had to take it out of beta, as it's also affecting the layout of other
unrelated tables - you can see here:
Borders - Watch Video
https://www.loom.com/share/e0b845ce96a84949934349eb1fecc8c8
https://www.loom.com/share/e0b845ce96a84949934349eb1fecc8c8?utm_medium=gif
On Tue, Nov 19, 2024 at 8:19 AM Gary Stark @.***> wrote:

Thank you again, Norm! Your responsiveness is amazing!
How long do I need to keep it in beta to preserve the new filter options?
Also, here's a short video to show you the table border quirk:
Filter options / table borders - Watch Video
https://www.loom.com/share/690fe9b30a42492da88f99c01732c2cc
https://www.loom.com/share/690fe9b30a42492da88f99c01732c2cc?utm_medium=gif
On Mon, Nov 18, 2024 at 11:32 PM Cortex R&D Inc. @.***>
wrote:

@gstark1234 https://github.com/gstark1234,
Glad you like it.
About your issue with borders appearing..., unfortunately I can't see any
image.
I think you made a typo with _ft. There's no such keyword.
Try again,
Norm
—
Reply to this email directly, view it on GitHub
https://github.com/cortexrd/Knack-Toolkit-Library/issues/409#issuecomment-2484686362,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BKDMEXWCFMP6CUXWX66ECDT2BK5ODAVCNFSM6AAAAABR33JV7GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBUGY4DMMZWGI
.
You are receiving this because you were mentioned.Message ID:
@.***>

Very clear now - thanks.
I'll need some time to reproduce the bug somehow.
Otherwise, if possible, can you give me access to one of those pages where the bug occurs?  I have your link, but the login is expired.  You can send me the info by email.

Just the live app.

Hi Norm!I sent you the info at @.*** If you need anything else, just let me know.Gary StarkValio, Founder & @.*** Nov 19, 2024, at 3:12 PM, Cortex R&D Inc. @.***> wrote:
Just the live app.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

@gstark1234,
Can you try the new Beta please?  Ctrl+F5.
Norm

BTW, whenever you see something wrong like this or a long spinner, always check the console logs.
This usually saves a lot of time. (F12 or Ctrl+Shift+i)

Working great now in Beta!! I didn't even have to add the code below!
ktl.userFilters.setCfg({
autoHideButtons: true,
monochromeButtons: true,
})
Thank you so much! What do I do now regarding beta and the production
mode? In other words, do I keep it in beta until you tell me to move
to Production?
Thank you again!!
On Wed, Nov 20, 2024 at 3:28 PM Cortex R&D Inc. @.***>
wrote:

@gstark1234 https://github.com/gstark1234,
Can you try the new Beta please? Ctrl+F5.
Norm
—
Reply to this email directly, view it on GitHub
https://github.com/cortexrd/Knack-Toolkit-Library/issues/409#issuecomment-2489483160,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BKDMEXRB7XCFBM6PWY6EHC32BTWF3AVCNFSM6AAAAABR33JV7GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBZGQ4DGMJWGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Great, but the two flags are supposed to be there!
I don't understand how this can work without them...

I've just release 0.29.3 a second ago.
You can just go back to Prod (default)
No version number in the loader.

Oh...they were still there from the other day :) sorry about that!
How long do I stay in beta now?
On Wed, Nov 20, 2024 at 3:37 PM Cortex R&D Inc. @.***>
wrote:

Great, but the two flags are supposed to be there!
I don't understand how this can work without them...
—
Reply to this email directly, view it on GitHub
https://github.com/cortexrd/Knack-Toolkit-Library/issues/409#issuecomment-2489498214,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BKDMEXQEUPCATFY32BBRXNT2BTXJZAVCNFSM6AAAAABR33JV7GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBZGQ4TQMRRGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

I just changed from b to p and now the filter buttons (the ones that the
new code hides if not filtered) are showing. The version showing in the
upper right is
V1.0.0 KTL v0.29.2
On Wed, Nov 20, 2024 at 3:39 PM Cortex R&D Inc. @.***>
wrote:

I've just release 0.29.3 a second ago.
You can just go back to Prod (default)
No version number in the loader.
—
Reply to this email directly, view it on GitHub
https://github.com/cortexrd/Knack-Toolkit-Library/issues/409#issuecomment-2489500303,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BKDMEXV7APUHAOZ6CXLMXN32BTXPBAVCNFSM6AAAAABR33JV7GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBZGUYDAMZQGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

You're not at the right version.  You have two options for force using the new code:

Ctrl+F5 to bypass the cache.  But all other users would have to do the same, unles their cache expires in a few hours.
Add ?1234 at the end of your loader's KTL_Start.js - see image.

Actually, any random number will work, as long as it changes when you need to force the update, in a future release.
This is a trick to go faster, without haing to wait until the cache expires.
ND

Yes, you can leave it there until you have the same issue, then change it to ?2345 or ?abcdxyz  doesn't matter what's after the question mark, but not space or funky chars.

Got it. Thank you so much...it's working great!!
On Wed, Nov 20, 2024 at 4:03 PM Cortex R&D Inc. @.***>
wrote:

Yes, you can leave it there until you have the same issue, then change it
to ?2345 or ?abcdxyz doesn't matter what's after the question mark, but not
space or funky chars.
—
Reply to this email directly, view it on GitHub
https://github.com/cortexrd/Knack-Toolkit-Library/issues/409#issuecomment-2489537299,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BKDMEXRKCRLHWDGENOM6BJT2BT2KTAVCNFSM6AAAAABR33JV7GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBZGUZTOMRZHE
.
You are receiving this because you were mentioned.Message ID:
@.***>


Accessibility rule for CompoundButton

This PR contains changes to cover all possibility for compound button's accessible name.
https://github.com/microsoft/eslint-plugin-fluentui-jsx-a11y/issues/46

@shweta786 there is some linting issue.


a first whack at ByteBufferSharing to fix TLS handshake corruption

Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[ ] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[ ] Is your initial contribution a single, squashed commit?

[ ] Does gradlew build run cleanly?

[ ] Have you written or updated unit tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, check Concourse for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

An alternative PR, using this same approach, has been merged to develop so I'm closing this one.


xarray.Dataset.var - xarray.DataArray.var - does it have ddof=1 parameter?

It is not clear from the description whether ddof = 1 is available and/or if it is set to 0.
(https://docs.scipy.org/doc/numpy-1.6.0/reference/generated/numpy.var.html)
for large samples, 1 or 0 don't make a lot of difference, but it would be good to know whether it uses N-1 or N.

Good question. Setting ddof should work. It's passed on to nanvar from NumPy or bottleneck, both of which default to ddof=0.

In core/nanops.py there are some explicit defaults of ddof=0 within xarray, but I'm not sure if those are always used or if there are also cases where var (or std) are directly passed on to numpy/bottleneck/dask.
I'm considering two different options to clarify this:

Add a docstring section on the ddof parameter specifying it uses ddof=0 as default for the reduction methods that use it, i.e. var and std. Possibly just copied from numpy's var page.
Refer to numpy's documentation page in the docstring of all reduction methods for further reference.

Both would require some logic in core/ops.py: either to check for which reduce methods need a ddof paragraph, or to create the proper url (which has to adjust min and max to np.amin and np.amax respectively)
Is there any clear preference from anyone about this?

Thanks for finding that @sjvrijn
I don't have a view on what we should use, so I would vote to defer to numpy (and pandas, which also seems to use 1), referencing that documentation to the extent xarray isn't changing anything.
But others probably have a stronger view on which ddof we should use?


Prompt the user when the app is started for the first time if he wants the assets download to take place or not

[x] Prompt user to download resources at startup otherwise read from offline json
[ ] Implement a preference setting where in user can select if he would like to download updates or not

Yes, i think this is a better solutions than what I suggested first. Just ensure the apps tries to download everything when it starts the first time.

Yep, sure thing!

@the-dagger Changing the title. We not only have to display the dialog, we also have to change how the download the data

Already completed in #490


Where to get the meanings of the configure parameters?

For example, the parameter weight_steer_rate in module planning.

There is currently no detailed introduction to the parameters. I think we may add related documents in the future!


Install

install/ubuntu_16.dep.py installs all the build dependencies and has been tested on a fresh Ubuntu 16.04 machine. After running this script, users can compile Clipper without worrying about dependency issues. -> Make Clipper install all of its build dependencies transparently to the user
Dockerfile builds all the dependencies as well as Clipper from fresh Ubuntu 16.04, and has been tested using the following command: docker build . -t clipper.

Can one of the admins verify this patch?


Add key logic

When a key is collected it can then open all the doors.
So allow key to be collected, a state var is recorded that the player has collected the key, and then any closed doors visited become equivalent open doors, plus character enters the door which goes to a different level.

Altered logic so that a new key is needed for each door


Performance on the validation set of something-something-v1

Hi, thank you for releasing pytorch version of ECO.
Have you run ECO-pytorch on the validation set of something-something-v1 dataset?
I wonder if it have reached the performance on the paper, 46.4%, which is obtained from an ensemble of networks with {16, 20, 24, 32} number of frames.
Thank you.

@pplntech can you share the downloaded something -something-v1 dataset with me ?My downloaded dataset has been not using.

@chen-ming2019 请问在something数据集复现，为何我的损失在４多不变了，准确率只有4%　是我的参数那里设置错了吗？还是什么问题

@anti1990 我没有跑ECO在something数据集上，但你这个结果应该是有问题的。你可以看看是不是模型最后的全连接层的类别数没有改？


feat(index): add puffin metadata cache

I hereby agree to the terms of the GreptimeDB CLA.
Refer to a related PR or issue link (optional)
What's changed and what's your intention?
Add puffin metadata cache
Checklist

[ ] I have written the necessary rustdoc comments.
[ ] I have added the necessary unit tests and integration tests.
[ ] This PR requires documentation updates.

@coderabbitai modify PR description according to diff


Add PATCH method and change methods icons as per issue request #4218

Description
Add PATCH method and change methods icons as per issue request #4218
Screencast
N/A
Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Hi @jonathangiardino 👋
Awesome update; what do you think about adding this look instead? I could add the code (since I already did) 😊

Totally dig it @pernielsentikaer!
Go ahead, seems like a nice touch! 🔥

Please feel free to change it so it matches your style.
Change whatever you like, I'm not that skilled as you 😊

Please feel free to change it so it matches your style.
Change whatever you like, I'm not that skilled as you 😊

I would not change anything honestly, if all is good I would merge it like this, I really like the tag, it's clearer than before. 🔥

Can you give it a last spin @jonathangiardino 😊

Can you give it a last spin @jonathangiardino 😊

Looking ready to ship 🚀 @pernielsentikaer! The last color differentiation was a great addition.
Thanks for the refinements! 🔥


service ip is unreachable from pod

Environmental Info:
K3s Version:
k3s version v1.29.5+k3s1 (4e53a323)
go version go1.21.9

Node(s) CPU architecture, OS, and Version:

Linux pi-node-2 6.6.28+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) aarch64 GNU/Linux

Cluster Configuration:

1 server
Describe the bug:

I've just initialized a dual stack cluster using the following command:
curl -sfL https://get.k3s.io | INSTALL_K3S_EXEC="server" sh -s - --cluster-init --cluster-cidr=fd93:c40c:7613::/56,<IP_ADDRESS>/16 --service-cidr=fd95:8606:8f22::/112,<IP_ADDRESS>/16

Afterwards, I've deployed a service and some pods:
> kubectl get services
kubernetes           ClusterIP   fd95:8606:8f22::1      <none>        443/TCP    23m
postgresql-service   ClusterIP   fd95:8606:8f22::1c82   <none>        5432/TCP   17m

Inside a pod, I can get the service's ip using the POSTGRESQL_SERVICE_SERVICE_HOST env variable:
> echo $POSTGRESQL_SERVICE_SERVICE_HOST
fd95:8606:8f22::1c82

However, that IP of the service is unreachable:
> ping fd95:8606:8f22::1c82
PING fd95:8606:8f22::1c82(fd95:8606:8f22::1c82) 56 data bytes
^C
--- fd95:8606:8f22::1c82 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1025ms
> ip -6 route
fd93:c40c:7613::/64 dev eth0 proto kernel metric 256 pref medium
fd93:c40c:7613::/56 via fd93:c40c:7613::1 dev eth0 metric 1024 pref medium
fe80::/64 dev eth0 proto kernel metric 256 pref medium
default via fd93:c40c:7613::1 dev eth0 metric 1024 pref medium

Connecting using the IP od a pod behind the service works. Since the service cidr doesn't appear in the routing tables, I suspect it didn't get added?
Expected behavior:

The pod behind the service is reachable
Actual behavior:

the pod behind the service is unreachable

Update: I've tried to run the same setup using ipv4 addresses for services by changing the order of the address families in the cluster init command:
curl -sfL https://get.k3s.io | INSTALL_K3S_EXEC="server" sh -s - --cluster-init --cluster-cidr=<IP_ADDRESS>/16,fd93:c40c:7613::/56 --service-cidr=<IP_ADDRESS>/16,fd95:8606:8f22::/112

It seems to work with that. However, I'd still prefer to use ipv6 internally.

I don't know that pings (ICMPv6) are supposed to work against service cluster IPs? Can you try hitting the service on its TCP port?


The documentation as-written does not successfully build an Azure static page.

This page is missing information regarding the github action output parameter.
hugo -D builds the output into app/public, but when creating a brand new static page using these instructions it's not clear that this needs to be specified in the github action workflow file. This probably needs to be updated on the Hugo static app build process on the backend, but probably worth explaining here?
Using exactly these instructions today, Azure Static pages with Hugo fail to build.
---End of Oryx build logs---
Oryx built the app folder but was unable to determine the location of the app artifacts. Please specify the app artifact location.

For further information, please visit the Azure Static Web Apps documentation at https://docs.microsoft.com/en-us/azure/static-web-apps/
If you believe this behavior is unexpected, please raise a GitHub issue at https://github.com/azure/static-web-apps/issues/
Exiting

Modifying the yaml file to be this fixes the build:
output_location: "public/" # Built app content directory - optional

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

ID: 878bad36-454a-063c-4100-c73f9e90aea3
Version Independent ID: b0c548c8-f830-311f-07e1-84f0ba644943
Content: Tutorial: Publish a Hugo site to Azure Static Web Apps
Content Source: articles/static-web-apps/publish-hugo.md
Service: static-web-apps
GitHub Login: @aaronpowell
Microsoft Alias: aapowell

Hi @miketheitguy , thanks for bringing this to our attention. I have assigned the issue to the content author to evaluate and update this doc as appropriate

Thanks, @miketheitguy! The Hugo preset now emits output_location: "public" and provides a successful build, so I am going to #please-close this issue.

Awesome! Appreciate it!


np.cross gives error

Reporting a bug

[x] I have tried using the latest released version of Numba (most recent is
visible in the change log (https://github.com/numba/numba/blob/master/CHANGE_LOG).
[x] I have included a self contained code sample to reproduce the problem.
i.e. it's possible to run as 'python bug.py'.

The numba implementation of numpy.cross() fails on the dimension check of the input arguments
from numba import njit
import numpy as np

@njit
def mycross(a,b):
  return np.cross(a,b)

a = np.random.random(3)
b = np.random.random(3)

mycross(a,b)

which results in the following error:
TypingError: Failed in nopython mode pipeline (step: nopython frontend)
No implementation of function Function(<function cross at 0x7f5eaefa0430>) found for signature:

 >>> cross(reflected list(int64)<iv=None>, reflected list(int64)<iv=None>)

There are 2 candidate implementations:
    - Of which 2 did not match due to:
    Overload in function 'np_cross': File: numba/np/arraymath.py: Line 4364.
      With argument(s): '(reflected list(int64)<iv=None>, reflected list(int64)<iv=None>)':
     Rejected as the implementation raised a specific error:
       UnsupportedError: Failed in nopython mode pipeline (step: analyzing bytecode)
     Use of unsupported opcode (CONTAINS_OP) found

     File "../../.local/lib/python3.9/site-packages/numba/np/arraymath.py", line 4372:
         def impl(a, b):
             <source elided>
             b_ = np.asarray(b)
             if a_.shape[-1] not in (2, 3) or b_.shape[-1] not in (2, 3):
             ^

  raised from /home/smiet/.local/lib/python3.9/site-packages/numba/core/byteflow.py:269

During: resolving callee type: Function(<function cross at 0x7f5eaefa0430>)
During: typing of call at <ipython-input-1-8c89f6d7a38d> (6)

File "<ipython-input-1-8c89f6d7a38d>", line 6:
def mycross(a,b):
  return np.cross(a,b)
  ^

though clearly the dimensions are correct.

Thanks for the report. The above is failing because you are using Python 3.9, which is not supported by any released version of Numba yet. See here: https://github.com/numba/numba/issues/6345#issuecomment-759509837 for how to get a development version with 3.9 support, or perhaps create a new environment for using Numba with a supported python (3.6, 3.7, 3.8 should all work fine)? I've tested the above code and it's working fine else. Hope this helps?

Thanks for the report. The above is failing because you are using Python 3.9, which is not supported by any released version of Numba yet. See here: https://github.com/numba/numba/issues/6345#issuecomment-759509837 for how to get a development version with 3.9 support, or perhaps create a new environment for using Numba with a supported python (3.6, 3.7, 3.8 should all work fine)? I've tested the above code and it's working fine else. Hope this helps?

Thank you, the issue has been resolved by switching to the master version of numba and llvm. Providing the installation commands using pip for reference:
pip install git+https://github.com/numba/numba
pip install git+https://github.com/numba/llvmlite

Thank you, the issue has been resolved by switching to the master version of numba and llvm. Providing the installation commands using pip for reference:
pip install git+https://github.com/numba/numba
pip install git+https://github.com/numba/llvmlite

@smiet happy to hear that you managed to resolve this issue by using development versions! As a sidenote, I would like to comment that the llvmlite you installed may not have been compiled against the custom LLVM version as required by Numba. It's probably fine for your use-case right now, but you may at some point later on, encounter some issues. So, this is just something to keep in mind in the future. You can read about it here:
https://llvmlite.readthedocs.io/en/latest/admin-guide/install.html
Also, we do provide pre-compiled llvmlite packages -- but only for conda -- doing the following
conda install -c numba numba

Should always get you the latest "nightly" pre-compiled build of both  Numba and llvmlite (with a correctly patched and compiled LLVM statically linked into the llvmlite packages).
Thanks again for following up on this and posting your solution.

@smiet happy to hear that you managed to resolve this issue by using development versions! As a sidenote, I would like to comment that the llvmlite you installed may not have been compiled against the custom LLVM version as required by Numba. It's probably fine for your use-case right now, but you may at some point later on, encounter some issues. So, this is just something to keep in mind in the future. You can read about it here:
https://llvmlite.readthedocs.io/en/latest/admin-guide/install.html
Also, we do provide pre-compiled llvmlite packages -- but only for conda -- doing the following
conda install -c numba numba

Should always get you the latest "nightly" pre-compiled build of both  Numba and llvmlite (with a correctly patched and compiled LLVM statically linked into the llvmlite packages).
Thanks again for following up on this and posting your solution.


Fix potential NullPointerException in toolsListRequestHandler

In certain scenarios, the 'params' argument could be null, resulting in a null 'request' object. This could lead to a NullPointerException when attempting to access request.cursor().

Thanks for the catch @qiangmao .
But given that currently the mcp server implementation doesn't support pagination (e.g. all tools are returned together) we don't need the request nor the logging.
I will clean this part of the code.


Package request: httptoolkit

HTTP Toolkit is an open-source tool for debugging, testing and building with HTTP(S) on Windows, Linux & Mac.
demo video
Metadata

homepage URL: https://httptoolkit.com/
source URL: https://github.com/httptoolkit/httptoolkit-desktop
license: AGPL v3.0
platforms: linux, darwin

Sorry, wasn't able to get it working. The httptoolkit-server is the difficult part. I tried building from source, however one of the dependencies tries to npm install more stuff in prebuild, so it wasn't building properly. I tried packaging the prebuilt binary but it's trying to do some auto updating and also package node with itself. I could have patched this when building from source, however the prebuilt one is minified & obfuscated so I couldn't do that.

Have you a branch to continue the work ?

+1

I've started a small bounty of 20$ on this: https://gitpay.me/#/task/843
It's not much but it would be great to have this tool on nix!

I made another attempt at packaging this and I'm pretty close to getting httptoolkit-server to compile from source. This should help with patching out stuff, since we can do it before it gets obfuscated.

if anyone needs to run this on nix the appimage provided by HttpToolkit works pretty well on nix with no extra dependencies. See the releases section and then $ appimage-run HttpToolkit-1.17.2.AppImage
Would still be great to have this as a nix package though.

Hey @TomaSajt thanks for adding this! You can claim the gitpay bounty here: https://gitpay.me/#/task/843 (I've tried to find your email to invite you but didn't have much luck) or email me at<EMAIL_ADDRESS>

Sent you an email, @Granitosaurus


VS Code - strange git behavior

VSCode Version: 1.17.0 c[ be377c0faf7574a59f84940f593a6849f12e4de7 ]
OS Version: Windows 8.1 64-bit & Linux Ubuntu 16.04.2 Gnome 3

Steps to Reproduce:
https://youtu.be/JCQgfc6OEXM
I think, initializate repository should be disabled, if folder isn't opened.
Or if it's intention, why after close and again open VS Code it isn't inicializated?
Reproduces without extensions: Yes

We should probably not allow this, much less suggest it.

Sorry, I thought you had a different issue: #35902

#35905

To keep the number of issues in our inbox on a manageable level, we're closing issues that have been on the backlog for a long time but haven't gained traction: We look at the number of votes the issue has received and the number of duplicates issues filed.
Thanks for your understanding. Happy coding!


media-lax1.inq.com

Energized Protection - block ⚡

Let's make an annoyance free, better open internet, altogether!

Issue Submit Form

  Provide the following infos properly, which will help us to resolve your issue quickly.

Issue(s):
Type x in between [ ] and make sure there isn't any space between brackets. Example; for Your Selected Issue(s), type like this - [x]
You can select more than one category of issues if you need to!

[x] Whitelist
[ ] Blacklist
[ ] App Broken
[ ] Website Broken
[ ] Request
[ ] Other Issue

Pack(s):
Write the name of the pack(s) you are using.

Pack(s) Name: blu

Extension(s):
Also name the extension(s) if you are using any. If you don't then leave it blank.

Extension(s) Name:

Domain(s):
If you are submitting this issue for whitelist/blacklist issue, send us the domain(s) for whitelisting/blacklisting here. Kindly use the Code Tag to prevent tracking.

Domain(s):

media-lax1.inq.com

Your Config:
Just to ensure there is no issues or conflicts with other app/software/magisk module/extension/source list.
Make sure you are running Energized Protection Service only.

Client:

Version:

Details:
Write us a lil bit more about your issue or query. You can attach any screen shot or log of the issue or advert, this will help to highlight it.

Your Issue Detail:
Breaks live chat on Verizon website.

Thank you for making Energized Protection great, with your kind help!
A project by Ador with ❤

I can't seem to find it in the domains version of Blu as of at the time of writing. Which I presume is a good thing.

And since I see it in Energized Unblock as well, which is the centralised whitelist, this seems like a solved case to me.


common orm and reactive persistence tests #367

Rebased and Merged https://github.com/hibernate/hibernate-reactive/pull/402


Mike pl native trigger

just try to test trigger pl by changes in native repo

Can you please include something like [IGNORE] or [TESTING] in your PR titles?


Notificationsource Implementation

Implements NotificationSource

Giving this a quick look over, it appears to be very similar to Publisher (#170). So long as comments from there are applied here too, I do not see a reason this could not be approved and merged at the same time.


[Proposal] Support Loop Device for Demo

Loop Device is easy to demo
ref to https://github.com/topolvm/topolvm/blob/main/example/Makefile#L91

remind

to be discuss

loop device is not a best choice for HwameiStor demo, as that lots of features can't work for loop device, such as disk health monitoring, disk discovery, etc ...
For demo, it's easy to add a disk into a VM, which is better.

even not full function can be demo, but at least it can running inside kind. Yes,  it's worth only when it's not a big effort , of coz.


Load failure for encrypted Media Overlays SMIL files, Content Filter Chain out of date with late registration of Content Module

Same as with NavDoc:
https://github.com/readium/readium-sdk/issues/262

Fixed in feature/lcp:
https://github.com/readium/readium-sdk/commit/24e004ae197e3bd90a5c5c1e67901810396e7d6e

Reopening, as not fixed in develop (only in feature branch)


Integration tests for latestmethod

Test scenarios for latest method:

Scenario: Retrieve the latest LicenseRecord for a valid Pointer Record ID.

Steps to reproduce:

Call latest() method with a valid Pointer Record ID.

Possible solutions or implementations:

Verify that the returned LicenseRecord object is not null and has the expected properties.

Expected result: The latest() method should return a non-null LicenseRecord object with the expected properties.

Scenario: Retrieve the latest LicenseRecord for a non-existent Pointer Record ID.

Steps to reproduce:

Call latest() method with an invalid Pointer Record ID.

Possible solutions or implementations:

Verify that the returned LicenseRecord object is null

outdated


feat(azure): Add HttpRequest.Builder extension methods

Added the extension methods for

Azure OpenAI path segments
Bearer Authentication header per request for Azure Entra ID

@RobertCraigie It seems like the feature branch next hasn't merged the latest changes from main branch yet, which is why the first Azure PR is missing.

@RobertCraigie It seems like the feature branch next hasn't merged the latest changes from main branch yet, which is why the first Azure PR is missing. Would you like some help with merging the latest changes from main into next?

@mssfang as far as I can tell, all the branches are in sync right now. Can you clarify what you mean?

@RobertCraigie It seems like the feature branch next hasn't merged the latest changes from main branch yet, which is why the first Azure PR is missing. Would you like some help with merging the latest changes from main into next?

@mssfang as far as I can tell, all the branches are in sync right now. Can you clarify what you mean?

Sorry. I meant branches are missing changes from this PR

hmm it looks like some of those changes are missing in the stainless-sdks/openai-java repo as well... I'm looking into it

@mssfang okay I think the repo is in the correct state now, sorry about that! can you double check the diff in this PR? then we can merge this :)

@RobertCraigie Thank you. It looks correct. Let's merge it!

merged, thanks @mssfang!


refactor(cli): inefficient policy sort

Summary
During policy list operation we were sorting the policy list for each entry which is very inefficient.
Also abstract sorting in case future methods need to take advantage of the sorting algorithm
How did you test this change?
Existing integration testing
Issue
https://lacework.atlassian.net/browse/ALLY-950

@afiune , we can transition from integration to unit testing here.

We're going to have a chicken and egg problem with respect to lacework-content-all changes, so I added a pipeline locked to this branch:
https://g.codefresh.io/build/6241d77e145328fde5c5b0d2

@afiune / @dmurray-lacework , anything else needed here?


maxWidth with YGPercentValue doesn't work properly in YGFlexDirectionRow container

Issues and Steps to Reproduce
maxWidth constraint is applied twice when measuring a view YGNodeBoundAxisWithinMinAndMax resolves max value with axisSize but axisSize was already constrained to the specified maxWidth value. So it basically does it twice.

Set maxWidth toYGPercentValue on the second view in a YGFlexDirectionRow container
Observe incorrect layout

Expected Behavior
Expected for the second subview in the example to be at most half its superview size.
Actual Behavior
The second subview in the example is 1/4 of the size.
Link to Code
                UIView *line1 = [[UIView alloc] init];
                [line1 configureLayoutWithBlock:^(YGLayout *layout) {
                    layout.enabled = YES;
                    layout.flexDirection = YGFlexDirectionRow;
                    layout.justifyContent = YGJustifySpaceBetween;
                    layout.alignItems = YGAlignCenter;
                    layout.paddingTop = YGPointValue(UBECardInfoViewTitleLabelMargins.top);
                }];
                line1.backgroundColor = [UBColor whiteColor];

                [self.titleLabel configureLayoutWithBlock:^(YGLayout *layout) {
                    layout.enabled = YES;
                }];
                [line1 addSubview:self.titleLabel];

                [self.subtitleLabel configureLayoutWithBlock:^(YGLayout *layout) {
                    layout.enabled = YES;
                    layout.marginTop = YGPointValue(2.0f);
                    layout.marginLeft = YGPointValue(UBEFeedItemCardCellDefaultMargin);
                    layout.maxWidth = YGPercentValue(50.0f);
                }];
                [line1 addSubview:self.subtitleLabel];
                [self insertSubview:line1 atIndex:0];

Hi @kostiadombrovsky .
I tried to reproduce, but this works for me, the size is correctly 60px wide:

could you please provide a more complete repo?

Sorry @kostiadombrovsky , found the problem! I pushed a PR at #649 . Thank you for the report.


Exception when using 4.5 client with config.UseHttp=true while running Fiddler.

Using AWS SDK for .NET 4.5, I wanted to see how AWS requests and responses look on the wire. To do that I set config.UserHttp=true to run in clear HTTP instead of SSL, and ran Fiddler. This produced an exception below. If Fiddler is stopped or exited, or if HTTPS is used, the problem does not occur. NET 3.5 client does not have this problem either - its traffic shows in Fiddler just fine.
Exception is thrown in AmazonWebServiceClient class, method:
private async Task InvokeConfiguredRequest(WebRequestState state, CancellationToken cancellationToken) where T : AmazonWebServiceResponse.
at
responseMessage = await httpClient.SendAsync(requestMessage, cancellationToken).ConfigureAwait(continueOnCapturedContext: false);
line.
Similar problem reported at http://social.msdn.microsoft.com/Forums/vstudio/en-US/6a745a51-8a7b-4a5c-9f07-be02cc01278c/httpwebrequest-in-c-do-not-work-with-net-45?prof=required. .
Exceptions chain:
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1.ConfiguredTaskAwaiter.GetResult()    at Amazon.Runtime.AmazonWebServiceClient.<InvokeConfiguredRequest>d__b1.MoveNext() in c:!Projects\Fabric.WebServices\aws-sdk-net\AWSSDK_DotNet45\Amazon.Runtime\AmazonWebServiceClient.cs:line 143
Inner exception:
at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult, TransportContext& context)
at System.Net.Http.HttpClientHandler.GetRequestStreamCallback(IAsyncResult ar)
The innermost exception is:
at System.DomainNameHelper.IdnEquivalent(String hostname)
at System.Uri.get_IdnHost()
at System.Net.HttpWebRequest.GetSafeHostAndPort(Uri sourceUri, Boolean addDefaultPort, Boolean forcePunycode)
at System.Net.HttpWebRequest.GenerateProxyRequestLine(Int32 headersSize)
at System.Net.HttpWebRequest.SerializeHeaders()
at System.Net.HttpWebRequest.EndSubmitRequest()
at System.Net.HttpWebRequest.SetRequestSubmitDone(ConnectStream submitStream)
at System.Net.Connection.CompleteConnection(Boolean async, HttpWebRequest request)

Closing this issue, as it's not reproducible and OP is not working on this anymore.


Unescaped $ in template string throw unexpected EOF error

Trying to transform the following valid javascript
let foo = `$`;

results in an exception from Shimport. As far as I can tell, the unescaped $ can appear anywhere in the string and cause this error. If an unescaped $ in a template string is not followed by a {, Shimport should just treat it like a regular character.

Fixed in 0.0.15 — thanks


Weird exception related to switch to Python 3

I got this traceback today, which I hadn't seen before, from the UserActivity queue worker:
SystemExit: 0

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/zulip/deployments/2017-08-16-14-17-59/zerver/worker/queue_processors.py", line 120, in consume_wrapper
    self.consume(data)
  File "/home/zulip/deployments/2017-08-16-14-17-59/zerver/worker/queue_processors.py", line 207, in consume
    do_update_user_activity(user_profile, client, query, log_time)
  File "/home/zulip/deployments/2017-08-16-14-17-59/zerver/decorator.py", line 623, in wrapped_func
    ret = func(*args, **kwargs)
  File "/home/zulip/deployments/2017-08-16-14-17-59/zerver/lib/actions.py", line 2483, in do_update_user_activity
    defaults={'last_visit': log_time, 'count': 0})
  File "/home/zulip/deployments/2017-08-16-14-17-59/zulip-py3-venv/lib/python3.5/site-packages/django/db/models/manager.py", line 85, in manager_method
    return getattr(self.get_queryset(), name)(*args, **kwargs)
  File "/home/zulip/deployments/2017-08-16-14-17-59/zulip-py3-venv/lib/python3.5/site-packages/django/db/models/query.py", line 464, in get_or_create
    return self.get(**lookup), False
  File "/home/zulip/deployments/2017-08-16-14-17-59/zulip-py3-venv/lib/python3.5/site-packages/django/db/models/query.py", line 374, in get
    num = len(clone)
  File "/home/zulip/deployments/2017-08-16-14-17-59/zulip-py3-venv/lib/python3.5/site-packages/django/db/models/query.py", line 232, in __len__
    self._fetch_all()
  File "/home/zulip/deployments/2017-08-16-14-17-59/zulip-py3-venv/lib/python3.5/site-packages/django/db/models/query.py", line 1105, in _fetch_all
    self._result_cache = list(self._iterable_class(self))
  File "/home/zulip/deployments/2017-08-16-14-17-59/zulip-py3-venv/lib/python3.5/site-packages/django/db/models/query.py", line 53, in __iter__
    results = compiler.execute_sql(chunked_fetch=self.chunked_fetch)
  File "/home/zulip/deployments/2017-08-16-14-17-59/zulip-py3-venv/lib/python3.5/site-packages/django/db/models/sql/compiler.py", line 886, in execute_sql
    raise original_exception
  File "/home/zulip/deployments/2017-08-16-14-17-59/zulip-py3-venv/lib/python3.5/site-packages/django/db/models/sql/compiler.py", line 876, in execute_sql
    cursor.execute(sql, params)
  File "/home/zulip/deployments/2017-08-16-14-17-59/zulip-py3-venv/lib/python3.5/site-packages/django/db/backends/utils.py", line 65, in execute
    return self.cursor.execute(sql, params)
  File "/home/zulip/deployments/2017-08-16-14-17-59/zerver/lib/db.py", line 32, in execute
    return wrapper_execute(self, super(TimeTrackingCursor, self).execute, query, vars)
  File "/home/zulip/deployments/2017-08-16-14-17-59/zerver/lib/db.py", line 19, in wrapper_execute
    return action(sql, params)
  File "/usr/lib/python3.5/encodings/utf_8.py", line 16, in decode
    return codecs.utf_8_decode(input, errors, True)
SystemError: <built-in function utf_8_decode> returned a result with an error set

@gnprice this is pretty clearly Python 3 related; can you investigate?

Looks like this is https://github.com/psycopg/psycopg2/551 -- not actually Unicode- or fundamentally Python 3-related, but probably related to this change which went into CPython 3.5.
The bug in psycopg should be fixed in their 2.7.2, so we should upgrade to that.


Catalogue: More coming soon

Add a label saying that there will be more questionnaires soon

 Library of standard question sets


about decouple ISP enhancement

Hello,
I have a small query regarding your outstanding article and would greatly appreciate your guidance.
In the paper, you mention the use of a bilateral grid to "decouple ISP enhancement" while simultaneously reconstructing the radiance field without the camera's ISP enhancement, wouldn't this approach result in an image that resembles the greenish raw output from the camera sensor? However, it appears that the paper does not reconstruct the radiance field without ISP enhancement, as the test results directly compare the rendered views with the corresponding ground truth sRGB.  I would like to know if the description of "decoupling ISP enhancement" in the paper is reasonable? Or is the primary function of the bilateral grid proposed in the paper to learn the enhancement for the inconsistencies across multiple views?
Thank you for your time and assistance.

Hi,
Thank you very much for your question!
Yes, "decouple ISP enhancement" refers to disentangling inconsistent ISP enhancement across input views.
Given multi-view images only, inversion of the whole ISP pipeline is unlikely feasible. Our workaround is to inverse part of the ISP. In this way, radiance fields will output renderings with average processing, and per-view bilateral grids will express the specific processing for each view.

Your response has resolved my confusion. Thank you very much for your detailed explanation!


Docs improvements 2

TL;DR
Refresh the docs and make it easier to start with the seal.
Details

[x] revamp getting started

add info about virtualenv
show example command to start seal pointing to a kubectl in interactive mode
show example command with a basic policy file killing random pods from all namespaces

[x] add a section on writing policies

write up a tutorial on how to write a policy, with some examples

[x] revamp setup

cleanup the arguments which are no longer needed
remove unnecessary arguments from the minikube examples
make it easy to understand that you can run with a cloud driver or without

add some kind of architecture/concepts/terminology section
[x] integrate docs-schema
[x] explain when/why you should use each mode
[x] fix all the relative links

Resolves https://github.com/bloomberg/powerfulseal/issues/233
Resolves https://github.com/bloomberg/powerfulseal/issues/240

I'm taking my time to review the PR. Tons of files :smile: :rocket:

I'm taking my time to review the PR. Tons of files 😄 🚀

BTW, @dgzlopes I like your idea for the asciicinema - do you think you could help with that bit?

I'm taking my time to review the PR. Tons of files smile rocket

BTW, @dgzlopes I like your idea for the Asciicinema - do you think you could help with that bit?

Yeah, sure. I was thinking about recording it locally and uploading it to the provider (Asciinema or another... they are all similar). Then we can embed it in our new docs :)
Also, we can keep the recording versioned in git, so we can make small changes without having to re-record it.
I can work on it tomorrow morning.

I'm taking my time to review the PR. Tons of files smile rocket

BTW, @dgzlopes I like your idea for the Asciicinema - do you think you could help with that bit?

Yeah, sure. I was thinking about recording it locally and uploading it to the provider (Asciinema or another... they are all similar). Then we can embed it in our new docs :)
Also, we can keep the recording versioned in git, so we can make small changes without having to re-record it.
I can work on it tomorrow morning.

That sounds fantastic 👍


⚠ Bofrost.de has degraded performance

In e2753b9, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1674 ms

Resolved: Bofrost.de performance has improved in 3a88d89 after 310 days, 2 hours, 14 minutes.


wrap tabbar elements to new line

fixes #420
Reviewers:
@mike-robertson
@dartharaknus
@blukai

Why don't we just break onto multiple lines in one screen size and scroll on others? I think breaking onto multiple lines is very bad in mobile; at least one whole screen length will be tabs before content.


normalize IRIs to a canonical namespace before compacting to a CURIE using the biolink-model context

See #199

For now I think this can be done instead with a new file we maintain: prefix-overrides.yaml. We can merge this last in our prefixes: https://github.com/NCATS-Tangerine/cam-kp-api/blob/0080a415cd5ebceecfdc062476b3571e56528f5a/src/main/scala/org/renci/cam/Biolink.scala#L29
This way we map to the right CURIE from the IRI forms in our database. Start with the WB prefix for this file.


use provided providerFields in my-provider-fields directive

same as #922 but against release/0.9.9 branch

:+1: pending travis


Test with GitHub Enterprise

Most of our testing so far has been on public GitHub. Re-test against GitHub Enterprise.

@akihikokuroda I know you mentioned this yesterday on an IBM scrum, are you planning to pick this up? We have experience here before from the Tekton Webhooks Extension work and previous projects at IBM - using the Git client without providing a URL results in github.com and we need a way to look at the URL and use that as the Git provider surely (and IIRC that was a simple parameter passed in to the client).

You'll want to add a new command-line option for the git endpoint, and thread it through to here (via the factory in the service manager).
https://github.com/rhd-gitops-example/services/blob/master/pkg/git/client.go#L13
The factory code is here, https://github.com/jenkins-x/go-scm/blob/master/scm/factory/factory.go#L28 and as you'll spot, you can pass a serverURL (which can default to "".

Ok.  Do you have any suggestions for the option name?


fix: update solhint

Please read contributing guidelines and remove this line.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#9399  👈
#9398
#9328
#9297
#9296
#9247
#9246
#9084
#8942
#8941
#8940
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @LHerskind and the rest of your teammates on  Graphite


Upgrade to Codecov node package

We are depreciating the codecov.io package in-favor of the codecov package: https://github.com/codecov/codecov-node
Thanks @eddiemoore  :)

Thanks. Will update the rest of the stuff to use this


[improve]support string type record in one topic to multiple tables

In the function of https://github.com/apache/doris-kafka-connector/pull/58 supporting one topic to multiple tables, only the data types converted using the org.apache.kafka.connect.json.JsonConverter converter are supported. For the converter of org.apache.kafka.connect.storage.StringConverter, Currently it is not supported.
This pr will support records of string type.

Hi @chuang-wang-pre , I noticed that string type records are not supported and need to be strongly bound to the converter of org.apache.kafka.connect.json.JsonConverter, so I supported string type.
Please take a look.


moodle: 4.4.1 -> 4.4.3

Description of changes
Update moodle
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Obsolete by https://github.com/NixOS/nixpkgs/pull/348684? Perhaps the change in nixos/modules/services/web-apps/moodle.nix is necessary?

Fixes CVE-2024-45691, CVE-2024-45690, CVE-2024-45689, CVE-2024-43440, CVE-2024-43439, CVE-2024-43438, CVE-2024-43437, CVE-2024-43436, CVE-2024-43435, CVE-2024-43434, CVE-2024-43433, CVE-2024-43432, CVE-2024-43431, CVE-2024-43430, CVE-2024-43429, CVE-2024-43428, CVE-2024-43427, CVE-2024-43426, CVE-2024-43425.


Socket write should be thread safe

Thanks for the PR it has been merged. Do you mind closing this?


simplify to_patch_embedding using Conv2d

Hi,
Thanks for this great repo!
I have a suggestion for a simpler implementation for to_patch_embedding. Instead of:
        self.to_patch_embedding = nn.Sequential(
            Rearrange('b c (h p1) (w p2) -> b (h w) (p1 p2 c)', p1 = patch_height, p2 = patch_width),
            nn.Linear(patch_dim, dim),
        )

one can use a Conv2d layer, with patch_size kernels, and with a patch_size stride:
        self.to_patch_embedding = nn.Sequential(
            nn.Conv2d(in_channels=channels, out_channels=dim, kernel_size=patch_size, stride=patch_size),
            nn.Flatten(start_dim=2, end_dim=-1)
        )

This way, the extension for 3D vision transformers much simpler (just change to nn.Conv3D).
Thanks again!

Link to relevant lines:
https://github.com/lucidrains/vit-pytorch/blob/4b8f5bc90002a5506d765c811b554760d8dd6ee7/vit_pytorch/vit.py#L94

It also requires to add a transpose in the forward pass
        x = self.to_patch_embedding(img).transpose(1, 2)

Wonderful suggestion！

Wonderful suggestion！

@avihu111 ohh nice, yea, i think its a matter of preference. personally prefer einops better when there is no overlapping
let me know if https://github.com/lucidrains/vit-pytorch#3d-vit helps


[TA] [Service Bug] temporally having 'latest' as the default value of 'modelVersion'

After service support null value for 'modelVersion', remove this temporally default value, 'latest'.

Do we have a tentative date/roll-out period when this should be fixed/supported by the service team?

still having this issue in the v3.1-preview.4. Looking for it get to be resolved before v3.1-preview.5 is released

service team fixed it. Verified on v3.1-preview.5


Lint CSS

Using Stylelint as a PostCSS Plugin, we should lint the stylesheets for consistency.
The rules should fit the current style of the existing CSS.

Note: If you submit a PR, do it against the v3.0.0 branch please!

Giving this one a shot

:+1:

Done by @brotzky, thanks for the amazing work!

:+1:


Use binary data format for tx payloads in http-node

Currently, all payloads used between http node and the rollup provider implementation are test. This is very inefficient for the requests/responses containing transactions. It would be better if we changed these to use binary payloads.

I just implemented this in https://github.com/AztecProtocol/aztec-packages/pull/929 . I think it would make sense to do the same for logs.


overwriting z-index property

Im trying to set a z-index value in a div that can be dragged, and the problem is that the module adds these classes "react-draggable react-draggable-dragged" automatically to the element, which seem to prevent me from putting the z-index i want, how can i manage to overwrite it?
thank you

Those classes don't prevent you from setting your own styles. Add your own classes or your own overriding css.

thank you, closing this,
could you please help me with https://github.com/react-grid-layout/react-draggable/issues/603, Im really stuck with that one, thank you


Updated path of the security scan report

Updated path of the security scan report

Actions failed, so closing the PR


How can these images be run locally in Docker for testing?

Where are the built images uploaded to?

We currently generate them and store them privately. I think you might be interested in #176 though.


Add figures and illustrations to tutorial

Add figures and illustration to PySparkTutorial.ipynb in order to enhance understanding of the reader. Ideas would be graphics for joins, groupby, aggregations and window functions as well as the inner workings of PySpark

This has been done 👍


Fix github workflows to run frontend checks as well

Background:
The current github actions does not run frontend checks. When selected NextJS for frontend.
 But it is missing the configuration for "cache-dependency-path" on github. We need to configure and test with both github and bitbucket


question: Custom check definition help

Similar to issue #1000 I am trying to write a custom check for security group and security group rule resources who have an open cidr <IP_ADDRESS>/0 on either port 22 or 3389.
I tried modifying the example given in the issue conversation, but it doesn't seem to work for my test cases.
sg rule custom check:
requiredTypes: [resource]
requiredLabels: [aws_security_group_rule]
matchSpec:
  action: or
  predicateMatchSpec:
  - name: type
    action: notEqual
    value: ingress
  - action: or
    predicateMatchSpec:
    - name: cidr_blocks
      action: notContains
      value: <IP_ADDRESS>/0
    - name: from_port
      action: isNone
      value: [22, 3389]

sg custom check:
matchSpec:
name: ingress
action: notPresent
subMatch:
  action: or
  predicateMatchSpec:
  - name: cidr_blocks
    action: notContains
    value: <IP_ADDRESS>/0
  - name: from_port
    action: isNone
    value: [22, 3389]`

test cases that should be marked:
resource "aws_security_group_rule" "rule22" {
  type              = "ingress"
  description       = "should be marked"
  from_port         = 22
  to_port           = 22
  protocol          = "tcp"
  cidr_blocks       = ["<IP_ADDRESS>/0"]
  security_group_id = "sg-03eee855906d90157"
}
resource "aws_security_group" "sg22" {
  name        = "allow_all"
  description = "Allow all inbound traffic on ports 22 and 3389"
  vpc_id      = aws_vpc.main.id
  ingress {
    description      = "open to internet"
    from_port        = 22
    to_port          = 22
    protocol         = "tcp"
    cidr_blocks      = ["<IP_ADDRESS>/0"]
  }
}
resource "aws_security_group_rule" "rule3389" {
  type              = "ingress"
  description       = "open to internet"
  from_port         = 3389
  to_port           = 3389
  protocol          = "tcp"
  cidr_blocks       = ["<IP_ADDRESS>/0"]
  security_group_id = "sg-03eee855906d90157"
}
resource "aws_security_group" "sg3389" {
  name        = "allow_all"
  description = "Allow all inbound traffic on ports 22 and 3389"
  vpc_id      = aws_vpc.main.id
  ingress {
    description      = "open to internet"
    from_port        = 3389
    to_port          = 3389
    protocol         = "tcp"
    cidr_blocks      = ["<IP_ADDRESS>/0"]
  }
}

test cases that should not be marked:
resource "aws_security_group_rule" "pass_specific" {
  type              = "ingress"
  description       = "this should not be marked"
  from_port         = 3872
  to_port           = 3872
  protocol          = "tcp"
  cidr_blocks       = [<list of values redacted>]
  security_group_id = "sg-1234567890"
}
resource "aws_security_group" "pass_specific_sg" {
  name        = "testsg_pass"
  description = "this should not be marked"
  vpc_id      = aws_vpc.main.id
  ingress {
    description      = "Ingress from UPN Oracle"
    from_port        = 3872
    to_port          = 3872
    protocol         = "tcp"
    cidr_blocks      = [<list of values redacted>]
  }
}

resource "aws_security_group_rule" "pass_all" {
  type              = "egress"
  description       = "egress type should pass"
  from_port         = 3390
  to_port           = 3390
  protocol          = "tcp"
  cidr_blocks       = ["<IP_ADDRESS>/0"]
  security_group_id = "sg-1234567890"
}
resource "aws_security_group" "pass_all" {
  name        = "testsg_pass_egress"
  description = "egress should pass"
  vpc_id      = aws_vpc.main.id
  egress {
    description      = "egress should pass"
    from_port        = 3390
    to_port          = 3390
    protocol         = "tcp"
    cidr_blocks      = ["<IP_ADDRESS>/0"]
  }
}

resource "aws_security_group_rule" "pass_egress" {
  type              = "egress"
  description       = "egress type should pass"
  from_port         = 3389
  to_port           = 3389
  protocol          = "tcp"
  cidr_blocks       = ["<IP_ADDRESS>/0"]
  security_group_id = "sg-1234567890"
}
resource "aws_security_group" "pass_egress" {
  name        = "testsg_pass_egress"
  description = "egress should pass"
  vpc_id      = aws_vpc.main.id
  egress {
    description      = "egress should pass"
    from_port        = 3389
    to_port          = 3389
    protocol         = "tcp"
    cidr_blocks      = ["<IP_ADDRESS>/0"]
  }
}

resource "aws_security_group_rule" "pass_port" {
  type              = "ingress"
  description       = "ports other than 3389 and 22 should pass"
  from_port         = 3390
  to_port           = 3390
  protocol          = "tcp"
  cidr_blocks       = ["<IP_ADDRESS>/0"]
  security_group_id = "sg-1234567890"
}
resource "aws_security_group" "pass_port" {
  name        = "testsg_pass_port"
  description = "ports other than 3389 and 22 should pass"
  vpc_id      = aws_vpc.main.id
  ingress {
    description      = "ports other than 3389 and 22 should pass"
    from_port        = 23
    to_port          = 23
    protocol         = "tcp"
    cidr_blocks      = ["<IP_ADDRESS>/0"]
  }
}

resource "aws_security_group_rule" "pass_cidr" {
  type              = "ingress"
  description       = "cidr blocks without 0s regardless of port should pass"
  from_port         = 22
  to_port           = 22
  protocol          = "tcp"
  cidr_blocks       = ["<IP_ADDRESS>/0"]
  security_group_id = "sg-1234567890"
}
resource "aws_security_group" "pass_cidr" {
  name        = "testsg_pass_cidr"
  description = "ports other than 3389 and 22 should pass"
  vpc_id      = aws_vpc.main.id
  ingress {
    description      = "ports other than 3389 and 22 should pass"
    from_port        = 22
    to_port          = 22
    protocol         = "tcp"
    cidr_blocks      = ["<IP_ADDRESS>/0"]
  }
}

to add and potentially raise a bug,
a simple check to match any security group with an ingress rule
requiredTypes: [resource]
requiredLabels: [aws_security_group]
matchSpec:
  name: ingress
  action: notPresent

marks the following tf config as expected:
resource "aws_security_group" "pass_cidr" {
  name        = "testsg_pass_cidr"
  description = "ports other than 3389 and 22 should pass"
  vpc_id      = aws_vpc.main.id
  ingress {
    description      = "ports other than 3389 and 22 should pass"
    from_port        = 22
    to_port          = 22
    protocol         = "tcp"
    cidr_blocks      = ["<IP_ADDRESS>/0"]
  }
}

adding to custom tfsec rule to match security groups with ‘<IP_ADDRESS>/0’ in the cidr_blocks list value
requiredTypes: [resource]
requiredLabels: [aws_security_group]
matchSpec:
  name: ingress
  action: notPresent
  subMatch:
    name: cidr_blocks
    action: notContains
    value: <IP_ADDRESS>/0

unexpectedly matches the above config as well

Hi @mobershall !
The developers efforts have moved to Trivy. You can write your own policies.
/cc @simar7


Align with upstream 08/08

First step to deploy frr-k8s via cno instead of directly. Next step would be adding the env vars that actually enable it once the cno changes get in.

/lgtm


Add message feedback

You can only send messages if there is at least one other person on your team.  That's great, but it's tempting to just send messages because it's there.  If you make a team and it's just you, you don't get a message.  Which is the way it should be, except that we'd like to let the user know that there are no team members to message.  The .alertDanger style would be appropriate here.

I'm moving this to V2 and throwing it back because I've spent too long with it already.  This commit at least makes the null values a bit more neatly presented and relies only on having teams to send the message (rather than just already having messages in your inbox).  userHasTeams ends up being true when it shouldn't be, but I can't find the source of the mismatch.  My best guess is
it's in setupProfileListener which does some business to filter out old teams and new teams.

Closing this because https://github.com/johnneed/GreenUpVermont/issues/217 addresses most of this, plus the behavior has since changed.  You currently can message your team even if it's just you.  But at least you can't message a team you're not on, so that's probably good enough for now.


Add support for semicolon separated value

For lack of a better name, I've called it ssv for semicolon separated values.
At this point the csv.lua, tsv.lua, and now ssv.lua files are nearly identical and one could refactor instead. Let me know if you'd prefer that approach.

This should resolved issue #3 , I forgot to mention


⚠ Bofrost.de has degraded performance

In f63accc, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 2214 ms

Resolved: Bofrost.de performance has improved in ba02ea4 after 7 minutes.


Added Launch Library support

Implemented threshold to fetch launch dates from Launch Library API.
I attach a txt to compare both APIs rapidly.
example_queries.txt

Just one thing to maybe consider:

This assumes that the mission name will be exactly the same as what they have in LL, which might not always be the case. We might want to fuzzy match to something reasonably close.

I have implemented the fuzzy match and also reduced the number of requests to the LL API to 1, instead of one per launch to update.
Let me know what you think.

Also, it may be a good idea to hide the new fields 'last_wiki_update' and 'is_date_from_wiki' from the API responses.

Might be useful to some? I'd rather keep them in the response.
Everything looks good, I'll merge this shortly.
Overall awesome work, with lots of good comments, appreciate you knocking this out for us 👍

Thank you! Glad to help 👍
Also, I have tons of free time, so I'm thinking of contributing with another feature, like:

Twitter scraping for live updates
Making the backup APIs a list instead of just Launch Library. Having different "Providers" from which to gather the data. E.g. Twitter, other APIs, etc.
Writing tests for the "scripts" folder
Etc

Let me know which one as a higher priority, or another feature that you need help with, and I'll be glad to create an issue and start working on it.
Cheers!


Auto linking breaks if markdown is in the URL.

For example an URL like: http://example.com/this_is_broken will render the _is_ as italic instead of considering it as part of the URL, causing the autolinking to only link the http://example.com. Copy and pasting the URL will also no longer world as it will be rendered as http://example.com/thisisbroken instead of http://example.com/this_is_broken

Please, use demo permalinks for live examples.
Here i don't see any problems with italic. The only known issues were described in #38.

It's indeed the issue described in #38 closing this as duplicate


Set tel type of input

FIXED:

Set up dev:hello-world command
Added example custom-input-rawhandler command dev:custom-input-rawhandler
Make js:dev and cd example/package && npm run start as a live reload dev server!
Fixed some dev conflicts
Connected examples as local one react

TODOS;

Set up css dev server to concurrently stdout

I needed to solve this problem https://github.com/Hacker0x01/react-datepicker/issues/3556 and I solved it in this example.


snippets: add inline LaTeX

Added inline LaTeX. I'm not sure if it makes sense to copy the UI code out of the latex/ directory, but open to changing that.

Thanks again. LGTM.
if you could, in future, do a regular commit, this way it is easier for me to see an incremental change as opposite to force push all the changes again.

Sounds good! I really appreciate the notes btw (for ex. regular commit instead of force push) — I'm not really sure what best practices are for GitHub/open source contributions, so the pointers are helpful.
BTW, I think merging is blocked for me still.

sent invite, try once accepted

use Squash and merge

accepted invite, still restricts to authorized users. No worries, it's not an issue if I can't do them myself (just wanted to give a heads up)

try now please

done!

@MykolaGolubyev bit of a lack of foresight on my part — inline LaTeX doesn't work with curly braces because it gets parsed as JSON. We could generate the freeParam in PluginParams using a stored String value, but I'm not sure how best to handle the JSON parsing.
It happens here in PluginParams: https://github.com/testingisdocumenting/znai/blob/682c09312852c2a50909830ea7b24d95bda9bfb1/znai-core/src/main/java/org/testingisdocumenting/znai/extensions/PluginParams.java#L83
We could set opts to an empty map if pluginId.equals("latex"), or we could wrap with try/catch (... seems bad).
We could also write a separate LatexPluginParams (or something) that's used here: https://github.com/testingisdocumenting/znai/blob/c87971b90ef1657f9321b4a0a2b2539060ab4c68/znai-core/src/main/java/org/testingisdocumenting/znai/parser/commonmark/MarkdownVisitor.java#L109
Any thoughts or better ideas?

@evinaik do you have telegram or other messengers? We could discuss things like that offline if you prefer. GitHub email notification makes it harder to see what is the new message and you need to scroll through.
To handle special symbols in other non-inline plugins like CliCommand we allow users to pass the actual content as a param value say {cmd: "command with {}"} instead of a free form param. Maybe that's something we can do here as well?

Yeah that would be good — what's the best way to share the contact? Not sure if it's just phone number.
That would work. I'll update with changes — and let me know how to share the messenger info!


esbuild: 0.16.1 -> 0.16.7

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/evanw/esbuild/releases.
meta.description for esbuild is: "An extremely fast JavaScript bundler"
meta.homepage for esbuild is: "https://esbuild.github.io"
meta.changelog for esbuild is: "https://github.com/evanw/esbuild/blob/v0.16.3/CHANGELOG.md"
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.16.3 with grep in /nix/store/vrsz06ydmxxq1p34zhqyh5i8baqn0n8f-esbuild-0.16.3
found 0.16.3 in filename of file in /nix/store/vrsz06ydmxxq1p34zhqyh5i8baqn0n8f-esbuild-0.16.3

Rebuild report (if merged into master) (click to expand)

8 total rebuild path(s)

8 package rebuild(s)

First fifty rebuilds by attrpath
code-server
esbuild
libsForQt5.bismuth
openvscode-server
plasma5Packages.bismuth
quarto
vscode-extensions.matklad.rust-analyzer
vscode-extensions.rust-lang.rust-analyzer

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/vrsz06ydmxxq1p34zhqyh5i8baqn0n8f-esbuild-0.16.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A esbuild https://github.com/r-ryantm/nixpkgs/archive/3846f52096aa48fe0700da198bd1bdd4acd82642.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/vrsz06ydmxxq1p34zhqyh5i8baqn0n8f-esbuild-0.16.3
ls -la /nix/store/vrsz06ydmxxq1p34zhqyh5i8baqn0n8f-esbuild-0.16.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

6 packages built:

code-server
esbuild
libsForQt5.bismuth
openvscode-server
quarto
vscode-extensions.matklad.rust-analyzer

Maintainer pings
cc @Lucus16 @marsam for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/esbuild/versions.
meta.description for esbuild is: "An extremely fast JavaScript bundler"
meta.homepage for esbuild is: "https://esbuild.github.io"
meta.changelog for esbuild is: "https://github.com/evanw/esbuild/blob/v0.16.4/CHANGELOG.md"
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.16.4 with grep in /nix/store/0nx96ka1mggvsrgic0mmq1r4jql1hgqc-esbuild-0.16.4
found 0.16.4 in filename of file in /nix/store/0nx96ka1mggvsrgic0mmq1r4jql1hgqc-esbuild-0.16.4

Rebuild report (if merged into master) (click to expand)

8 total rebuild path(s)

8 package rebuild(s)

First fifty rebuilds by attrpath
code-server
esbuild
libsForQt5.bismuth
openvscode-server
plasma5Packages.bismuth
quarto
vscode-extensions.matklad.rust-analyzer
vscode-extensions.rust-lang.rust-analyzer

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/0nx96ka1mggvsrgic0mmq1r4jql1hgqc-esbuild-0.16.4 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A esbuild https://github.com/r-ryantm/nixpkgs/archive/4a32d2006e09d383d4f221042b949fa06c34d8f2.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/0nx96ka1mggvsrgic0mmq1r4jql1hgqc-esbuild-0.16.4
ls -la /nix/store/0nx96ka1mggvsrgic0mmq1r4jql1hgqc-esbuild-0.16.4/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

6 packages built:

code-server
esbuild
libsForQt5.bismuth
openvscode-server
quarto
vscode-extensions.matklad.rust-analyzer

Maintainer pings
cc @Lucus16 @marsam for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/evanw/esbuild/releases.
meta.description for esbuild is: "An extremely fast JavaScript bundler"
meta.homepage for esbuild is: "https://esbuild.github.io"
meta.changelog for esbuild is: "https://github.com/evanw/esbuild/blob/v0.16.7/CHANGELOG.md"
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.16.7 with grep in /nix/store/9m7655mpsyspyqidyq2lxbrj70582rrv-esbuild-0.16.7
found 0.16.7 in filename of file in /nix/store/9m7655mpsyspyqidyq2lxbrj70582rrv-esbuild-0.16.7

Rebuild report (if merged into master) (click to expand)

8 total rebuild path(s)

8 package rebuild(s)

First fifty rebuilds by attrpath
code-server
esbuild
libsForQt5.bismuth
openvscode-server
plasma5Packages.bismuth
quarto
vscode-extensions.matklad.rust-analyzer
vscode-extensions.rust-lang.rust-analyzer

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/9m7655mpsyspyqidyq2lxbrj70582rrv-esbuild-0.16.7 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A esbuild https://github.com/r-ryantm/nixpkgs/archive/6ae5cf854dfc6f42960e44ef367a4a2d31c8ed22.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/9m7655mpsyspyqidyq2lxbrj70582rrv-esbuild-0.16.7
ls -la /nix/store/9m7655mpsyspyqidyq2lxbrj70582rrv-esbuild-0.16.7/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

6 packages built:

code-server
esbuild
libsForQt5.bismuth
openvscode-server
quarto
vscode-extensions.matklad.rust-analyzer

Maintainer pings
cc @Lucus16 @marsam for testing.


API ImportScan Fix

This is a fix for the API ImportScan. Added True for the active and verified of the import parser factory calls. The two checks correspond to whether or not the user trusts the 'Active' and 'Verified' columns of a generic findings import file.

@devEricA I don't see any record of this bug. Would you please provide the issue number? Also won't this set it to true every time rather than taking user input?

It's supposed to be an extended fix for #1065. @ptrovatelli commented on that issue and noted that the import scan results was broken for the API. @aaronweaver requested that I investigate and check out what was going on, and I noticed that the signatures in the API were not properly updated.
Good point on the things being set to true though, I will go ahead and make the modifications to allow user input.

Thanks that fixed it in dev branch. shouldn't we port this to master and legacy-python2.7?
@devGregA


Fonts issue

Hello,
I have a pb with the icons, on my browser they're missing on the demo and local (using docker-compose)

http://localhost:7481/#/
https://mediatracker-bonukai.herokuapp.com/#/

example: 'mode_night' > icon missing

Not working on : Mozilla Firefox 91.10.0esr
Self hosted service do no need external dependencies.
Can you add icons font ?
edit: I fix my issue changing my FF settings
[X] Allow pages to choose their own fonts, instead of your selections above.
cf. https://support.mozilla.org/en-US/kb/change-fonts-and-colors-websites-use

From version mediatracker:0.1.0-beta.29 all fonts are local


Whole file buffering

The caching scheme is made for some process interacting with only some limited part os a massive file. If a huge file is opened and read beginning to end, eventually the whole thing will be cached in memory, which may not be possible. Should there be a "streaming mode" where, although we can still read ahead, when we get passes data it gets cleaned?

Clearing out extraneous parts of the buffer sounds good to me.

Drop data more than blocksize earlier in the file than the current location?

Sure?  Honestly I'm probably not as informed on current system or the best way to do this as you are.


Feat/lesq 515/specialist subject listing query

Description
Music year: 1984

adds queries for the specialist subject listing page
adds page for specialist subject listing
update types
add 404 fallback when no specialist content is published

How to test

Go to https://deploy-preview-2294--oak-web-application.netlify.thenational.academy/teachers/specialist/subjects
when there is no specialist data published there will be a 404 page (broken on preview so will internal server error)

Screenshots
How it should now look:

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


Rewrite log4j / slf4j resolution to prepare for upcoming slf4j releases

The mechanism for SLF4J resolution will be deprecated soon
As of SLF4J version 1.8.0, the static binder mechanism is deprecated.
This class exists for backward compatibility earlier versions of slf4j-api.jar, in particular in the 1.6.x and the 1.7.x series.
Note that this class is likely to be removed in future releases of SLF4J.
https://www.slf4j.org/api/org/slf4j/impl/StaticLoggerBinder.html

@smiklosovic what's the benefit of doing this? It looks like it will break backwards compatibility, so maybe something for 3.0?

Yeah whatever version works for you.
That StaticLoggerBinder class is not in 1.8.0-beta2 of org.slf4j:slf4j-api so whatever 1.8 version you put on the class path, it will still complain it is not there even there is not any need to do that because 1.8 slf4j works differently. I ve removed dependency on simple logger and I am using slf4j-log4j12 of version 1.7.25 just because of this annoying log :)

From what I understand of SLF4J 1.8/ java ServiceLoaders all you need to do is check if the resource
/META-INF/services/org.slf4j.spi.SLF4JServiceProvide is present. If not there is not Logger if so you are good!
if(Javalin.class.getResource("/META-INF/services/org.slf4j.spi.SLF4JServiceProvider")==null){ printThatWarningForMissingDepend();
}

Any progress in this issue? Not serious although annoying and misleading. Using:
<javalin.version>3.1.0</javalin.version>
<slf4j.version>1.8.0-beta4</slf4j.version>

@m-rossini Don't think anyone has worked on it. Would you like to submit a PR?

If you do not mind looking at my PR


Update db #4

Related Tickets

#Ticket_ID

WHAT this PR does?

ex: Change number items completed/total in admin page.

Notes Impacted Areas

N/A.

Attachments

N/A.

ready


Support for multi-element JSON responses from external sources of metadata

So a source of metadata that responds with a JSON such as:
{"foo":"bar"}
{"blah":"bleh"}

Results in a metadata object appended to the Authorization JSON as such:
[
  {"foo":"bar"},
  {"blah":"bleh"}
]

...instead of:
{"foo":"bar"}

Tested manually, automation pending #201

Tested manually, automation pending #201


Important note is note quite accurate or clear

The "Important" note is a little misleading. "This setting is only applicable to Active Directory domains. It does not apply to Microsoft Entra domains." As it does effectively block OneDrive on syncing Entra only joined devices when enabled.
It may also be worth mentioning the workaround for those with the restriction enabled and Entra joined devices:
https://techcommunity.microsoft.com/t5/sharepoint/onedrive-sync-for-azure-ad-joined-computers/m-p/3630765/highlight/true#M64237

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

ID: aff608fe-1f13-ad08-df3e-d2db050b87f8
Version Independent ID: 32325172-804d-fac1-5deb-9e51ccc6dd75
Content: Allow syncing only on computers joined to specific domains - SharePoint in Microsoft 365
Content Source: SharePoint/SharePointOnline/allow-syncing-only-on-specific-domains.md
Service: one-drive
GitHub Login: @JoanneHendrickson
Microsoft Alias: jhendr

Hello @CBrasga
How are you?
While I dig into this, can you please detail which version of the OneDrive client are you running? Also, please expand what you exactly did, did you used the Allow syncing only on computers joined to specific domains check box described in this article and entered a 365 Tenant Guid on the text field?

To make it easier for you to submit feedback on articles on learn.microsoft.com, we're transitioning our feedback system from GitHub Issues to a new experience.
As part of the transition, this GitHub Issue will be moved to a private repository. We're moving Issues to another repository so we can continue working on Issues that were open at the time of the transition. When this Issue is moved, you'll no longer be able to access it.
If you want to provide additional information before this Issue is moved, please update this Issue before December 15th, 2023.
With the new experience, you no longer need to sign in to GitHub to enter and submit your feedback. Instead, you can choose directly on each article's page whether the article was helpful. Then you can then choose one or more reasons for your feedback and optionally provide additional context before you select Submit.
Here's what the new experience looks like.
Note: The new experience is being rolled out across learn.microsoft.com in phases. If you don't see the new experience on an article, please check back later.
First, select whether the article was helpful:

Then, choose at least one reason for your feedback and optionally provide additional details about your feedback:

Article was helpful
Article was unhelpful

Finally, select Submit and you're done!

We appreciate any feedback that improves the content in the Microsoft docs but we haven't had any response from you so we are going to close this issue.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.


check updates

"mongo-express": "^1.0.0-alpha.1" is latest 4months now
https://www.npmjs.com/package/mongo-express

checking if there are breaking changes we should be aware of: https://github.com/mongo-express/mongo-express/blob/master/HISTORY.md#10-alpha1---mon-jun-22-2020