Torque layer dependencies not correctly registered

Context
Due to a confusion with the meaning of Layer.data_layer and Map.data_layers (they are not the same), there are a bunch of pieces of code that are incorrect. This ticket illustrates one of them.
Steps to Reproduce

Create a map
Add a torque layer on dataset P
Add a join analysis to the torque layer, with dataset Q
Try to delete dataset Q

Current Result
You are not warned of a dependency with the map .
Expected result
You should be warned.
Additional info
The problem is that Carto::Map.update_dataset_dependencies calls data_layers which does not include torque layers. This mistake is repeated throughout the code (I'm thinking that the layer node style cache might also be affected).
My suggestion here would be to bite the bullet, and instead of fixing this specific issue (it's as easy as changing data_layers to carto_and_torque_layers), changing the behaviour of data_layers so it behaves consistently with Layer.data_layer?.

This is the current status of the layer kind methods:
                  | Map models                   | Layer models
base              | all                          | tiled/bg/google/wms
data              | carto                        | carto/torque
user              | tiled/bg/google/wms          | tiled/bg/google/wms
carto_and_torque  | carto/torque                 | N/A
torque            | torque                       | torque
other             | torque                       | N/A
named_map         | carto/tiled/bg/google/wms    | carto/tiled/bg/google/wms
basemap           | N/A                          | tiled/google

My proposal is to standardize so:
base              | tiled/bg/google/wms
data              | carto
user              | *Remove*
carto_and_torque  | *Remove*
torque            | torque
other             | *Remove*
named_map         | carto/tiled/bg/google/wms
basemap           | tiled/google

Alternatively, we could just fix the bug. Looking at how costly would be to change this.

@javitonino I'm beginning now the CR of this. Did you follow strictly that table? After reading it, removing the need of data mixing carto and torque is unexpected to me.

Oh, that was a typo. I just edited the table. Indeed, data = carto + torque. I did not follow the entire table, I just removed carto_and_torque, and changed data to mean carto + torque.
I did not removed the other, nor user, and base_layers stills refers to everything.
I preferred the baby steps approach and keep myself to what fixes the current bug. We can open a refactor ticket if we want for the rest (I'm up for it!), although I'm not aware of any bug cause by that (but base_layers meaning everything lends itself to bugs).

Yep, I think that the proposal is not only great but also needed. Let's get the most out of your analysis work, open an issue with the steps (including this one).
Thanks for the explanation!

PS: visualization model is also involved here. I assume that your proposal includes changing visualization methods as well so they're the same as maps (they're mostly wrappers, now).

For sure. I forgot about visualization model until I started implementing this. I created the follow up issue here: https://github.com/CartoDB/cartodb/issues/11553 and reflected the need to update the visualization models as well.


What "Administrative Privileges" Are Required

The documentation simply says, "Note: Administrative privileges are required to use BCDEdit to modify BCD." (emphasis is mine).

To me, that statement is meaningless. Which, exactly, administrative privileges, are required to run the command? To me, when someone says "administrative privileges", they are referring to one or more of the following:
https://learn.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/user-rights-assignment
Those are granted and managed using the Group Policy Editor, as seen here:

It would be extremely helpful and meaningful to correct this documentation to state explicitly, which of the administrative privileges are required to run the command. If the documentation isn't going to be explicit and tell us what we need, then what is the point of writing the documentation at all? We need meaningful information, not just generic, broad, placeholders of words. You need to ask the developers exactly what is required/needed to execute the command. If the permissions vary depending on the options passed to the command, then that should be documented as well.

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

ID: 5cb98e1d-8a4e-b087-b9f0-3f98862f3347
Version Independent ID: 2e8ca9f3-b293-8677-b379-0d2f3b204857
Content: bcdedit
Content Source: WindowsServerDocs/administration/windows-commands/bcdedit.md
Product: windows-server
Technology: windows-commands
GitHub Login: @JasonGerend
Microsoft Alias: jgerend

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


Project Name Position Changed to Static

Fixes #807
Describe the changes you have made in this pr -
The Project Name position has been changed to static to prevent overlapping of Project name and Help on resizing.
Screenshots of the changes (If any) -

Coverage remained the same at 83.902% when pulling 52cea074fbc1073480d786409bdb4faf1b099815 on Shivansh2407:patch-13 into 8c2774b9925ec1d624fb9bb874083908749d0e52 on CircuitVerse:master.

Would like to hear your views @tachyons Sir.

Thanks


Feat(eos_cli_config_gen): add support for SSL profile cipher-list

Change Summary
Add support for cipher-list
Related Issue(s)
Fixes #1973
Component(s) name
arista.avd.eos_cli_config_gen
Proposed changes
Added cipher_list parameter for ssl_profiles
  management_security:
    entropy_source: < entropy_source >
    password:
      minimum_length: < 1-32 >
      encryption_key_common: < true | false >
      encryption_reversible: < aes-256-gcm >
    ssl_profiles:
      - name: <ssl_profile_1>
        tls_versions: < list of allowed tls versions as string >
        # cipher_list syntax follows the openssl cipher strings format
        cipher_list: < column separated list of allowed ciphers as a string >
        certificate:
          file: < certificate filename >
          key: < key filename >
      - name: <ssl_profile_2>
        tls_versions: < list of allowed tls versions as string >

How to test
molecule
Checklist
Repository Checklist

[x] My code has been rebased from devel before I start
[x] I have read the CONTRIBUTING document.
[x] My change requires a change to the documentation and documentation have been updated accordingly.
[x] I have updated molecule CI testing accordingly. (check the box if not applicable)

it is clearly stated just above the snippet:

Added cipher_list parameter for ssl_profiles


Support Async Gzip Decoding

For #161
I figured I'd open this up for visibility, and because it's easier to talk about code in PRs than issues or gitter. It's an attempt to support decoding in the async implementation, but there may be better approaches. This does introduce a bit of indirection and complexity.

The current tests picked up a nice little bug in my changes where a small chunk was being dropped rather than retained to be errored on later. I've fixed that up.
If you're happy with the general approach @seanmonstar then I'll go add a bunch of test cases. It'd be nice to make a test server that can programmatically delay chunks so we can test WouldBlock paths.

Thanks for the feedback @seanmonstar. As we discussed on gitter, libflate requires wrapping a Read, which is why I've wired this up the way that I have. I'm also not a huge fan of Read on the async response (it's needed for AsyncRead), because it'll panic if you can read() outside of an executing task, which is a shame. That's why there's that PollChunk trait, so the synchronous impl can swap the Stream out for a WaitStream and read synchronously until it gets to the end of a chunk.
So I'm not really sure how to go about refactoring the decoder to work on chunks as you described yet @seanmonstar but don't want this to stall so I'll work on the test server and get a decent suite of tests up in the meantime.

@KodrAus Could we change decoder to implement a future::Future trait instead of read, and in the synchronous implementation just call wait() on it?

@echochamber I did that initially but came to the conclusion that:

If the Future just returns the complete potentially decompressed response in some buffer then it's too limiting. What if the client wants to supply their own buffer? What if it's too small?
If the Future just performs a read then it's a lot of up-front effort allocating Arcs to handle timeouts for each call. Especially with serde_json::from_reader that'll just read 1 byte at a time.

So I ended up with this implementation that can read synchronously without blocking unless a chunk is unavailable.
Note that for the second point I didn't think about wrapping the asynchronous body in a BufRead on the synchronous side, which would probably solve that problem of allocating for each call to read. It just didn't cross my mind at the time. It's probably worth looking into and could make this a lot simpler.

I looked at all the compression libraries, and flate2 has BufRead implementation which can follow hyper's zero-copy policy. I have also opened https://github.com/tokio-rs/tokio-io/issues/61 to request adapters.
We can then wrap the Body stream to make it yield buffers. Not sure if such (Async)BufRead wrapper should implemented in hyper or reqwest.

Thanks @ishitatsuyuki :+1: I think the best way forward is to wrap the AsyncRead in a sync BufReader for the synchronous Response. That means we can do large, infrequent reads from the AsyncRead, which means setting up some shared state, and individual reads on the synchronous side will be mostly cheap because the decompressed bytes are already there.
As far as I know, we're using libflate because it has better cross-platform support than flate2.
If we really don't want the async Response to implement Read, then we might have to figure something out about tracking yet another BytesMut, reading into slices of that and emitting those slices as chunks. That seems less ideal to me than just dealing with a read-like API though.
Does anyone have any other thoughts before I go and make those changes? @seanmonstar @echochamber @ishitatsuyuki?

Nope, sounds good to me.

libflate because it has better cross-platform support than flate2

You are correct

No, BufReader is an additional layer of nonsense. As Chunk is already buffered, we should wrap it to satisfy the read_buf method.
Using flate2 definitely makes a difference because it can handle BufRead resulting in less copies. This matches hyper's aim.

I'm not sure I understand you @ishitatsuyuki. I've arrived at BufReader based on the following:

flate2 requires msvc on Windows, which makes it a non-starter for reqwest
libflate requires a Read. It doesn't have BufRead support
You can't decompress any arbitrary chunk of a gzipped response, so we can't simply decompress the chunks we receive independently and emit those in a stream
My current implementation already does minimise copies, but is complex to work around the fact that we can't poll a futures::Stream without being in the context of an executing task
Without that complexity we need to wrap all synchronous calls to read in a timeout, which makes it particularly slow for readers that only grab 1 byte at a time
We can improve that situation by wrapping the slow reader in a BufReader. Maybe it's not appropriate for reqwest to do that though and expect a caller to. Or we just do that in calls to json()
The async response doesn't introduce another buffer that data is copied into

I think maybe we should sketch out a plan of what we expect the sync and async responses to look like, so we're all on the same page.
I think (straw-man names):

async::Response provides a Decoder that is AsyncRead that is accessible by calling body() and emits decompressed bytes
async::Response provides a method like raw_chunks() that is Stream<Item = Chunk>. Those Chunks aren't decompressed
sync::Response wraps async::Decoder as AsyncRead in a synchronous reader, sync::Decoder. This means sync::Decoder needs to wrap the whole call to async::Decoder.read() in a wait::timeout so chunks can be polled as necessary, or it needs to call async::Decoder.read() synchronously and wrap the chunk polling in a wait::timeout (this is what my PR does currently)
sync::Response limits calls to sync::Decoder by wrapping it in a BufReader

Do you have other ideas of how this should work @ishitatsuyuki?

This is what I think about:

the internal Body implements Read the way it should, and BufRead by returning a slice of chunk without copy.
flate2 is definitely a win here; but well, it may be feature gated. It should be transparent as the user only see Read in the interface.
for the blocking needs, can we call Core::run with one of the tokio-io wrapper?

Ok I've made some changes:

The BufRead thing didn't quite pan out because we peek some bytes from the response to check whether it's empty or not, but that might be non-blocking. So I've wrapped that in a future. The blocking side will still only block the decoder if it needs to fetch a chunk
Removed the weird wrap_stream stuff and just don't create a Decoder unless the user asks for one
Added some quick chunking to the test server
Added a simple async gzip test

The diff on the last commit is really noisy so it's probably worth looking at it from the top again.

Travis says no. Looks like a random Travis fail?

It just seems that it's hitting the per user build limit and being queued.

If you're looking a way to provide Read's all-or-error guarantee, either:

return at chunk boundary.
check the size first and read beforehand.
fake a Ok when it blocks. Defer the error until the internal buffer is completely empty.

See also what BufReader in std do. It may greatly simplify the implementation if you implemented BufRead at first.

Additional one. As both libflate and flate2 expects read_exact() to be all-or-nothing (they don't expect retry on error), we may need to have a specialized implementation to do so.

I've pushed a few changes but this isn't ready for another review yet. I'll send a ping when I think it is.

Any reason to do so? I think this is completely nonsense.

What in particular are you referring to? Also, calling people's work "complete nonsense" is kind of hostile, could you dial it back? Pointing out specific flaws will be much more useful for everyone.

I think the 'complete nonsense' @ishitatsuyuki is referring to is the fact that we're decompressing into an intermediate buffer, not the fact that I haven't implemented it properly yet.
To be honest, I'm also not 100% sure why we don't want the response body to be AsyncRead, but I figure if it becomes something we do want in the future it's not too difficult to add it. I think there are also a bunch of strategies for minimising the cost of that buffer but I haven't done any benchmarking so don't know what the impact is.

I intended to comment on the latest commit, but for some reason the mobile UI turned it into a review.
I don't think using a stream fits here. HTTP response is just a stream of bytes, and I think there's no better solution than Read/AsyncRead.
Anyway, do you have a particular reason to make it a Stream? There's more overhead, it is less intuitive, and API compatibility is not a problem.

@ishitatsuyuki I basically agree with you. Maybe @seanmonstar can shed some more light on why this needs to be Stream and not AsyncRead.
But I think it's also worth considering that this is an unstable API. I don't think we need to get it perfect right away. For the stable API there'll be an impact on memory usage for compressed responses but that could be improved through major changes to this async API in non-breaking version bumps (I'm assuming the unstable module isn't semver'd).
So personally I'm happy for this to move forward in any shape that @seanmonstar is happy with.

I cannot understand why you're moving to use Stream where AsyncRead would be definitely be better. I saw too much changes that it would require substantial amount of work to revert to AsyncRead.
Can you elaborate on why you're switching to Chunks?

Yeh I get that it doesn't seem ideal, but I don't really want to push back on the design right now. I'd rather focus on having a robust implementation that isn't going to cause regressions for all the current synchronous reqwest users.
@ishitatsuyuki Your reviews have been great, you've caught a lot of errors in this PR. So I think any more bug-related feedback you have would help drive this forward more than the merits of AsyncRead vs Stream right now because I already agree with your points there.

There's a debug_assert failing in libflate that I haven't quite figured out yet. Swapping to flate2 works fine.

@seanmonstar other than the debug_assert failure this should be ready for another look.

Looks like the libflate bug is all fixed now :tada:

Thanks for this spectacular work!


typescript definitions

Hi, cool library.
Are there any plans to add typescript definitions?
Thanks.

Someone, please provide typescript definitions for this package, in my opinion, this would be a very useful plugin for some startups who want their system be extensible.

I would appreciate some help in this matter. I am not a TypeScript user nor an expert.

Hi,
I can help with writing the types. Would you rather have the library rewritten in typescript, or only added types declarations ?

I have been hesitating, as a matter of fact. If you wish to go full TS, why not.

I'm working on the TS rewrite and this line bugs me.
https://github.com/adaltas/node-plug-and-play/blob/89a80c6e8ebcf082769ec8844f6bb388d1405794/lib/index.js#L122
Could you please explain ?
Isn't plugin.hooks[name] supposed to refer to a single hook ? How come we could map this ?

Not so sure about this[key] in this line :
https://github.com/adaltas/node-plug-and-play/blob/89a80c6e8ebcf082769ec8844f6bb388d1405794/lib/error.js#L25
Is there any reason for not simply doing key = ... ?
I'd need some help to make the tests work as I'm not familiar at all with mocha and currently it won't run:
Error: Use CoffeeScript.register() or require the coffeescript/register module to require .coffee files.

return plugin.hooks[name].map(function(hook){

It is always an array. the property plugin.hooks[name] is normalized at line 81 with the normalize_hook function.

Not so sure about this[key] in this line :

This refers to the error object instance. In here, we add any property of the contexts arguments to the error instance. For example, const err = new Error('CODE', 'some message', { prop: 'value' }) leads to err.prop === 'value'. Note, a commited a change to the error JS file to clean up the variable (a leftover from the coffee to js migration).

I'd need some help to make the tests work as I'm not familiar at all with mocha

The error is related to mocha not calling the Node.js --loader argument to load .coffee file, i'll have a look, I have done it in the past with the csv parser.

Error: Use CoffeeScript.register() or require the coffeescript/register module to require .coffee files.

Replace all occurrences of ../lib/index.js with ../dist/esm/index.js in the tests and they will run. I just tested after a rebase on master. However, I am not agains rewriting the test in TS but I can do this, it will train me with TS, I have too little experience with it.

Thank you, I'll have a look at all this, this afternoon.

Do you mind if we replace the array_flatten method with lodash.flatten, as it is already typed ?

I am reluctant to introduce dependencies, but there is arr.flat(Infinity) now which shall do the job.

Didn't know this one, thanks

One these lines https://github.com/adaltas/node-plug-and-play/blob/1f4b16b308a5e9e0706ce55fd4939d55dfc082f8/lib/index.js#L141-L143
We use the plugin property that is added to hooks a few lines before.
2 questions:

This property isn't available on all hooks. Hooks coming from L107 don't have this property, can you confirm ?
Should we add the  require and plugin properties to the Hook interface, or just leave it as a transitional property used only for sorting ?

The Hook interface looks like this atm:
export interface Hook {
  /**
   * List of plugin names with hooks of the same name are to be executed after, a string is coerced to an array.
   */
  after?: string[];
  /**
   * List of plugin names with hooks of the same name are to be executed before, a string is coerced to an array.
   */
  before?: string[];
  /**
   * Name to indentify the hook.
   */
  name: string;
  /**
   * The hook handler to be executed
   */
  handler: HookHandler;

  // require?: string[];
  // plugin?: string;
}

I am trying to refresh my mind but I am pretty sure you are right, require and plugin look like transitional properties.
hook.plugin is the associated plugin name, and hook.require is used to get the list of required plugins defined in its associated plugin
I just push a commit on master to correct line 142.

Thanks.
This part is a pain to adapt to typescript, as it goes against TS strong typing practice. In the TS paradigm, we should not dynamically add properties to the Hook interface. I found a workaround, but it's not the cleanest way. This will be a point of improvement in the future

Is the call_sync function still in use ? You don't speak about it in the docs nor in your blog post.

we should not dynamically add properties to the Hook interface
Then you can always declare those properties. If I remember correctly, the idea is that user-provided hooks don't need a name and required plugins but I am not even sure anymore.

Is the call_sync function still in use

Yes, I use it in some libraries


Improve bevy_ecs query docs

Mainly documents Query, WorldQuery and the various Query Filter types as well as some smaller doc changes.

Wonderful doc work as always. Looks good to me!

bors r+


Error MSB3721. Please HELP

1>------ Build started: Project: mapDriver, Configuration: Release x64 ------
1>  Building 'mapDriver' with toolset 'WindowsKernelModeDriver10.0' and the 'Universal' target platform.
1>  Stamping x64\Release\mapDriver.inf [Version] section with DriverVer=02/06/2018,<IP_ADDRESS>7
1>ApiValidation : error : ApiComparer had an XmlException. Make sure XML file has correct format.
1>ApiValidation : error : Check that XML files are formatted correctly.
1>ApiValidation : error : Test failed with error message: Analysis run on incorrect file types or the folder is empty.
1>C:\Program Files (x86)\Windows Kits\10\build\WindowsDriver.common.targets(1746,5): error MSB3721: The command ""C:\Program Files (x86)\Windows Kits\10\bin\x64\ApiValidator.exe" -DriverPackagePath:"C:\Users\14471\Desktop\123\PUBG-map-hack-master\kernel driver\x64\Release\" -SupportedApiXmlFiles:"C:\Program Files (x86)\Windows Kits\10\build\universalDDIs\x64\UniversalDDIs.xml" -ModuleWhiteListXmlFiles:"C:\Program Files (x86)\Windows Kits\10\build\universalDDIs\x64\ModuleWhiteList.xml" -ApiExtractorExePath:"C:\Program Files (x86)\Windows Kits\10\bin\x64"" exited with code -3.
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
========== Deploy: 0 succeeded, 0 failed, 0 skipped ==========
I noticed that #148 has mentioned this situation, but I don't see the solution there.

Try to make a new driver project and copy and paste the needed .c and .h files there.


Review spacing across the landing

Everything feels a bit too tight, we could add a bit more spacing between different sections and between the different parts of each section.

I agree, think almost everything could use a bit more spacing. Sharing some other examples that I've seen here: basically around the titles of sections & the margin of the cards.

Also, not sure this is the best Issue to mention this or it should be in #28 , but I would also reduce the font sizes on:

card titles
card paragraph
community grants cta section paragraph (& make it equal to the hero paragraph)
all section titles (maybe except the hero) and make it equal to CTA section (that one looks okay to me)
'see completed grants' button

I can provide more specific details about this if needed, thanks so much guys!! :)


Metadata column tests: issues #24 and #25

Added python script to test the columns of the metadata file, and the logic of the warning-type columns

Thanks @thartshorne.  I believe that @vineetbansal would like to talk to you about these before we merge them.  Can you set up a time to meet with him?


Dash asset page

A simple-as-possible page that allows the user to view everything the DLCS knows about an asset. In old DDS there was a link to the asset page in the DLCS Portal.
We need this page in the DDS because we don't have a replacement portal just yet.
If it's an image, the page shows the thumbnails and an OpenSeadragon instance for testing tile requests.
You can reingest the image (a call to [image-uri]/reingest)
Not implemented yet:

Delete
Edit fields

Made it a draft as we will rename deliveryChannel to deliveryChannels


how to cache pages error on client side?

I can cache component error from page's from "componentDidCatch"

but if I put some error on pages, I don't know where I can catch errors...
Does anyone has a good idea? thx!

componentDidCatch doesn't work server side. Either way there's not really anything we can do on the Next side, since it's not clear what you are trying to do exactly.
In the future please follow the issue template (that big chunk of text you removed before writing the issue). Otherwise it's really hard to help you.


Attempt to open an admin tab fails.

Every attempt to open a profile with administrator rights fails on Windows 10. It opens and immediately closes.
Terminus Version: 114
OS: Windows 10 Pro
Version: 2004
OS Build: 19041.388
Window Feature Pack: 120.2202.130.0

Duplicate of #2800


css3 ::marker psuedo-element support

css3 ::marker psuedo-element support

This issue was imported from Google Moderator
Moderator votes: +13
Issue added by skeg64 on 2012-08-17
To vote this issue up or down, simply include +1 or -1 in your comment.

This is part of CSS Lists and Counters Module Level 3.

+1

+1

oui oui oui

+1

+1

+1

+1

Now available at http://caniuse.com/#feat=css-marker-pseudo
(sorry folks, no support anywhere yet)


Make suffix of generated React Apollo components customizable

This PR addresses the following issue: #1834
The default suffix is Component. It should be possible to specify the desired suffix (string) via customSuffix property in plugin config in codegen.yml.
I only made changes to the typescript-react-apollo plugin.

Hi @jlkiri ! Thank you for your contribution!
I think componentSuffix could be a better name for this, what do you think?

@dotansimha This indeed sounds like a better name. I'll change it.

Thanks @jlkiri !


Rollup fires on new record even though criteria excludes the current record for count rollup.

When we are using boolean values in the relationship criteria it still fires if that value is false or doesn't match the criteria.
To stop this from happening on new records check that the relationship criteria matches the current record.
I believe it would be the same for deletes as well.
Not sure if this should be the case for other rollups?
This would be good to avoid unnecessary updates although parsing of the relationship query would be required (if not already done).

Yeah the tool does not evalatue the criteria only that the field to aggregate field and any of the relationship criteria field fields have changed. Having it not run the rollup if the criteria is not met does involve parsing the criteria as you say, currently though this can be quite rich, basically the SOQL WHERE syntax. I am sure there is another GitHub issue discussing this and is still open to continue to try to figure this one out. I'll leave this one open until i find it! 👍

Thanks Andy.
I don't know if this would help but if you ran a soql query with the where clause returning the id of the sobject would it not satisfy this requirement as we are in the after (in trigger terms) the Id should be populated and and soql queries that run should return the current object?
Something like:
'SELECT Id From OBJECT WHERE Id = '' + oldRecord.Id + '' AND ' + relationshipCriteria
It would require an extra soql query but you could add this as an option in the config?
The alternative is like I suggested earlier to parse the where clause.

Yes that would work, at the expense of performance and SOQL governor usage. As you say though an option to let the user choose what they want would be the way to go, put the decision in the users hands. Thanks for the thought. 👍

This should be handled by the new logic provided by #1289 that will validate that the DML will modify the target record.
If this is the first child and the parent record doesn't already have a correct default value the first update will populate the value according to having zero matching child records. But if the parent already has the expected value then the DML against the parent will be skipped.


Add Sphinx documentation

Initialize sphinx documentation using MyST parser and publish to readthedocs

This was completed in #23


[DNM] Bugfix: trying to set annotation instead of label

Signed-off-by: Shivam Mukhade<EMAIL_ADDRESS>
Changes

Submitter Checklist

[ ] ♽  Run make test lint before submitting a PR (ie: with pre-commit, no need to waste CPU cycle on CI
[ ] 📖 If you are adding a user facing feature or make a change of the behavior, please verify that you have documented it
[ ] 🧪 100% coverage is not a target but most of the time we would rather have a unit test if you make a code change.
[ ] 🎁 If that's something that is possible to do please ensure to check if we can add a e2e test.
[ ] 🔎 If there is a flakiness in the CI tests then don't necessary ignore it, better get the flakyness fixed before merging or if that's not possible there is a good reason to bypass it. (token rate limitation may be a good reason to skip).

the bug is fixed on tektond/pipelines so we might not this now.
o/


Document InfluxDB I/O procedures

Summary of the changes / Why this is an improvement
Checklist

[x] Link to issue this PR refers to (if applicable): https://github.com/crate/tech-content/issues/99
[x] CLA is signed

CI fails like:
(integrate/etl/influxdb: line   17) broken    https://github.com/crate-workbench/cratedb-toolkit/tree/main/cratedb_toolkit/io#installation - Anchor 'installation' not found

-- https://github.com/crate/cratedb-guide/actions/runs/8989923871/job/24694060679?pr=75#step:4:1063
This is certainly not your fault.

https://github.com/sphinx-doc/sphinx/issues/9016

Thanks! Removed the anchor already, just didn't push. Addressing other suggestions.

It may be sensible to add a "start services" section here, which conveys how to run both services using Docker. We can't present it for each and every platform, so Docker just yields the best platform coverage.

Can you check now? Added, but this is only influxio right? That doesn't come with ctk or crash. Which are needed here:
export CRATEDB_SQLALCHEMY_URL=crate://crate@localhost:4200/testdrive/demo
ctk load table influxdb2://example:token123@localhost:8086/testdrive/demo

crash --command "SELECT * FROM testdrive.demo;"

influxio does not come with ctk or crash?

It should be installed when installing CrateDB Toolkit appropriately.
pip install 'cratedb-toolkit[influxdb]'`

Please also use such aliases to provide optimal UX to readers of the documentation when it comes to invoking tools, and why not just everything. ;]
All aliases at once, also alphanumerically sorted:
alias crash="docker run --rm -it ghcr.io/crate-workbench/cratedb-toolkit:latest crash"
alias ctk="docker run --rm -it ghcr.io/crate-workbench/cratedb-toolkit:latest ctk"
alias influx="docker run --rm -it --network=host influxdb:2 influx"
alias influxio="docker run --rm -it ghcr.io/crate-workbench/cratedb-toolkit:latest influxio"

Feel free to do anything of that on a later iteration, based on your energy and spirits. The current version is more than good enough to have it, and can also improved later. Don't forget to squash your commits, into a single one with a meaningful message. Thanks!

That's good, thank you very much. Running it all on docker would be ideal for sure.
Will continue on this tomorrow and try to wrap it up.

Hi again. I think it should be good now. I did it a bit differently than in the docs, looked easier to me this way. What do you think?

One thing to mention. On macOS (Apple Sillicon) I got docker: no matching manifest for linux/arm64/v8 in the manifest list entries. for both of these:

https://github.com/crate/cratedb-guide/pull/75/files#diff-a9fd0140e16a6e1b64b4fa6e2ed9c2be66e12e55201944581fd72c30be4e5c29R69
https://github.com/crate/cratedb-guide/pull/75/files#diff-a9fd0140e16a6e1b64b4fa6e2ed9c2be66e12e55201944581fd72c30be4e5c29R75

Hi. I did not review the HTML preview, apologies. Apparently, there is something wrong on the folding/nesting of elements, see https://cratedb.com/docs/guide/integrate/etl/influxdb.html. Can you fix it?

I missed that too, thanks for checking. https://github.com/crate/cratedb-guide/pull/78 will help

Sorry for eventually merging this too early. It looks like the commits have not been squashed.


Rename apigee2openapi?

Would be great to have this using the latest incarnation of OpenAPI rather than Swagger

Thank you @earth2marsh for the feedback. Renamed project & npm module. Thank you for the PR.


Camera plugin outer zoom limit not functioning

Describe the bug
The camera plugin for expanding the outer zoom limit no longer works as of the RS update for League II - Trailblazer (Rev 192)
To Reproduce
Steps to reproduce the behavior:

Enable Camera plugin
Set 'Expand outer zoom limit' to 400 and attempt to zoom out in game, it does not allow the same maximum zoom level as pre-update

Expected behavior
Allows zoom out to an extreme distance
Environment (please complete the following information):

Windows 10 Home 10.0.19041 B19041
RuneLite version: 1.6.29
Launcher version: 1.6.0

fixed by 8a5825fbde105f71099bd9e03beb8a7b65cad7ca


small bug: tilde expansion with -L

When using the -L option, single-quotes placed around a tilde directory ("~/") on the command line
are improperly preventing tilde-expansion:
$ jq -L ~/github/jqMaster/tests/modules -cMn  'include "c"; [a, c]'
[0,"acmehbah"]

$ jq -L '~/github/jqMaster/tests/modules' -cMn  'include "c"; [a, c]'
[0,"acmehbah"]

$ gojq -L ~/github/jqMaster/tests/modules -cMn  'include "c"; [a, c]'
[0,"acmehbah"]

$ gojq -L '~/github/jqMaster/tests/modules' -cMn  'include "c"; [a, c]'
gojq: compile error: module not found: "c"

Command expanding ~ in program path arguments is not a good command behavior in general. It is a task handled by shell, and none of any basic linux commands supports this as far as I know.

Yes, but -L is indeed special.  From the jq manual:

Paths in the a search path are subject to various substitutions.

For paths starting with "~/", the user's home directory is substituted for "~".

Okay, I'll implement it.

Small thorns are often the most irritating.
Thanks.


Suggestion: Use a backchannel in future tutorials

Excellent tutorial today! Thank you for putting all of this together. I have one small suggestion.
I think it would've been helpful to have a backchannel to share code snippets, ask questions, etc. without disrupting the tutorial. I've seen the Mozilla Etherpad used quite successfully in tutorials like this before.

Thanks, we might do that in the future. You can also just flag me down.


Include new tab 'CAE insights by SignIn' to CAE Workbook

Description
Updated existing CAE Workbook and moved existing content under "IP Address Mismatch" tab and included new tab "CAE per SignIn" insights.
Validation
Here is the link for draft workbook in Woodgrove Tenant.
Screenshots
Existing content moved under tab:

New tab:

PR Checklist

[x] Explain your changes, so people looking at the PR know what and why, the code changes are the how.

If adding or updating templates:

[x] post a screenshot of templates and/or gallery changes
[x] ensure your template has a corresponding gallery entry in the gallery folder
[ ] If you are adding a new template, add your team and template/gallery file(s) to the CODEOWNERS file. CODEOWNERS entries should be teams, not individuals
[x] ensure all steps have meaningful names
[x] ensure all parameters and grid columns have display names set so they can be localized
[x] ensure that parameters id values are unique or they will fail PR validation (parameter ids are used for localization)
[x] ensure that steps names are unique or they will fail PR validation (step names are used for localization)
[x] grep /subscription/ and ensure that your parameters don't have any hardcoded resourceIds or they will fail PR validation
[x] remove fallbackResourceIds and fromTemplateId fields from your template workbook or they will fail PR validation

Yes, will be adding 'learn more' link once the documentation is ready.


CLOUD-52267 Typo problem around cb.template.defaults variable

@keyki plz review

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/2047/

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/2048/


Bug-Fix-3.11/FE-256-minor-UI-fixes-for-the-graph-viewer backport

Scope & Purpose
Backport for #18890

[x] :hankey: Bugfix

Checklist

[x] :book: CHANGELOG entry made

Related Information

[x] GitHub issue / Jira ticket: https://arangodb.atlassian.net/browse/FE-256

[ ] https://jenkins01.arangodb.biz/job/arangodb-ANY-jslint/29038/


Update aks-arm-deploy.json

Purpose
The current provider version "preview" seems not be supported. The new version of provider is set to 2024-01-01.
Does this introduce a breaking change?

[ ] Yes
[x] No

Pull Request Type
Update of Deployment Template JSON file.

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test
Click on Deploy button
git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

Test the code

Thanks @ddobric


Plugin Support

Add support for plugins. Plugins should be able to eventually allow you to modify the public and admin site (of their own pages) and the pubic facing pages. They should be able to store data (run migrations) from settings pages. They should be able to enabled / disabled via the admin pages.
In order to achieve this, Tanzawa should autodiscover plugins.py modules using from django.utils.module_loading import autodiscover_modules
The autodisocvered modules can then be listed in a page in the admin with a button to activate / deactivate.
Activation should add the application to installed apps and run migrations like below.
from collections import OrderedDict
from django.apps import apps
from django.conf import settings
from django.core import management

new_app_name = "my_new_app"

settings.INSTALLED_APPS += (new_app_name, )
apps.app_configs = OrderedDict()
apps.apps_ready = apps.models_ready = apps.loading = apps.ready = False
apps.clear_cache()
apps.populate(settings.INSTALLED_APPS)

management.call_command('makemigrations', new_app_name, interactive=False)

management.call_command('migrate', new_app_name, interactive=False)

source
The general flow should be:

django starts up
plugins app autodiscovers plugins and compares them against activated plugins
activated plugins will be added to installed apps / urls.py
migrations should only be run on activation or when activated and the system as a whole is running migrations

Is there any core features that should instead be a plugin and activated on case by case basis ?
what would be an example of a tanzawa plugin ?
Syndication to Twitter/mastodon comes to mind

Syndication via Twitter/mastodon would be a great example of something that might work better as a plugin and is kind of a core feature.
Example plugins I'm thinking about are: A "now" page or a blogroll, or custom views for bookmarks?. More niche, something that could maybe import my activity from Strava, a plugin to provide a custom endpoint for me to post my electric usage to.

Would be indeed great to be able to plug-in different data sources (Strava or even more self-hosted approach using open source tracking apps)
Custom endpoint for different usage is also neat!
Custom views : I'm thinking more for Photos, What if we could have a All Photo's views, aggregating all the content type photos ? That would be really neat!

Yes - I think custom photo views could be handled by a plugin. You could also group by exif data and such as well (as we do store it in the db as a python blob).

With the merge of #119, I've added support for plugins. Closing this issue.


endless loop while updating extension

VSCode Version: 1.46.0-insider
OS Version: Ubuntu 20.04

Steps to Reproduce:

Install Version Lens
Version Lens tries to update 1.0.1 (even though latest version seems to be 1.0.0)
Endless loop

Does this issue occur when all extensions are disabled? No

On our extension, our users are seeing this problem as well - https://github.com/IBM-Blockchain/blockchain-vscode-extension/issues/2349
We published a VSIX yesterday, so I'm guessing something is wrong with the marketplace. I'm hoping publishing a new version of our VSIX sorts the problem 🤞

Publishing<EMAIL_ADDRESS> ERROR  TF10216: Azure DevOps services are currently unavailable. Try again later. Activity Id: 27ab2aeb-cf42-430c-bae4-867cf103ce27

Looks like the marketplace is having issues.

This issue is causing fan in MacPro spin at highest rate

For Ubuntu 18.04 as well.

I have a temporary.
The attempt to install 1.0.30 left this in ~/.vscode/extensions
.ibmblockchain.ibm-blockchain-platform-1.0.28
So
$ cd .vscode/extensions/
Copy it out
$cp -r .ibmblockchain.ibm-blockchain-platform-1.0.28/ ibmblockchain.ibm-blockchain-platform-1.0.28
$ cd ibmblockchain.ibm-blockchain-platform-1.0.28/
$npm install
After that completes, start up VS Code.  It will take a while rebuild environments, etc., but everything seemed come back.  Also, you might think about stopping automatic upgrades/updates/whatever in preferences.

Also, you might think about stopping automatic upgrades/updates/whatever in preferences.

+1 to this!

@joaomoreno
The problem seems to be how vscode is handling the api results from the marketplace
When version lens is not installed the json results from https://marketplace.visualstudio.com/_apis/public/gallery/extensionquery shows
v1.0.0 and flags=verified (screenshots from fiddler)

Once version lens is installed then the json shows v1.0.4 with flags=none
This is when I see

In the marketplace
After publishing the extension since v1.0.0 I see this error:

The error popup says this:

The extension 'vscode-versionlens' from 'pflannery' contains an entry which is unsafe for extraction.

I get a log file emailed to me and that shows the same high level message.
To add I have'nt actually included anything unsafe, in fact since v1.0.0 I've reduced the amount of production node_modules to less than half the file size.
There are 0 security issues reported by npm audit and github, so god knows what marketplace is falling over on.
When running vscode/vsce it packages and publishes to marketplace with no errors.
I emailed marketplace support  2 days ago and I'm just waiting to get more information about what  the problem is.
The short term workaround is to install manually from the generated releases -> https://github.com/vscode-contrib/vscode-versionlens/releases
The issue is also being tracked at https://github.com/vscode-contrib/vscode-versionlens/issues/211

Analysis
The valid version available for installing this extension is 1.0.0 and it seems Marketplace also has a non validated version 1.0.4 of this extension.
VS Code is not excluding non validated extensions while querying market place for latest versions but excluding while installing. Hence an update to 1.0.4 is seen always but while trying to install, it installs 1.0.0 version and this is going in auto update loop.

@sandy081 Do u have any idea why versionlens is failing validation ?
Seeing as microsoft/vscode-vsce is happy to publish to the marketplace I have no clue what is wrong.
Im guessing the validation logic on marketplace has been updated recently which hasn't been applied to microsoft/vscode-vsce yet.

I am sorry that I do not know about how validation is being done.
CCing @fiveisprime @joaomoreno

Over at https://github.com/IBM-Blockchain/blockchain-vscode-extension, we published a new version of our extension earlier and all seems to be working now. @pflannery

Over at https://github.com/IBM-Blockchain/blockchain-vscode-extension, we published a new version of our extension earlier and all seems to be working now. @pflannery

@Jakeeyturner sounds good.
I see there have been changes since your first failure which makes me wonder if any of those changes got around the validation issue on marketplace or its actually fixed on their side.
I want to push another update but I've already accumulated over 18+ million installs thanks to this bug so I really dont want to push until I know:

it's fixed or why its failing; and
vscode has released a loop fix

@pflannery I would recommend to publish a new version so that users will not see this endless loop.
TBH we count installs than downloads.

Over at https://github.com/IBM-Blockchain/blockchain-vscode-extension, we published a new version of our extension earlier and all seems to be working now. @pflannery

@Jakeeyturner sounds good.
I see there have been changes since your first failure which makes me wonder if any of those changes got around the validation issue on marketplace or its actually fixed on their side.
I want to push another update but I've already accumulated over 18+ million installs thanks to this bug so I really dont want to push until I know:

it's fixed or why its failing; and
vscode has released a loop fix

We initially released v1.0.29 on Thursday which was when we first saw the update loop problem.
Tried again with v1.0.30, which had a small change, on Friday quite quickly after everything was reported to be working fine here - https://status.dev.azure.com/_event/189079011
I suspect we did it too soon and that there was a backlog or something.
Then tried v1.0.31 (same as v1.0.30, minus a change to our changelog) which worked earlier.

I'm thinking this has something to do with #98375, which was mitigated last night. I'll reach out to the marketplace team.

Removing the candidate tag as there is a new valid version of Version Lens extension is published and available in Marketplace which fixes existing clients.

I got a response from the marketplace today

I don't know what the new check was but sounds like it's been disabled.
Would love to get a heads up in future if new validation checks are going to be added.

Removing the candidate tag as there is a new valid version of Version Lens extension is published and available in Marketplace which fixes existing clients.

I published1.0.6 with no issues from marketplace.

Based on users comments and that I can no repro with latest insiders adding verified label.

@isidorn , I see the fix in 667142d is to filter the extensions provided by the Marketplace to prevent getting unvalidated extensions. It's a great mitigation, but consider this: servers have bugs, so can you really trust them? If the Marketplace starts sending unvalidated extension versions again we will be in the same situation. I recommend an additional fix, that will make the client resilient to server bugs. For example, if an auto-update fails, don't try again for X minutes.
//cc @fiveisprime , @xavierdecoster

@skofman1 Valid argument. Since we cannot implement fall backs for all server errors which can be any we might add some general protective measures which can also benefit VS Code. For eg: we are planning to enable VSIX caching on VS Code (which we already support for VS Code Dev Containers) - https://github.com/microsoft/vscode/issues/99674. This is a first good step to not to reach Marketplace continuously.

@sandy081, can you please explain how VSIX caching will prevent and endless loop in the auto-update scenario? If I understand correctly, the root cause was that the server responded to a query with a latest version of an extension that wasn't actually available for download. This caused an endless loop of retires. How can we prevent this next time the server returns a latest version that's not available for download?

If I understand correctly, the root cause was that the server responded to a query with a latest version of an extension that wasn't actually available for download.

@skofman1 I think root cause is because VS Code is using different queries to check for updates and to install an extension. See below:

VS Code has an extension with version (say 1.0) is installed
VS Code (Version check logic) asks Marketplace to get the latest version (missing a filter to skip invalid extensions)
Marketplace returned a version (say 2.0) that is invalid
Since there is a newer version, VS Code triggers auto update
VS Code (Install logic) asks Marketplace to get the latest version with proper filters
Marketplace returns valid version (1.0)
VS Code (Install logic) asks Marketplace to download this version
And this loops.

But I see your point that VS Code might loop if the auto update failed for any reason - https://github.com/microsoft/vscode/issues/99734


IGNITE-12364 Migrate JMS module to ignite-extensions

Thank you for submitting the pull request to the Apache Ignite.
In order to streamline the review of the contribution
we ask you to ensure the following steps have been taken:
The Contribution Checklist

[x] There is a single JIRA ticket related to the pull request.
[x] The web-link to the pull request is attached to the JIRA ticket.
[x] The JIRA ticket has the Patch Available state.
[ ] The pull request body describes changes that have been made.
The description explains WHAT and WHY was made instead of HOW.
[ ] The pull request title is treated as the final commit message.
The following pattern must be used: IGNITE-XXXX Change summary where XXXX - number of JIRA issue.
[ ] A reviewer has been mentioned through the JIRA comments
(see the Maintainers list)
[ ] The pull request has been checked by the Teamcity Bot and
the green visa attached to the JIRA ticket (see TC.Bot: Check PR)

Notes

How to Contribute
Coding abbreviation rules
Coding Guidelines
Apache Ignite Teamcity Bot

If you need any help, please email<EMAIL_ADDRESS>or ask anу advice on http://asf.slack.com #ignite channel.

@samaitra, looks good to me, please go ahead and merge the changes.

@dmagda thank you, I have merged the changes.


Can't import flux_bootstrap_git in new provider

I'm trying to re-write our terraform to use the new flux provider, but when I try to import the flux_bootstrap_git resource I get
terraform import flux_bootstrap_git.this flux-system
Error: Could not get GitRepository flux-system/flux-system

If I change this to be the name of the git repo I get
terraform import flux_bootstrap_git.this my-repo
Error: Could not get Deployment my-repo/kustomize-controller

I assume I've done something wrong with the providers/config, but I can't work out what.
provider "flux" {
  kubernetes = {
    host                   = "https://api.my-cluster.com"
    client_certificate     = XXX
    client_key             = XXX
    cluster_ca_certificate = XXX
  }
  git = {
    url =<EMAIL_ADDRESS>    ssh = {
      username    = "git"
      private_key = tls_private_key.this.private_key_pem
    }
  }
}
provider "github" {
  owner = "my-owner-name"
}

and
resource "flux_bootstrap_git" "this" {
  cluster_domain   = "my-cluster"
  components_extra = ["image-reflector-controller", "image-automation-controller"]
  depends_on       = [github_repository_deploy_key.this]
  path             = "cluster/flux"
}

The value that you pass at the end of the import command is the namespace that Flux is installed in, as stated in the documentation. I am trying to figure out where `kubeconf`` is coming from.

Ah right so kubeconf is the name of the repo. Let me update the original post for clarity.

What version of Flux is installed compared to the version of the provider that you are using?

I upgraded this cluster first before I tried to move over to the new provider layout.
Flux version is 2.0.0-rc2, and provider version is 1.0.0-rc.2


Cannot connect erwin DM 2021 R1 to Docker container on SQL server 2019:latest

I have an issue opened with Quest Erwin Data Modeling group (SR Number:4945004).  They suggested "Please reach out to Microsoft Docker support.  I reviewed this ticket with Bob and you will need to involve their support also." or is it a configuration issue (attached is the powershell script used in my class)?
I have everything working in docker accept Erwin (https://www.screencast.com/t/pMkNxaU8ySA) is a video of all steps using volumes that persist data locally bidirectional mapping of windows to the Ubuntu file system.
SSMS connects effortlessly and Azure Data Studio is not as forgiving as SSMS and the advanced properties allows the connection?   Therefore, it may be the connection string used in Erwin that is in conflict with docker in the same manner as Azure Data Studio?

`## Pull the latest SQL Server 2019 Ubuntu image
docker pull mcr.microsoft.com/mssql/server:2019-latest
Verify that the docker image is on your system
docker image ls -a
You can customise the container by modifying any of the parameters or not
docker container run
--name unixSql2k19   								You can change unixSql2k19
-p 12001:1433 										You can change 12001
-e "ACCEPT_EULA=Y" -e "SA_PASSWORD=PH@123456789" 	You can change PH@123456789
-e  "MSSQL_AGENT_ENABLED=true"
-e  "MSSQL_DATA_DIR=/var/opt/mssql/data/"
-e  "MSSQL_LOG_DIR=/var/opt/mssql/log/"
-e  "MSSQL_BACKUP_DIR=/var/opt/mssql/backup/"
-v //w/csci331-backup:/var/opt/mssql/backup          		 You can change //w/csci331-backup (w:\csci-backup) to whatever UNC
-v //w/csci331-backup/data:/var/opt/mssql/backup/data        You can change //w/csci331-backup (w:\csci-backup\data) to whatever UNC
-v //w/csci331-backup/log:/var/opt/mssql/backup/log          You can change //w/csci331-backup (w:\csci-backup\log) to whatever UNC
-h csci331-server 									You can change csci331-server to any hostname
-d mcr.microsoft.com/mssql/server:2019-latest
Run the command below to start the container as is with no changes if you would like.## Run the command below to start the container as is with no changes if you would like.
docker container run --name unixSql2k19 -p 12001:1433 -e "ACCEPT_EULA=Y" -e  "MSSQL_AGENT_ENABLED=true" -e "SA_PASSWORD=PH@123456789" -e  "MSSQL_DATA_DIR=/var/opt/mssql/data/" -e  "MSSQL_LOG_DIR=/var/opt/mssql/log/" -e  "MSSQL_BACKUP_DIR=/var/opt/mssql/backup/" -v //w/csci331-backup:/var/opt/mssql/backup -v //w/csci331-data:/var/opt/mssql/data -v //w/csci331-log:/var/opt/mssql/log -h csci331-server -d mcr.microsoft.com/mssql/server:2019-latest

docker container ls -a

Now connect to the docker container using the bash shell use ls -ls
docker exec -u 0 unixSql2k19 whoami  # Show that you are logging in as the root

docker exec -u 0 -it unixSql2k19 bash
cd /var/opt/mssql/backup/

cd /var/opt/mssql
chmod -R 777 /var/opt/mssql
`

One last note, the image that I had previously used was at least 7 months old since it was used in a college class at the begginning of the semester.

By not mapping the data and log directories.  Erwin connects but persistence is lost.
##  -v //w/csci331-backup:/var/opt/mssql/backup         Use only the one volume You can change //w/csci331-backup (w:\csci-backup) to whatever UNC
docker container run --name bckvolSql2k19 -p 13001:1433 -e "ACCEPT_EULA=Y" -e  "MSSQL_AGENT_ENABLED=true" -e "SA_PASSWORD=PH@123456789" -e  "MSSQL_DATA_DIR=/var/opt/mssql/data/" -e  "MSSQL_LOG_DIR=/var/opt/mssql/log/" -e  "MSSQL_BACKUP_DIR=/var/opt/mssql/backup/" -v //w/csci331-backup:/var/opt/mssql/backup -h csci331-server -d mcr.microsoft.com/mssql/server:2019-latest


Installation / enable plugin error: Unable to load addon script from path: 'res://addons/haxe/editor-plugin-main/scripts/haxe.gd' There seems to be an error in the code, please check the syntax.

Following the installation instructions, when trying to enable the plugin, I get the following error:
Unable to load addon script from path: 'res://addons/haxe/editor-plugin-main/scripts/haxe.gd' There seems to be an error in the code, please check the syntax.

It's because I downloaded this editor repo using the download link in the README, and unzipped it in addons/haxe, but github creates an extra directory level. I ended up moving the files out of the sub-directory like this:
cd <project_dir>
mkdir -p addons/haxe
cd addons/haxe
unzip ~/Downloads/editor-plugin-main.zip
mv editor-plugin-main/* .
rmdir editor-plugin-main

Then the plugin can be successfully enabled:


Is there an configuration option to disable Duktape.env?

Similar to DUK_USE_DUKTAPE_BUILTIN which can disable Duktape.pointer() usage. Is there a way to disable Duktape.env so that Duktape.env won't output system/compiler information?
Thanks.

Not at present; it wouldn't be difficult to add.
But, you can also just run the following after you have created the Duktape heap (and after creating a new global context if you do that):
duk_eval_string(ctx, "delete Duktape.env");

Also, it's quite likely Duktape.env will be removed at some point when the Duktape built-in is reorganized. For some of the bindings it might be better if they were by default only available to C code (not JS code).

Thanks for your reply!


Vimeo-dl command not found

Hello! I cloned the files to Kali Linux and when I run some command I get "vimeo-dl command not found". Can you help me?

Hi! Which version of go are you using? If it is 1.6 or later, try go install github.com/akiomik/vimeo-dl instead of go get -u github.com/akiomik/vimeo-dl. vimeo-dl will install in $GOBIN or $GOPATH/bin.

Sorry but... what operating system should I use?  I am trying to clone it from kali linux with the "git clone" command.

You can use Windows, macOS, or Linux (probably includes Kali Linux) as your OS, but you must have go installed.
go is a programming language, and this project is written in go. This repository does not contain the binary (i.e. vimeo-dl), so you need to compile it with go install.
If you do not have go installed on your system, please try installing it first.
https://go.dev/doc/install

I've just released vimeo-dl v0.0.2 and uploaded the binary to the release page 🎉
This binaries don't require Go to be installed, so please try it out.
https://github.com/akiomik/vimeo-dl/releases/tag/v0.0.2

Thanks for everything! The file downloaded using Go worked fine for me! You are a genius :) Great job


Actionsheet need more bottom spacing on iPhone X

Ionic version:  (check one with "x")
(For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1)
[X ] 2.x
[X] 3.x
I'm submitting a ...  (check one with "x")
[X ] feature request
Current behavior:
The last action of an actionsheet is displayed to close from the home button on iPhoneX (see screenshot)
Expected behavior:
A bit of more spacing between the last action of an actionsheet and the home button on iPhoneX
SIfteps to reproduce:
Sample minimal application: https://github.com/peterpeterparker/ionic-iphonex
Other information:

For example, share action sheet as a bottom-padding

Thank you for checking on that. I had noticed that as well and informed the team that is working on the iPhone X adjustments. I had also noticed similar issues with the date picker and "bottom" toasts.
If you notice any others, please let me know. This information is very helpful to us.

I just tested this with<EMAIL_ADDRESS>and the issue is resolved. Please give 3.7.0 a try in combination with the iOS 11 checklist.

@kensodemann I could confirm that this issue is resolved. Bottom spacing of the action sheets is correct on iPhone X and is still correct too on iPhone 8 for example (tested both with simulator).
thx guys for the enhancement!


Cannot add answer override for catalog app which doesn't have questions.yaml

rancher/rancher:master 02/14
Steps to reproduce

Enable Helm Incubator
Launch an app from Helm Incubator
Click the Add Override button in Answer Overrides section

Results:
User cannot add any override as there is no question in this catalog

I think this is not working correctly:
When you create a MC app that does not have questions.yaml you can still create your own answers and you can overwrites those answers now:

Why are we sending two answers? Shouldn't we overwrite answer number 0 so we just send answer 0 with foo: tacos ?
When I submit I do indeed see in API two answers:
answers": [ 2 items
{
"clusterId": null,
"projectId": null,
"type": "/v3/schemas/answer",
"values": {
"foo": "bar"
}
},
{
"clusterId": null,
"projectId": "c-g5ktw:p-z7r8t",
"type": "/v3/schemas/answer",
"values": {
"foo": "tacos"
}
}

I think this is not working correctly:
When you create a MC app that does not have questions.yaml you can still create your own answers and you can overwrites those answers now:

Why are we sending two answers? Shouldn't we overwrite answer number 0 so we just send answer 0 with foo: tacos ?
When I submit I do indeed see in API two answers:
answers": [ 2 items
{
"clusterId": null,
"projectId": null,
"type": "/v3/schemas/answer",
"values": {
"foo": "bar"
}
},
{
"clusterId": null,
"projectId": "c-g5ktw:p-z7r8t",
"type": "/v3/schemas/answer",
"values": {
"foo": "tacos"
}
}

Re-opening; pretty sure this is not expected behavior. Otherwise please let me know if I made a mistake in my testing. See the first screenshot. There are no answers in helm incubator therefor in UI I must make one and then I can override mine (which seems a little odd). Is this just a misunderstanding? A separate bug? Thank you.

Assigned back to me -- there was a misunderstanding around how answer overrides work -- what I am seeing in the HTTP / API is actually correct.

Assigned back to me -- there was a misunderstanding around how answer overrides work -- what I am seeing in the HTTP / API is actually correct.

Version: Master 2.2 (2/25/19)
When you create a MC app that does not have questions.yaml you can still create your own answers and you can overwrite those answers now:

HTTP:

API:
answers": [ 2 items
{
"clusterId": null,
"projectId": null,
"type": "/v3/schemas/answer",
"values": {
"foo": "bar"
}
},
{
"clusterId": null,
"projectId": "c-g5ktw:p-z7r8t",
"type": "/v3/schemas/answer",
"values": {
"foo": "tacos"
}
}

You can also just fill in the question as a plain text box assuming you have not created any of your own answers already:

HTTP:

API:
answers": [ 2 items
{
"clusterId": null,
"projectId": null,
"type": "/v3/schemas/answer"
},
{
"clusterId": null,
"projectId": "c-g5ktw:p-z7r8t",
"type": "/v3/schemas/answer",
"values": {
"my2ndquestion": "my2ndanswer",
"my3rdquestion": "my3rdanswer",
"myquestion": "myanswer"
}
}


GL window won't appear in Robofont v1.7.3

Window won't appear, though focus comes off of the main Robofont window, when the extension icon is clicked.
Here's the traceback I get:
Traceback (most recent call last):
  File "/Applications/RoboFont.app/Contents/Resources/lib/python2.7/vanilla/vanillaWindows.py", line 484, in windowDidBecomeMain_
    self._alertBindings("became main")
  File "/Applications/RoboFont.app/Contents/Resources/lib/python2.7/vanilla/vanillaWindows.py", line 455, in _alertBindings
    return callback(self)
  File "/Users/lukas/Library/Application Support/RoboFont/plugins/Ghostlines.roboFontExt/lib/ghostlines/windows/ufo_delivery_window.py", line 42, in fetch_applicants
    self.window.applicants.fetch()
  File "/Users/lukas/Library/Application Support/RoboFont/plugins/Ghostlines.roboFontExt/lib/ghostlines/applicant_list.py", line 70, in fetch
    registry = response.json()
  File "/Library/Python/2.7/site-packages/requests/models.py", line 818, in json
    self.content.decode(encoding), **kwargs
  File "json/__init__.pyc", line 338, in loads
  File "json/decoder.pyc", line 366, in decode
  File "json/decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
Traceback (most recent call last):
  File "/Applications/RoboFont.app/Contents/Resources/lib/python2.7/vanilla/vanillaBase.py", line 211, in action_
    self.callback(sender)
  File "/Users/lukas/Library/Application Support/RoboFont/plugins/Ghostlines.roboFontExt/lib/ghostlines/toolbar.py", line 55, in openSender
    UFODeliveryWindow(CurrentFont()).open()
  File "/Users/lukas/Library/Application Support/RoboFont/plugins/Ghostlines.roboFontExt/lib/ghostlines/windows/ufo_delivery_window.py", line 57, in open
    self.window.open()
  File "/Applications/RoboFont.app/Contents/Resources/lib/python2.7/vanilla/vanillaWindows.py", line 236, in open
    self.show()
  File "/Applications/RoboFont.app/Contents/Resources/lib/python2.7/vanilla/vanillaWindows.py", line 263, in show
    self._window.makeKeyAndOrderFront_(None)
  File "/Applications/RoboFont.app/Contents/Resources/lib/python2.7/vanilla/vanillaWindows.py", line 484, in windowDidBecomeMain_
    self._alertBindings("became main")
  File "/Applications/RoboFont.app/Contents/Resources/lib/python2.7/vanilla/vanillaWindows.py", line 455, in _alertBindings
    return callback(self)
  File "/Users/lukas/Library/Application Support/RoboFont/plugins/Ghostlines.roboFontExt/lib/ghostlines/windows/ufo_delivery_window.py", line 42, in fetch_applicants
    self.window.applicants.fetch()
  File "/Users/lukas/Library/Application Support/RoboFont/plugins/Ghostlines.roboFontExt/lib/ghostlines/applicant_list.py", line 70, in fetch
    registry = response.json()
  File "/Library/Python/2.7/site-packages/requests/models.py", line 818, in json
    self.content.decode(encoding), **kwargs
  File "json/__init__.pyc", line 338, in loads
  File "json/decoder.pyc", line 366, in decode
  File "json/decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
Traceback (most recent call last):
  File "lib/doodleDelegate.pyc", line 169, in sendEvent_
  File "/Applications/RoboFont.app/Contents/Resources/lib/python2.7/vanilla/vanillaBase.py", line 211, in action_
    self.callback(sender)
  File "/Users/lukas/Library/Application Support/RoboFont/plugins/Ghostlines.roboFontExt/lib/ghostlines/toolbar.py", line 55, in openSender
    UFODeliveryWindow(CurrentFont()).open()
  File "/Users/lukas/Library/Application Support/RoboFont/plugins/Ghostlines.roboFontExt/lib/ghostlines/windows/ufo_delivery_window.py", line 57, in open
    self.window.open()
  File "/Applications/RoboFont.app/Contents/Resources/lib/python2.7/vanilla/vanillaWindows.py", line 236, in open
    self.show()
  File "/Applications/RoboFont.app/Contents/Resources/lib/python2.7/vanilla/vanillaWindows.py", line 263, in show
    self._window.makeKeyAndOrderFront_(None)
  File "/Applications/RoboFont.app/Contents/Resources/lib/python2.7/vanilla/vanillaWindows.py", line 484, in windowDidBecomeMain_
    self._alertBindings("became main")
  File "/Applications/RoboFont.app/Contents/Resources/lib/python2.7/vanilla/vanillaWindows.py", line 455, in _alertBindings
    return callback(self)
  File "/Users/lukas/Library/Application Support/RoboFont/plugins/Ghostlines.roboFontExt/lib/ghostlines/windows/ufo_delivery_window.py", line 42, in fetch_applicants
    self.window.applicants.fetch()
  File "/Users/lukas/Library/Application Support/RoboFont/plugins/Ghostlines.roboFontExt/lib/ghostlines/applicant_list.py", line 70, in fetch
    registry = response.json()
  File "/Library/Python/2.7/site-packages/requests/models.py", line 818, in json
    self.content.decode(encoding), **kwargs
  File "json/__init__.pyc", line 338, in loads
  File "json/decoder.pyc", line 366, in decode
  File "json/decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded

Figured this out—there was an issue on the server side that was sending bad info back.


LDAP Error

How can i check the LDAP configuration and error log ?
Found: /logs/kirjuri.log
ldap_connect(): Could not create session handle: Bad parameter to an ldap routine, File: /home/xxx/www/web/include_functions.php, line 171";/submit.php?type=login;<IP_ADDRESS>;-;Session ID: -;-;

TBH the LDAP part was hacked together in a few hours and then swiftly forgotten about so I'm not sure where the errors get logged; I can't test it right now to find out.
The configuration is at conf/settings.conf, there are four configuration directives you can change there. Kirjuri logs most of it's stuff into the PHP error log and it's own app log under logs/
Make sure you have the necessary web server dependencies installed for LDAP to function with your installation.
(This project is no longer under active development so I'm sorry for being unable to provide more help.)


Fix eth pubkey to plasm address mismatch bug

Required Tasks

[ ] add encryption unit tests
[ ] add unit testing for efficient work
[ ] find the reason as to why this bug is happening!

Description
There is a glitch where the plasm address generated from the lockdrop participant's public key does not match the one on Plasm chain. This glitch is most likely caused due to a minor issue within the cryptographic pipeline.
Estimated dev time
two research days and 6 hours of work

Checked 👍


Coverage differences without change

Please investigate why #7490 and #7488 show coverage changes for DynamicLinks and Database even though there were no changes in those libraries.

The reason for that is probably caused by changes happening between the base commit and the head commit.
On solution could be update the base commit to the head of the merged branch, master in this case.

Hmm, neither of those libraries have had any recent changes?

Have tried scripts/build.sh and unit tests via podspec in #7585, they have the same result.
I tried locally on the base commit, and the result is the same as the one in the pull requests.
Based on the xcresults, the difference of code coverages is from here, where the coverage in a pull request is 83.9% while the one in the base commit is 59.1%.
Has rerun the workflow runs to upload new code coverages to see if the data is updated. Will also investigate why the tests for code coverage are not consistent between the merge and pull requests.

Looks like the eventCode is not consistent  here. Unit tests do not have a consistent coverage on the switch cases. I suspect that is due to the stream?

Oh good find.  Do you know if there is best practice for measuring coverage on unit tests that exercise networking code that is not consistent? I wonder if there should be more mocking?
cc: @schmidt-sebastian @maksymmalyhin @ryanwilson

Looks like currently we use both unit and integration tests for measuring coverage. We may consider excluding less stable integration tests from the measurement. Also I'd be curious what exactly conditions lead to different coverage for the tests. Maybe we can just make it more stable. I'll take a look and let you know if I find something.

Unit tests should be the one measured in the coverage workflow. Except for Firestore and Peformance, tests are running unit in podspecs, e.g. database. I ran locally and it turned out the safeHandleEvent did not have a consistent number of calls as well. If the internet is disconnected, the coverage will be consistent since only NSStreamEventErrorOccurred will be called.
If unit tests are using network, we probably need to mock the return code.


how to use multiple or where ?

Please be aware that these issues will be closed if inactive for more then 14 days :)
i 'm think this is not working

Please take a look at #148.


refactor(allocator): move GetAddress trait into oxc_allocator

Pure refactor. It makes more sense to me for Address and GetAddress to be defined in the same place. Also then we can use the trait for impl GetAddress for Box.

[!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

#6738  👈
#6737
main

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

Join @overlookmotel and the rest of your teammates on  Graphite

Merge activity

Oct 21, 7:43 AM EDT: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.


Customize pageTheme for pages and cards

Feature Suggestion
The current implementation of the Header Component have fixed colors and it can't be modified using the theme customization, so it's a lock for changing the look and feel.
https://github.com/spotify/backstage/blob/35abda0fa0d7402a0024ee4f53971d93ad0b0b8d/packages/core/src/layout/Page/PageThemeProvider.ts#L52-L61

Possible Implementation
To solve this we need to remove the use of @backstage/core -> pageTheme and maybe add the definition to the createTheme from @backstage/theme to include the object for the customization of the pageTheme like:
const myTheme = createTheme({
  pageTheme: {
    home: genPageTheme(colorVariants.teal, shapes.wave),
    documentation: genPageTheme(colorVariants.pinkSea, shapes.wave2),
    tool: genPageTheme(colorVariants.purpleSky, shapes.round),
    service: genPageTheme(colorVariants.marineBlue, shapes.wave),
    website: genPageTheme(colorVariants.veryBlue, shapes.wave),
    library: genPageTheme(colorVariants.rubyRed, shapes.wave),
    other: genPageTheme(colorVariants.darkGrey, shapes.wave),
    app: genPageTheme(colorVariants.toastyOrange, shapes.wave),
  },
  palette: lightTheme.palette,
  fontFamily: 'Comic Sans MS',
});

I'm not entirely sure about how to make this change without affecting all the plugins.

Context
When trying to customize the look and feel the current implementation is good enough for most of app, but the headers for pages and cards are fixed to use the default colors on backstage. Allowing to do that it's good when an adopter needs to match the portal with the internal branding.

I would like to work on it.

Nice, assigned you @Marvin9

@mijailr I have implemented for pages. However as this issue addresses cards too, can you please elaborate on that one?

Many thanks @Marvin9 the part related with cards should have a similar approach.
As you can see here:
https://github.com/spotify/backstage/blob/1518741f67fe706edc2e4dd468fcc5da0befe66c/packages/core/src/layout/ItemCard/ItemCard.tsx#L19-L38
The styles can't be customized.


Added Bengali translation for README and updated base files

Added Bengali translation for README and updated base files
This pull request adds Bengali translation for the README.md file and updates the base README.md and CONTRIBUTION.md files to include a link to the translated version.
Partly fixes #1
Why ?
This pull request aims to make the project more accessible and inclusive for Bengali speakers who want to learn about it or contribute to it.
Changes
The tasks involved in this pull request are:

[x] Created a new file named README-bengali.md with the Bengali translation of the README file
[x] Updated the base README file to include a link to the Bengali translation
[x] Fixed the links and typos of the base README file
[x] Updated the language of CONTRIBUTION file to make it more user friendly

The expected outcome of this issue is to have a fully functional Bengali translation of the README file and updated base files that reflect the changes.
Testing
The translated README.md file was previewed on GitHub and verified that the formatting and links are working correctly. The base README.md and CONTRIBUTION.md files were also previewed on GitHub and checked for any typos or broken links.

Thanks!! Merging now ❤

Thanks for merging! ❤
Could you please add hacktober and hacktoberfest-accepted labels to this PR? It would help me climb up the ladder!

Thanks for merging! ❤ Could you please add hacktoberfest and hacktoberfest-accepted labels to this PR? It would help me climb up the ladder!

Sure!

Thanks a lot ❤


slang-tag-version.h doesn't get updated for windows releases

All the slang-tag-version.h headers have #define SLANG_TAG_VERSION "unknown" in the windows builds. The Mac and Linux contain the correct header.

Thanks for heads up, will look to fix now.

On checking packages built with #2429 it looks the files are now being set on windows.


[$500] Web - Contact list - Scroll wheel slide does not work on contact list but works on chat switcher

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: v1.4.15-4
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal team
Slack conversation:
Action Performed:

Click on search icon to open chat switcher
While on the contact list hold down the mouse scroll wheel button and slide through the contact list
Go back and click on FAB
Click on Request money > Enter an amount > Click next
While on the contact list hold down the mouse scroll wheel button and slide through the contact list
Compare the result of step 5 with step 2

Expected Result:
Scroll wheel slide should work on both contact lists and on chat switcher
Actual Result:
Scroll wheel slide does not work on contact list but works on chat switcher list
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/93399543/dca63717-6807-4398-9a65-435a258d744e
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01c2fb43a4d63fb946
Upwork Job ID:<PHONE_NUMBER>901796352
Last Price Increase: 2023-12-28

Not overdue, waiting for proposals

I don't actually understand the bug report and don't see any issues in the recorded video. I'm going to close the issue, if anyone disagrees and thinks this is something we should solve right now, please raise for discussion in #expensify-open-source in Slack. Thanks!


docs: properly capitalize brands GitHub and SendGrid

Ensure brands are properly capitalized
SendGrid
GitHub

Hello @aslafy-z,Thanks again for the PR! It's HACKTOBERFEST! We want to show our appreciation by sending                                              you some special Hacktoberfest swag. If you have not already, could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX

Hello @aslafy-z,Thanks again for the PR! We appreciate your contribution and look forward to                                              continued collaboration. Thanks!                                             Team SendGrid DX


python - torch auto-patchelf could not satisfy dependency libcuda.so.1

I've got a python poetry project that uses a version of torch - this requires cuda to be available. The package itself fails to build with the following error:
       > auto-patchelf: 1 dependencies could not be satisfied
       > error: auto-patchelf could not satisfy dependency libcuda.so.1 wanted by /nix/store/nxy6vswgy0s0vzadv4cdsa2p2rnhm1a9-python3.10-eurmars-classifier/lib/python3.10/site-packages/torch/lib/libcaffe2_nvrtc.so
       > auto-patchelf failed to find all the required dependencies.
       > Add the missing dependencies to --libs or use `--ignore-missing="foo.so.1 bar.so etc.so"`.

I've noticed that the NixOS package adds libcuda.so.1 to the ignore list due to it being a runtime issue:
https://github.com/NixOS/nixpkgs/blob/e11142026e2cef35ea52c9205703823df225c947/pkgs/development/python-modules/torch/bin.nix#L54-L60
So I have two options:

Somehow add this to an --ignore-missing
Add cuda to torch build

So far I have failed to get either approach working. Here are some of my attempts:
        myapp = dream2nix.lib.makeFlakeOutputs {
            systems = [ system ];
            config.projectRoot = ./.;
            source = ./.;
            projects = ./projects.toml;

            packageOverrides = {
                torch = old: {
                    buildInputs = old.buildInputs ++ [ pkgs.cudatoolkit ];
                };
            };
        };

        myapp-base = dream2nix.lib.makeFlakeOutputs {
            systems = [ system ];
            config.projectRoot = ./.;
            source = ./.;
            projects = ./projects.toml;
        };

        myapp = myapp-base.packages.${system}.default.overrideAttrs (old: {
            autoPachelfIgnoreMissingDeps = [ "libcuda.so.1" ];
            propagatedBuildInputs = old.propagatedBuildInputs ++ [
                pkgs.cudatoolkit
            ];
        });

Any thoughts on how to get this working? I've been also trying with poetry2nix and having different kinds of failures, so I'm pursuing both that and dream2nix to see which I can get working first.
Thanks in advance

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/dream2nix-with-python-poetry-pytorch-libcuda-so-1-not-found/30300/1


9210 rel phrase refactoring

This resolves issue #9210 (https://support.onefact.net/issues/9210)

Support added to refactor event parameters and their corresponding state parameters. See issue #9218 (https://support.onefact.net/issues/9218)


[[Feature Request]] Search within Journals to link pages

So with the new V2 Journal update, I realized that as you add things, if you have a page within a Journal with the same title, currently it doesn't use that page to fulfill the link. Only separate Journals currently. It'd be great to have that added to the mod if possible.

I'll look into it, I'd like it working with pages as well ;)

I just found this module, and this mod is amazing. Wanting to add to this feature request of searching within journals: I noticed it links wiki links to compendia when you create the new journal. It would be handy to be able to "refresh links" so that it would link compendia that may have been created after the journal was importet.
Really great work on this module, I hope you can find the motivation to maintain it! I will be happy to donate on ko-fi if that helps!


Getting Status 403 when "Collect Build Info" is not "true"

Hey guys,
we are getting a 403 on the generic upload task in Azure Pipelines if we don´t se "Collect Build Info"
Log:
Starting: Generic upload
Task         : Artifactory Generic Upload
Description  : Upload build artifacts to Artifactory using FileSpecs while allowing to collect build-
info. The collected build-info can be later published to Artifactory by the "Artifactory Publish Build
Info" task.
Version      : 1.7.4
Author       : JFrog
Help         :
Found tool in cache: jfrog 1.30.3 x64
Running jfrog-cli from d:\a_tool\jfrog\1.30.3\x64\jfrog.exe.
JFrog CLI version: 1.30.3
Using file spec:
{
"files": [
{
"pattern": "d:\a\1\a/xxxx.zip",
"target": "xxxxx"
}
]
}
[Info] [Thread 2] Uploading artifact: d:\a\1\a\xxxx.zip
[Error] [Thread 2] Artifactory response: 403 Forbidden
{
"status": "failure",
{
"totals": {
"errors": [
"success": 0,
{
"failure": 1
"status": 403,
}
"message": ""
}
}
]
}
[Error] Failed uploading 1 artifacts.
##[error]Error: Command failed: d:\a_tool\jfrog\1.30.3\x64\jfrog.exe rt u --url="https://xxxx" --spec="d:\a\1\s\uploadSpec1573232531243.json" --user=*** --password=*** --fail-no-op=true
Finishing: Generic upload

@chrizzo84,
We've just tried reproducing this, and it seems to be working for us.
Few questions:

We assume that you masked the target in the file spec as "xxxxx". If so, can you please share with us the complete file spec you used? Please send us the spec text as you saved it in the UI and not the spec as it appears in the log. This may provide us with a hint to the cause of this issue.
Is the file uploaded successfully when setting the Collect build info checkbox to on? Nothing is the task configuration is changed besides this?

Thanks

@chrizzo84,
Adding the previous questions, one of the reasons for a 403 Forbidden response can be received, is a wrong target repository name. Does the target repository configured exist and is it accessible for the user used?

@eyalbe4,

File spec in UI:
{
"files": [
{
"pattern": "$(Build.ArtifactStagingDirectory)/dist-$(version).zip",
"target": "supplier-portal-food-generic/EXS/"
}
]
}

Yes, the file is successfully uploaded when 'Collect build info' is selected and nothing in the task configuration is changed besides this.

Hope this helps.

@eyalbe4,
The target repository definitely exists. As mentioned just the 'Collect build info' is selected to get it working.

@Chimera96,
As @eyalbe4, we couldn't reproduce the issue.
We have, however, some thoughts. It will be helpful if you can provide us with the following details:

Are you using hosted agent or private agent? Can you please provide us with more information about the agent such as the OS version? Also, if you are using private agent, you can try to delete the tasks cache in <agent_home>\_work\_tasks\Artifactory*
By looking into the Artifactory's logs we can conclude the root cause of the 403 error. For example, if the repository does not exist, we can see in artifactory.log: should be a repo request and does not match any repo key. To see artifactory.log, follow the instructions here.
What is your Artifactory's version?

Thanks.

@Chimera96 and @hrizzo84,
Are you still experiencing this issue with the latest release?


⚠ ClamAV has degraded performance

In 58ddc54, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 428 ms

Resolved: ClamAV performance has improved in e6a70b8.


Bors retry can cause unreviewed code to be merged

Currently it is possible for the following to happen:

Maintainer queues a merge with bors r+
Bors fails for some reason
PR author adds new arbitrary unreviewed code
PR author calls bors retry

This allows arbitrary unreviewed code to be committed. In general this isn't a problem because the PR author has already indicated that they are trustworthy by getting the initial approval / not adding malicious code. But this is still a hole and we should close it.
#6992 was created in an attempt to fix it, but it wasn't a full solve. Ideally this is fixed in upstream bors, probably by making bors retry require the same permissions as bors r+.

Ideally this is fixed in upstream bors, probably by making bors retry require the same permissions as bors r+.

Simpler would be to have an option to disable bors retry. A user that can trigger it should already be able to use the commands they have permissions for.

Is this considered solved with the transition to Github merge queue?

Yup


docs: provides a suggested path through the docs after the quickstart

(#3179)
What type of PR is this?
docs PR
What this PR does / why we need it:
adds a subsection after completing the quickstart with a suggested list of tasks to try out.
Which issue(s) this PR fixes:
Fixes #3179

/retest

/retest


CFLinuxsf4 Stack for Applications

In order to ensure we move out of bionic for buildpacks, we want to start testing our applications using the cflinuxsf4 stack
Acceptance Criteria

[ ] Verify that language buildpacks are supporting cflinuxsf4 - Example: https://github.com/cloudfoundry/nodejs-buildpack/releases/tag/v1.8.0
[ ] CG Applications working on new stack
[ ] Customer communication about moving to cflinuxsf4

Security considerations
cflinuxsf3 is EOL in April
Implementation sketch

[ ] Confirm all our default buildpacks have new stack added
[ ] Start testing our simple apps with new stack - doc here: https://docs.cloudfoundry.org/devguide/deploy-apps/stacks.html
[ ] Blog post or status page about new stack

Superseded by other tickets


Support python 3.5

Python 3.5 is released on 2015/09/13.
https://www.python.org/downloads/release/python-350/

I added py3.5 to test environment.
https://github.com/pfnet/chainer-test/pull/35


Dockerfile deploy doesn't honor repository's exposed port for readiness check

Sorry I put this here but I don't now which deis service handles this cases!
Came across this when using a Dockerfile like this:
FROM nginx
EXPOSE 80

by simply doing this, and pushing to deis, the readiness check points to port 443, this is because nginx image Dockerfile exposes both 80 an 443 and Deis seems to choose this instead of honoring the repository's dockerfile
How to reproduce:

git init
Create a Dockerfile

echo "FROM nginx
EXPOSE 80" > Dockerfile

git add Dockerfile
git commit -a -m Test
deis create test-expose
git push deis master
kubectl get po --namespace=test-expose
kubectl describe po --namespace=test-expose <podname> |grep Readiness

Result:
    Readiness:		tcp-socket :443 delay=5s timeout=5s period=5s #success=1 #failure=1

Expected result:
Deis should honor any exposed port from the repository's Docker file rather than the ones on the base image:
    Readiness:		tcp-socket :80 delay=5s timeout=5s period=5s #success=1 #failure=1

hey @n0n0x, at this time we only support dockerfile apps that expose only one port for these reasons.
That being said we are currently working on rewriting how health checks can be configured, which you can follow along in https://github.com/deis/controller/issues/603.

Oh, I misunderstood the documentation. Because I am actually explicitly telling to expose port 80 in my Dockerfile, but It exposes port 443 because of the inherited Dockerfile from the nginx image. I thought if I explicitly declare EXPOSE 80 on my Dockerfila that would override it.

Yeah that's what I thought too, but that is something built into docker. all child images inherit anything from parents, including exposed ports.

Awesome, thanks for the explanation! I am closing this.


Re-adds divider on refresh

Can you create a method of removing itemdecoration on pull to refresh? Currently when a recyclerview is refreshed it adds the divider along with the existing one.

@DaveMurchison83 Can you post here some code demonstrating how you are using the divider?

Sure.
Very simply, after setting the recyclerview adapter, I call your code:
                            mRecyclerView.setAdapter(adapter);

                            RecyclerViewDivider.with(rootView.getContext())
                                    .color(rootView.getContext().getResources().getColor(R.color.listDivide))
                                    .hideLastDivider()
                                    .build()
                                    .addTo(mRecyclerView);

When I use pull to refresh, it clears the recyclerview but the divider isn't cleared, so when the recyclerview is populated again, it adds a second divider under each item.
If I use the official Android method of adding dividers, it works:
                            mRecyclerView.setAdapter(adapter);

                            mRecyclerView.removeItemDecoration(itemDecorator);

                            itemDecorator = new DividerItemDecoration(mRecyclerView.getContext(),
                                    linearLayoutManager.getOrientation());
                            mRecyclerView.addItemDecoration(itemDecorator);

                            itemDecorator.setDrawable(ContextCompat.getDrawable(context, R.drawable.divider));

So it looks to me that by calling removeItemDecoration before setting a divider would work.

Actually, you can remove the RecyclerViewDivider as you are doing with the Android method.
You can do it using the method below in RecyclerViewDivider class:
void removeFrom(@NonNull RecyclerView recyclerView)

So, taking your example changing the DividerItemDecoration to RecyclerViewDivider, the result is:
divider.removeFrom(mRecyclerView);

mRecyclerView.setAdapter(adapter);

divider = RecyclerViewDivider.with(rootView.getContext())
        .color(rootView.getContext().getResources().getColor(R.color.listDivide))
        .hideLastDivider()
        .build();

divider.addTo(mRecyclerView);

@DaveMurchison83 If the issue is solved, can you close it?

@DaveMurchison83 I'm closing it, reopen it again in case.


[Suggestion] viewBox : Int -> Int -> Int -> Int -> Attribute msg

I believe the viewBox : Int -> Int -> Int -> Int -> Attribute msg type signature would be more intutive than viewBox : String -> Attribute msg.
Html.Attributes has adaptations like this, such as Html.Attributes.spellcheck, which uses the Bool -> Attribute msm signature instead of the traditional String -> Attribute msg.

You can use viewBoxof Typed Svg library
https://package.elm-lang.org/packages/elm-community/typed-svg/6.0.0/TypedSvg-Attributes


Issue/PR stats images in README do not update

Hard refresh of the repo homepage shows this:

But clicking through on the issuestats images shows fresher info:

Github gurus, what's the deal?

when i click, i get same stats on http://issuestats.com/github/Microsoft/visualfsharp ( 12, 18 )

@latkin i repro, you too? maybe is easier to remove the badge? or close this bug

Yes I still repro.  Of course, it makes it look like we have really fast turnaround :)
If https://github.com/hstove/issue_stats/issues/20 is tracking the root cause, let's see if that is going to be fixed.  If that is moving forward then we will benefit from the fix.  If there is nothing happening there then we should just remove the badges.  Thanks for pinging them, I will do the same.

@latkin bug is still here and no activity on issue, remove the badges?

Left one more ping, will remove them in a week or so if we don't hear back

Never heard back. Issue stats are now removed.


Automate version bumping

We should add a git action to auto-bump the dojo versions on release.

Hey @ponderingdemocritus, I can work on it


Cannot connect to videoStream server from scrcpy ...

Hello everyone, I am building a project on nodejs and scrcpy. I try to get the video stream from scrcpy by running a socket:
adb forward tcp:8000 localabstract:scrcpy
adb push C:/ProgramData/scrcpy-win64-v2.0/scrcpy-server-v2.0 /data/local/tmp/scrcpy-server-v2.0.jar
adb shell CLASSPATH=/data/local/tmp/scrcpy-server-v2.0.jar app_process / com.genymobile.scrcpy.Server 2.0 tunnel_forward=true max_fps=30 cleanup=false max_size=1600 raw_video_stream=true

const WebSocket = require('ws');
const {spawn} = require('child_process');
const fs = require('fs');
const {Buffer} = require('buffer');

const ws = new WebSocket('ws://<IP_ADDRESS>:8000');

ws.on('message', (data) => {
    console.log(`data:`, data); // Nothing log in here
    const dataEncode = new Uint8Array(Buffer.from('data'));
    fs.writeFile('ws.txt', dataEncode, (err) =>{
      if(err) throw err;
      console.log('Write Successed');
    })
});

the localhost:8000 running, i use html try to display the video stream, but nothing display. I try some button (increase voulme, decrease volume..) to control the device, it works fine. And then I know this is server control-socket, not server return h264 data.
Please give me a code or guideline that i can open server video-socket.
Thank eveyone...

Try to add control=false audio=false, otherwise it waits for other socket connections.

Try to add control=false audio=false, otherwise it waits for other socket connections.

Thank bro, i spent one day do find a way. But i with this way I can connect only one device. How can i connect and get multiple video stream from multiple device? Do you have any document about this case?
Thank bro.


[FEATURE] Add Wrap Alignment inside Toolbar

By Default, when we have a row of actions, Wrap alignment is always in: WrapAlignment.start,

By creating this parameter to be user editable gives the freedom to be dynamic with any design.

Hi @DarkMarksDoe
I have added all Wrap properties in the ToolBar, which allows more customisation of the toolbar. It is now available in the new version 2.1.7
I appreciate your feedback
Thanks!


Analyzer: control flow collections phase 2

Phase 2 covers tool support.  For the analyzer this means high quality error messages, parser recovery, and quick fixes.
Note that this should be behind an experimental flag.
See the language tracking issue: https://github.com/dart-lang/language/issues/165
And the feature specification: https://github.com/dart-lang/language/blob/master/accepted/future-releases/control-flow-collections/feature-specification.md
And the implementation plan: https://github.com/dart-lang/language/blob/master/accepted/future-releases/control-flow-collections/implementation-plan.md
Subtasks include:

[x] IDE quick fixes using spread and if #35867

I don't know whether there is more work here that we wanted to get done or whether we should close this.

I'm happy to consider it done at this point.