Skip writing null storage quota config to table configx

Current coverage is 64.65% (diff: 20.00%)

Merging #955 into master will increase coverage by 0.02%

@@             master       #955   diff @@
==========================================
  Files           764        764
  Lines         35927      35929     +2
  Methods           0          0
  Messages          0          0
  Branches       5388       5390     +2
==========================================
+ Hits          23218      23229    +11
+ Misses        11215      11188    -27
- Partials       1494       1512    +18

Powered by Codecov. Last update c104452...527b17d


Logfile functionality incomplete

There are quite a few remaining perror()s and such that should be wrapped into appropriate logfile handling function(s).

Closed by Issue #37 merge.


date for notes

ex. "last updated 10.5.2022"
consider adding original post date aswell

@GemperC I don't have any helpful doc to provide but I implemented it in my fork. It's using frontmatter from the .md, eg:
---
title: "You can also override the title"
created: 2023-02-01
updated: 2023-02-10
extra:
    something: "I'm also passing down any extra to the template, can be useful!"
---

Output when only created is provided:
Posted February 1, 2023

Output when both created and updated are provided (and are different):
Posted February 1, 2023, last updated February 10, 2023

I'll eventually document it but for now hopefully this can help you!

Yeah I think that'd be a great option to have for sure. I personally prefer having control over those dates, especially the updated one. My garden is very recent and isn't read by anyone at the moment but I'd like to think that it will be eventually, and I'd rather not have the Last Updated date changed for a quick typo fix.


Add search on card's name

Search with substring on card's name
Add ALL colors and ALL types in comboboxes

Done.
Exclusive with comboboxes


Rendering backface of the discs

Hi,
thanks for sharing the implementation. I have a short question.
Are discs rendered on both sides or are they rendered only when looking at their top face? (like in common mesh visualization)

Hi @magistri,
I apologize for the delay! In our implementation you can filter points using back-face culling since we analytically compute normals by computing a derivative of SDF with respect to input point locations. Alternatively, you can use an HPR operator as described in here. If both options are disabled, you'll be rendering them on both sides.


How can I add watermark on pic?

Hello @Abeautifulsnow
With the latest release, you could define your own file handler backend class:
https://github.com/django-ckeditor/django-ckeditor/blob/master/ckeditor_uploader/backends/pillow_backend.py#L16
register it,
https://github.com/django-ckeditor/django-ckeditor/blob/master/ckeditor_uploader/backends/__init__.py#L26
and use it, defining the CKEDITOR_IMAGE_BACKEND setting.

I have been looking at overriding the PillowBackend create_thumbnail function to make it crop thumbnails square (I'm sure it used to do this - now it keeps the original image aspect ratio...). What would be the best way to register the custom image backend? I'm not sure where I should do this.


Set proper package name

Resolves #74

@Lirt ready for review

Hi,
Is this MR OK to be merged as first? Probably followed by this small MR - https://github.com/Lirt/velero-plugin-for-openstack/pull/76/files?

The sequence doesn't really matter :)


Weird Delay after unzooming.

Hello JaeYeop, great work on this!
I have a small issue, that when I unzoom, for a period of around ~1 second, I can't zoom back in, nor do I have the zoom symbol anymore.
Thanks again for this.

This seems to have stopped happening, so will close. Must of been something on my end.


Update AzureMonitorLogs ReadMe Image

Added azuremonitorlogs image. Updated readme to reference image

This PR fixes #

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
4 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.007%) to 41.992%

Files with Coverage Reduction
New Missed Lines
%

extensions/notebook/src/common/ports.ts
4
74.14%

Totals

Change from base Build<PHONE_NUMBER>:
-0.007%

Covered Lines:
26506

Relevant Lines:
57213

💛  - Coveralls


Feature/better repack modal 2

As the main feature was reverted, this PR aims to merge the feature definitively
Known issues: When a torrent throws an error after 3 attempts, it logs inside the electron server terminal. It is not breaking anything, but it can be unpleasant to debug other things in the future. I am still trying to find a way to suppress this error message, any help is welcome :)
Error occurred in handler for 'getMagnetHealth': Error: Failed to get seeders and peers after 3 retries.
    at Object.getSeedersAndPeers (file:///home/dev/workspace/projects/opensource/hydra/out/main/index-DrJ3egtA.js:342:43)
    at async WebContents.<anonymous> (node:electron/js2c/browser_init:2:77963)

Ok, two important things

As of #562, Hydra will get the download options from an external source, then we will probably pass the responsability of adding tags to the provider of the JSON
The seeds/peers feature would still be really useful, but I don't know if it is the library or what, but they are not loading most of the time.

Closing this PR, at least for now, as it is not working as we expected


Update website

Remove bower install instructions and add instructions for yarn.
Remove WebUI 8.x documentation and add new WebUI 11.x documentation as default.
Reduce size of images where possible and remove unused images.

Completed.


Let user override timezone

E.g. could be if the user is in Thailand but he is ordering something in the Netherlands (if your shop is Dutch) Then you would like to show the calendar in that timezone. (?)

If providing a timezone
the date, startDate, endDate should probably be in UTC format

@RichardLindhout so I am not sure if i should create a seperate issue but this seems be related to not being able to define a timezone. I am in Germany and a date ends up as a utc timestamp with the previous day at 2200 or 2300 depending on summer time. So while the selection is 21., the resulting timestamp is the 21. in my timezone aswell, just not in UTC and it seems the UTC date is what is used for the "SELECT DATE" value…

Please upgrade package, the week should start on saturday.

date picker should use timezone of device so are you sure emulator is on the same timezone?

Please upgrade package, the week should start on saturday.

the screenshots week starts on saturday, no?

date picker should use timezone of device so are you sure emulator is on the same timezone?

thats not an emulator, its my phone :) and my phone is set to en-US locale, europe aka CET timezone

I mean it should be Sunday :)
What happens if you upgrade to a newer version of the package? The datepicker should pick the timezone of the device and return the right time but we had a bug in a previous version with the grid where it would only work in the Netherlands because we used a wrong Day constructor.
https://github.com/web-ridge/react-native-paper-dates/commit/343f9991bd27cae805cb1cf6e759736a88828f23#diff-2559e2b6c4b0f94fc3c597c197336358332aa49d7d15eb54d8229c1067534d6c
Are you also sure you followed the FormatJS steps in the Android caveats section
https://github.com/web-ridge/react-native-paper-dates#android-caveats
And this part:
  // https://formatjs.io/docs/polyfills/intl-datetimeformat/#default-timezone
  let RNLocalize = require('react-native-localize');
  if ('__setDefaultTimeZone' in Intl.DateTimeFormat) {
    Intl.DateTimeFormat.__setDefaultTimeZone(RNLocalize.getTimeZone());
  }

Trying 0.4.0, same picture :/
Great, thats the only part i left out, but it doesnt work, since i am using expo and not native react-native, i get an error about i should link stuff…

  // https://formatjs.io/docs/polyfills/intl-datetimeformat/#default-timezone
  if ("__setDefaultTimeZone" in Intl.DateTimeFormat) {
    Intl.DateTimeFormat.__setDefaultTimeZone(
      require("expo-localization").timezone
    );
  }

that works though, sunday start, correct day, im happy, thanks for your support :)

Yeah thanks you I'll add this to readme

// https://formatjs.io/docs/polyfills/intl-datetimeformat/#default-timezone
let RNLocalize = require('react-native-localize');
if ('__setDefaultTimeZone' in Intl.DateTimeFormat) {
Intl.DateTimeFormat.__setDefaultTimeZone(RNLocalize.getTimeZone());
}

In which file I can add this ?

@ZohaibNaseer786 if you upgrade RN 0.66 and Hermes you won't need this, it will automatically pick the timezone of the device!


Properties seems to be required

Expected behavior and actual behavior.
The geo interface documentation says that properties is optional, yet it appears to be required by Fiona.
Steps to reproduce the problem.
If I define a schema like so...
schema = {
    "geometry": "Polygon",
    # No properties defined here.
}

This already gives an error if I try to use this schema:
import fiona
from fiona.crs import from_epsg

f = fiona.open("tmp.shp", "w", schema={"geometry": "Polygon"}, crs=from_epsg(3035), driver="GeoJSON")

~/Workspace/anaconda/envs/et/lib/python3.7/site-packages/fiona/env.py in wrapper(*args, **kwargs)
    404             with Env.from_defaults(session=session):
    405                 log.debug("Credentialized: {!r}".format(getenv()))
--> 406                 return f(*args, **kwargs)
    407     return wrapper
    408

~/Workspace/anaconda/envs/et/lib/python3.7/site-packages/fiona/__init__.py in open(fp, mode, driver, schema, crs, encoding, layer, vfs, enabled_drivers, crs_wkt, **kwargs)
    256                 # Make an ordered dict of schema properties.
    257                 this_schema = schema.copy()
--> 258                 this_schema['properties'] = OrderedDict(schema['properties'])
    259             else:
    260                 this_schema = None

KeyError: 'properties'

If I amend the schema to have an empty properties field:
schema = {
    "geometry": "Polygon",
    "properties": {},
}

then the f = fiona.open("tmp.shp", "w", schema={"geometry": "Polygon"}, crs=fiona.crs.from_epsg(3035), driver="GeoJSON") call works, but I still get an error when trying to add a shape without a properties key. The following code...
import fiona
from fiona.crs import from_epsg
from shapely.geometry import Polygon, mapping

with fiona.open(
            "tmp.shp",
            "w",
            driver="GeoJSON",
            crs=from_epsg(3035),
            schema=schema) as source:
    polygon = Polygon(
        [
            (0, 0),
            (1, 0),
            (1, 1),
            (1, 0)
        ]
    )

    shape = dict(geometry=mapping(invalid_shape))
    source.write(shape)

gives the error
~/Workspace/anaconda/envs/et/lib/python3.7/site-packages/fiona/collection.py in write(self, record)
    351     def write(self, record):
    352         """Stages a record for writing to disk."""
--> 353         self.writerecords([record])
    354
    355     def validate_record(self, record):

~/Workspace/anaconda/envs/et/lib/python3.7/site-packages/fiona/collection.py in writerecords(self, records)
    345         if self.mode not in ('a', 'w'):
    346             raise IOError("collection not open for writing")
--> 347         self.session.writerecs(records, self)
    348         self._len = self.session.get_length()
    349         self._bounds = self.session.get_extent()

fiona/ogrext.pyx in fiona.ogrext.WritingSession.writerecs()

KeyError: 'properties'

It seems that the properties key is required both in the schema and in the written data, even though the spec doesn't seem to require it. Merely using empty dicts appears to fix this issue, but Fiona probably shouldn't require these keys at all.
Operating system
Ubuntu 18.04.
Fiona and GDAL version and provenance
Fiona 1.8.6 via pip on Python 3.7.3 via conda.

Thanks @SeanDS . Features and datasets without non-geometry properties haven't been on our radar. I'm not sure if all formats allow them, but the library probably doesn't need to require them.

How should unexpected keys be handled? For example:
feature = {
    "geometry": {"type": "Point", "coordinates": [0, 0]},
    "property": {"name": "example"},  # a mistake, should be properties
}
collection.write(feature)

In the current behaviour an exception would be raised. I guess this should still raise if the feature doesn't match the properties in the schema?

@snorfalorpagus good question. The GeoJSON driver can handle extra keys in a limited way (see "NATIVE_DATA" under https://gdal.org/drivers/vector/geojson.html#open-options), but no other driver can. In fiona 2 your code won't be valid, we'll have a real Feature class with a proper constructor with specific keyword arguments. Meanwhile, for 1.8 and 1.9 let's be pragmatic: don't require properties in the schema, but do require that features match the schema. How about that?

Resolved by #848.


fix for #40 - possibility to redirect specific url

I would recommend to removed commented code from the commit and also either supply documentation or remove empty XML code doc comments

Thanks for the pull request, but unfortunately I cannot merge it. It has too many changes in one PR. Also, it is not compatible with the latest version anymore.


stuck in Cloudformtion [title]

:question: General Issue
The Question

Environment

AWS SaaS Boost Version:

Other information

Hi @pnjegan , thanks for opening this issue request! Can you provide more information about your issue? In particular:

What steps did you try? What did you expect to happen, and what happened instead?
Which CloudFormation stack are you stuck in? Is this when creating the SaaS Boost environment, onboarding a tenant, or something else?

Thanks for your participation and with your help we can work to resolve your issue as quickly as possible.

@PoeppingT , it stuck at this stage
2022-01-11 16:29:39.258  INFO  SaaSBoostInstall - [INFO] Total time: 25.676 s
2022-01-11 16:29:39.260  INFO  SaaSBoostInstall - [INFO] Finished at: 2022-01-11T16:29:39Z
2022-01-11 16:29:39.440  INFO  SaaSBoostInstall - [INFO] Final Memory: 55M/190M
2022-01-11 16:29:39.440  INFO  SaaSBoostInstall - [INFO] ------------------------------------------------------------------------
2022-01-11 16:29:39.484  INFO  SaaSBoostInstall - Uploading Lambda source package to S3 metering-billing/lambdas/target/BillingService-lambda.zip -> lambdas/BillingService-lambda.zip
2022-01-11 16:29:39.484  DEBUG SaaSBoostArtifactsBucket - Putting metering-billing/lambdas/target/BillingService-lambda.zip to Artifacts bucket: sb-test-artifacts-9581b529-db40
2022-01-11 16:29:39.677  INFO  SaaSBoostInstall - Running CloudFormation
2022-01-11 16:29:39.684  INFO  SaaSBoostInstall - createSaaSBoostStack::create stack sb-test
2022-01-11 16:29:40.177  INFO  SaaSBoostInstall - createSaaSBoostStack::stack id arn:aws:cloudformation:us-east-1:310864222925:stack/sb-test/ac7b6b10-72fb-11ec-a5e3-0e8a3c442c39

@pnjegan
There is an issue running the java project on windows os.
After building the lambda functions, on windows, it places on a path separated with "" forward slash.
While in the cloud formation template the resources search for lambda zip files with path separator "/"
So for time being do a workaround by replacing
!Sub ${LambdaSourceFolder}/
with !Sub ${LambdaSourceFolder}\
for all the files in aws-saas-boost/resources.
But for a permanent fix maybe @PoeppingT would find a way to make file separators uniform on various OS.

@aquibchiniwala , am using Amazon Linux 2 as mentioned in readme.

Still you can try the same approach @pnjegan

@pnjegan are you following the instructions in getting-started.md? What steps did you follow to see the stuck script that you saw? CloudFormation createStack can take a while to complete, how long was it stuck?

@PoeppingT , Stuck in Step 3 after running install.sh!

Log into the AWS Console and go to CloudFormation and look at the Events and Resources tab for the stack named sb-test to see if there are any errors.
If the stack sb-test is not visible, change the dropdown near the stack name filter input from Active to Failed.
You can also use the AWS CLI
aws cloudformation describe-stacks --stack-name arn:aws:cloudformation:us-east-1:310864222925:stack/sb-test/ac7b6b10-72fb-11ec-a5e3-0e8a3c442c39

@PoeppingT , LMK if any details needed!

Hi @pnjegan, on that same CloudFormation page you posted a picture for, if you scroll down on that Events page you should find an event like CREATE_FAILED, which will be tied to a specific resource and should include an error code. That will give you more information into what went wrong, and provide a pathway to fix.
With the information you have provided so far we have no way to reproduce this issue, and so no way to investigate ourselves. You say that you were running Step 3 in install.sh. Can you be more explicit: were you installing a new SaaS Boost environment? If so, which options did you select as part of install.sh? Were you using the sample java application as recommended in getting-started.md?
By the way, there are new commits in the repo since yesterday which have fixed a few bugs others have raised reports on. Please try again with the latest version of the main branch and provide further information if that fails.

@PoeppingT ,sure, let me try with the repo and update

FYI- Event failed was
Embedded stack arn:aws:cloudformation:us-east-1:310864222925:stack/sb-test-network-PNE7SZKR9Q9O/b1dd7080-72fb-11ec-98aa-12b6e64cdc09 was not successfully created: The following resource(s) failed to create: [InternetGateway, EgressVPC].
I created new VPC to be used for Cloud9

What was the underlying cause? Did you run out of VPCs? Check your number of VPCs and your service quota. Installing SaaS Boost will require you to have a free VPC slot available in your account and onboarding tenants will require additional VPCs. You will have to increase your VPC quota from the default 5 if you want to onboard more than a couple of tenants.
Go to the VPC console and view your list of current VPCs. If it is 5 and you haven't requested a quota increase, you won't be able to install SaaS Boost.
Go to the Service Quotas console and choose Amazon Virtual Private Cloud (Amazon VPC) from the dashboard. Scroll to the bottom of the list to find the current setting for the VPCs per Region quota. By default, both numbers will be 5. To increase your quota, click on the Request quota increase button and fill out the form.

@pnjegan SaaS Boost does not require a VPC with a private subnet. Have you looked into the comment above from @brtrvn ? The most common issue we see is running into VPC quota limits. Without knowing the actual errors CloudFormation gave you it will be difficult to provide useful help.

No VPC Quota issues ! error i got last week was - The following resource(s) failed to create: [InternetGateway, EgressVPC].
I may run with the latest code tomorrow and update if the same issue occurs

CloudFormation will give you a reason that those resources failed to create. For example, if a stack failed to create because two subsequent resources failed to create (as you mention) you can navigate into that stack in CloudFormation and look at the same resources tab to find those resources in particular. Thinking of it like asking "I see that the InternetGateway failed to create, but why?" If you can find the InternetGateway resource that failed to create, CloudFormation should tell you exactly why, to help you debug further.

Hey @pnjegan , it has now been three months without comment on this issue, and we are in the process of releasing v2 of SaaS Boost. If you have no other comments on this issue, I will close it within the week.


Filter vulnerabilities' list in web application

I was wondering if it is possible to filter the vulnerabilities in the web app not only be severity and status, but also by programming language, user, and security tool and file name.

hello @adhamj90 tnks for you contribution.
This is a great idea, currently this is not possible in us structure of the project, but I'll add this in us backlog for implement in the future :)


chore: use GitHub Action

Replace Travis with GitHub Action.

Thank you for your contributions, but I'm not sure I can merge this as is.

“chore: update Go version” seems fine as it is. I'd be happy to merge this.
“chore: add .gitignore” appears unnecessary. The .idea directory can be added to the global .gitignore file instead.
“chore: use GitHub Actions” I don't have experience with GitHub Actions, and this seems a bit too complex for a tool that's essentially in maintenance mode. Including a Makefile is not necessary at all.

“chore: use GitHub Actions” I don't have experience with GitHub Actions, and this seems a bit too complex for a tool that's essentially in maintenance mode. Including a Makefile is not necessary at all.

Currently, you are using Travis but Travis is dead, which means you have no CI.
Even if the project is in maintenance mode, I think a CI is always useful.
The Makefile is just a way to document the project.


fix: allow angular 5 peer dependency

Angular 5.x should work, but I don't think cdk 5.x works yet.  I plan to get that working this week.

Actually, it looks like cdk 5.x works just fine.  Thanks for the contribution!

Awesome, thanks for the quick response! 😄


Add support for Ddr5/LpDdr5 memory device types

Fix issue https://github.com/jcreekmore/dmidecode/issues/27

ldfsilva wants to merge 14 commits into jcreekmore

I'm not sure why github shows previous commits when they were already merged, I'll look this up. Let me know if you know/wish me to modify the PR @jcreekmore  and I'll do so.

Yeah, if you could rebase your branch on top of my master branch, that should cause that to go away.

rebased, looks clean now with 1 commit.


Revert #18 and #22

The new requests from #18 and #22 have been moved to the trussed-staging extension.

Don't we want to have the same tree as upstream?
Maybe renaming or current may to "old-main" and force pushing the upstream main on our main here?

We can also push tags without a branch

No, we still need https://github.com/Nitrokey/trussed/pull/19.


Narsese Syntax Review and Suggested changes

The following is a compilation of ideas for suggestion of how to improve
Narsese syntax.
Removal of unnecessary commas:
all compound-terms can be parsed without commas:
examples:
{a b c} and [a b c] can be parsed between set delimiters
(| a b c), (& a b c), (- a b), (~ a b) can be parsed between parenthesis
Also in infix notation:
(a | b), (a & b), (a - b), (a ~ b) can be parsed between parenthesis
negation is already handled this way in the current notation but no other
operators so this is inconsistent.
Truth and budget can also be parsed efficiently with the removal of commas:
Examples:
%1.0 0.9% and $0.5 0.8$ can be parsed between delimiters
There is no need for commas to appear in the syntax as the language can be
parsed efficiently without them, they are unnecessary clutter and increase
the complexity of the input language.
Multi-ops and set ops to be infix
Allow all multi-ops to be infix:
Examples:
(*, a, b) to become (a * b)
Other ops to include here would be &&, ||, |, & (for /, &/ and &| see below)
Parallel and Sequential Conjunctions
The current syntax of:
(&/, a, b, c) can be improved as follows:
(a, b, c) where commas in this case have a semantic meaning and represent
Sequential conjunction (as in Non-Axiomatic Logic - A Model of Intelligent
Reasoning). This is possible once the unnecessary use of commas is removed.
Similarly:
(&|, a, b, c) can be improved as follows:
(a; b; c)
Temporal Copulas
The current temporal copulas are not intuit on inspection as to the order of
the temporal aspect:
For example:
<A =/> B> where '/' implies future - this is somewhat arbitrary and can
easily be confused with the opposite ''
<A =+> B> is the proposed alternative copula, similarly:
<A =-> B> for retrospective, =|> seems reasonably intuitive, in my opinion
and need not be changed.
Image syntax
Again the use of '/' and '' is difficult to remember without a reasonable
degree of familiarity:
Examples:
(, R, a, _) would be improved by two changes, 1: change to a form of infix
notation and 2: use a different symbol for image to remove the confusion:
The alternative symbols suggested are:
<|  for extensional image
|>  for intensional image
the thinking behind this is that it is similar to the relational image in
formal specification such as Z
(https://staff.washington.edu/jon/z-lectures/structure.html)
(| and |) would be a closer match but that would cause difficulties from a
parsing perspective although that can be overcome if this is a preferred
symbol.
There is one additional aspect that support the above suggestions in that
the direction of the 'arrow' suggests whether it is extensional or
intensional and therefore is an aid to memory.
Examples:
(R <| a _ ) for extensional image
(R |> a _ ) for intensional image
Alternatively:
(R (| a _ ) for extensional image
(R |) a _ ) for intensional image
Infix relations
In the past I have felt this was unnecessary but given the move to build a
larger audience for Narsese and OpenNARS I have now changed my position on
this and believe infix relations would be a better approach:
Examples:
<(*, a, b) --> R> would become:
 where R takes the place of a copula for input/output purposes but
would still be represented with inheritance internally.
However:
<R --> (a * b)> would remain the same and not be allowed as infix
In the case of products with more than 2 terms I suggest the following:
<(a * b * c) --> R> becomes
Interval Notation
Predictive hypotheses quite often have the form:
<(&/, A, Interval(n)) =/> B>
I suggest the following change to temporal copulas to support this common
form more easily:
<A =n> B> where n is an integer +/-.
examples:
<A =10> B> and <A =-10> B>
The benefit is that this form is more concise and simpler to read and
understand. Again this is only at the I/O interface internally it would be
represented as:
<(A, Interval(n)) =+> B> in the new notation.
Whilst I like the idea in principle for this suggested change, I am not
entirely sold on the specific copula format, i.e. =5> which is not as clean
as a regular copula. If anyone has an alternative suggestion for this copula
that would be great.
Conclusion
These ideas have come from many sources and are not just my own. There may
be other suggestions that I am unaware of and I would be grateful of any
feedback.

<A =n> B>

We had this topic before, this is not composable!

Multi ops

(*, a, b) to become (a * b)
and products
<R --> (a * b)>
overlap in syntax with a completely different meaning. Narsese was not designed as a context specific language and this is good this way.

i reimplemented images in a slightly different way than the original design.
here are the rules
https://github.com/automenta/narchy/blob/skynet5/nal/src/main/resources/nal4.nal#L2
its just a few but it relies on some internal code and also all images appearing as subterms (not at top level) are unexpanded, when possible, during normalization.  it also uses 2 reserved terms, / and \ , which are not operators as in the original image design, but just special un-unifiable atoms.
the main difference though is shown in these tests
https://github.com/automenta/narchy/blob/skynet5/nal/src/test/java/nars/nal/nal4/NAL4Test.java#L22
          .believe("((0,1,0,1) --> bitmap)", 1.0f, 0.9f)
            .mustBelieve(CYCLES, "(1 --> (bitmap, 0,/,0,/))", 1.0f, 0.9f)
            .mustBelieve(CYCLES, "(0 --> (bitmap, /,1,/,1))", 1.0f, 0.9f);

notice what it does with the repeats.  its reversible of course. i dont know if this has any other consequences, like when images get wraped in images, or in the opposite direction.  but at the surface it seems work. i need to do more testing by porting the NAL4 test cases to this syntax.
the repeat selection could be useful for data with lots of repeats in products.  thats why i called that example bitmap because it shows how from a product containng only 0 and 1 subterms, only 2 unique image exts and 2 unique image ints would be generated

i suggest consider products as NAL0 (not NAL4), and not confuse people with the * symbol anywhere.  just plain (a, b, c, ...).  and then can be explained, along with Set extensional as theoretical foundation of non-commutive and commutive subterms, respectively, forming compounds starting in NAL1.  by the way what is the Set equivalent of * ? see it doesnt have one.


Update kusto-ingest-client-examples.md

add note due to clients confusions

@t-shanigit : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@YaelSchuster

Hi @t-shanigit  please make this PR on the private repo. You can install the SpineEdit extension to automatically redirect you to the right place.
#please-close


config task problem

Hi,author! In model config, the tasks are as follows:
tasks = [
dict(num_class=1, class_names=["car"]),
dict(num_class=2, class_names=["truck", "construction_vehicle"]),
dict(num_class=2, class_names=["bus", "trailer"]),
dict(num_class=1, class_names=["barrier"]),
dict(num_class=2, class_names=["motorcycle", "bicycle"]),
dict(num_class=2, class_names=["pedestrian", "traffic_cone"]),
]
Why do you want to set it that way, instead of directly dividing it into the following forms:
tasks = [
dict(num_class=1, class_names=["car"]),
dict(num_class=1, class_names=["construction_vehicle"]),
dict(num_class=1, class_names=[ "construction_vehicle"]),
dict(num_class=1, class_names=["bus"]),
dict(num_class=1, class_names=["trailer"]),
dict(num_class=1, class_names=["barrier"]),
dict(num_class=1, class_names=["motorcycle",]),
dict(num_class=1, class_names=[ "bicycle"]),
dict(num_class=1, class_names=["pedestrian"]),
dict(num_class=1, class_names=["traffic_cone"]),
]

each dict specifies a head and during the training the loss is only backpropagated to the specific head. Basically, if the loss is related to a "car", it will only train the "car" head.
Therefore, we want to group related objects together instead of separating them completely. This setup is from https://arxiv.org/abs/1908.09492 and det3d.


This API is only available when targeting a specific CPU architecture. AnyCPU cannot generate this API.

The majority of the SetupAPI imports are still done manually via P/Invoke since Any CPU doesn't produce them (see CsWin32 docs), will currently just result in this warning:
This API is only available when targeting a specific CPU architecture. AnyCPU cannot generate this API.

Look into building and packaging a multi-arch project and NuGet to get this resolved properly.

Looked into it further, don't really think there's an awful lot to gain in comparison to the work required, so closing for now.


feat: add initial host implementation

Please review commit-by-commit (https://github.com/wasmCloud/wasmCloud/pull/273/commits) and mind the commit messages/descriptions
Crate documentation available at https://rvolosatovs.github.io/wasmCloud/wasmcloud/index.html
This PR contains:

initial host implementation, which:

executes actors via wasmtime
implements the wasmbus FFI interface
contains built-in provider implementation adaptors for log and rand crates

CI setup for linting, testing and build of cross-compiled binaries along with OCI images containing them

Related Issues

Release Information

Consumer Impact

Testing

Built on platform(s)

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

Tested on platform(s)

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

Unit Test(s)

Yes, see tests within src/actor.rs
Acceptance or Integration

See tests
Manual Verification

Tested with a custom http-log-rng actor utilizing builtin providers and https://github.com/wasmCloud/examples/tree/main/actor/echo integrated into this repository

we're also going to want to add CI support, branch protection, etc.

we're also going to want to add CI support, branch protection, etc.

The CI is already set up as part of the PR, the checks should just be enabled in the settings

LGTM to go ahead unless @ricochet has additional thoughts

My thoughts are "LETS GOOOOOOO"

@autodidaddict should I change the target branch to main or keep it at dev?


MSBuild Import doc claims relative paths are relative to the importing project's dir, but this is not true for imports in the imported file

This paragraph is correct in some cases, but not in others:

Relative paths in imported projects are interpreted relative to the directory of the importing project. Therefore, if a project file is imported into several project files in different locations, the relative paths in the imported project file will be interpreted differently for each imported project.

This is generally true for properties and items (and I think that was the intent behind the writing because they're what people more often get tripped up by). It is incorrect for Imports within the imported project: these are actually relative to the imported project.
Example project: import-relative.zip

ImportingProject\ImportingProject.csproj -- default dotnet new console project.
ImportingProject\Program.csproj -- default dotnet new console program.
Directory.Build.targets -- targets file imported automatically by the SDK targets.

Contains <Import Project="Outside.File.targets" />

Outside.File.targets -- prints Hello World! after the Build target to prove it's imported.

dotnet build succeeds, and prints Hello World!.
If the doc were correct, <Import Project="Outside.File.targets" /> would search for the file relative to ImportingProject\ImportingProject.csproj and fail when it doesn't see ImportingProject\Outside.File.targets.
This doc caused some confusion over at https://github.com/dotnet/core-setup/pull/8785.

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

ID: af512ce8-46bd-b15a-c5a2-f8315d2b258a
Version Independent ID: e2c221b8-466f-df7f-078c-bab89be71828
Content: Import Element (MSBuild) - Visual Studio
Content Source: docs/msbuild/import-element-msbuild.md
Product: visual-studio-windows
Technology: msbuild
GitHub Login: @Mikejo5000
Microsoft Alias: mikejo

cc @Mikejo5000
maybe it should just say the "immediately importing" project? What it means by "importing project" is "the file that has the <Import element in it". But "project" generally means an entry point like a .csproj--for example, that's what you get with $(MSBuildProjectFullPath).

The way I'm understanding that suggestion, I think it'd make the item/property scenario less clear. With that wording I might expect items defined in \Outside.File.targets to be relative to the "immediately importing" \Directory.Build.targets. (If I manage to interpret "project" to mean "MSBuild file" in the first place. 😄)
I don't have a tweak in mind that can solve this... in my mental model of what MSBuild's doing, how the imports vs. items/conditions are handled are fairly separate processes that probably can't be lumped together without something being unclear.

I'm not sure I understand what you're saying about items/properties. Items can't be used in import elements. If properties are used, they're either:
a. expanded to a relative path, and that's treated as relative to the (immediately) importing project, or
b. expanded to an absolute path and that gets imported.
Maybe the tweak should be around the first part of this sentence? Maybe something along the lines of

Relative paths in the Project attribute are interpreted relative to the file that contains the Import element

And maybe also a note that this doesn't affect items?

I think you're reading this bit completely differently than I am:

Relative paths in imported projects

To me, this means "relative paths you find in an imported project", such as relative paths in properties, and in item Includes. This in my opinion it the way to read it to make the rest of the paragraph make sense:

Therefore, if a project file is imported into several project files in different locations, the relative paths in the imported project file will be interpreted differently for each imported project.

Your suggestion sounds good to me in isolation, but I don't see how it fits with the rest of the paragraph:

Relative paths in the Project attribute are interpreted relative to the file that contains the Import element

Therefore, if a project file is imported into several project files in different locations, the relative paths in the imported project file will be interpreted differently for each imported project.

(If the solution is to have two paragraphs... that would make sense to me.)

There are a few things at play here:

Properties are strings. You can use them to hold a relative path, but that's not known to MSBuild.
<Import Project="relativepath" /> is relative to the file containing the Import element.
Item Include="relativepath" are relative to the primary project ($(MSBuildProjectDirectory)).

This page was trying to get at 3, 2 was what tripped up that other PR, and 3 doesn't seem to be documented in the Items docs at all, which it probably should be.

Yep, that all matches my understanding. Thanks.

@rainersigwald Sounds like we need a minor update to the doc for point 3?

@rainersigwald What about UsingTask?

It is relative to the file in which the UsingTask appears:
https://github.com/microsoft/msbuild/blob/00781ad1353afba25451148dba61845ac139b572/src/Build/Instance/TaskRegistry.cs#L303-L304

Why was this issue closed?
The doc still makes this claim that is not correct and caused confusion:

Relative paths in imported projects are interpreted relative to the directory of the importing project.

To be specific, it is not true in this case highlighted above by @rainersigwald:

<Import Project="relativepath" /> is relative to the file containing the Import element.

The page needs to clarify that it's only trying to clarify this specific point about items:

Item Include="relativepath" are relative to the primary project ($(MSBuildProjectDirectory)).


Notes improvements (UI and Jira integration)

This PR improves few things related to notes:

Private notes are not exported to Jira (change discussed on Slack)
Jira configuration name is added to dropdown in product settings. This adds more context to the Jira configuration selection when a single Jira user is used across several Jira boards/configurations
Jira notifications in DD are updated to use the Jira configuration name instead of the Jira URL. Using the Jira URL is confusing if we have several configuration using the same Jira host.

Current accepted labels for PRs:

enhancement

When reviewing this I noticed the existing code allows for up 2000 characters as configuration name, username or password. very efficient ;-)


SearchBox Label Incorrect Positioning

The label for SearchBox shows inside the search field if using Chrome, but in Edge and IE the label is shown to the right of the input field with the icon above the text label.

Interesting... we're actually not getting that exact bug, but we're seeing that the placeholder text blocks selection of the SearchBox.
What versions of IE and Edge are you currently using?

Edge is 20.10240.16384.0
IE is 11.0.10240.16431 (also has "Update Versions: 11.0.22")

Thanks for the extra info - we'll look into this one.

Looks like this has been fixed by @wdo3650.


Use fixtures in test algo

Coverage increased (+0.05%) to 87.163% when pulling f5954469acf28d0379311135195bf7f24973bb4e on use-fixtures-in-test-algo into 5579b04095963990457cc2d75e46c71a86791fee on master.


Now target .NET Standard 1.1

Now target .NET Standard 1.1.
Removed support of .NET 4.0.
Removed old nuget builder since project now output nuget package.

Did not run tests since I use XUnit instead of NUnit.


Using version 0.6.0 for swift 2.3

Use following pod for swift 2.3
pod 'Fusuma', :git => 'https://github.com/ytakzk/Fusuma.git', :tag => '0.6.0'
Original:
pod 'Fusuma', '0.6.0'
Doesn't work =((

@almaskz it works now!


Bugs, many bugs

[x] Bullet tracers on projectile's sometimes renders twice or more (this bug appears much more often with dt and moving enemies)
[x] Bullet tracers don't have glow (a major issue)
[X] Unlocking achievements unlocks only like 5 (it should atleast unlock all milestone achievements)
[x] Recharging while charging as demoman causes you to stop instantly
[ ] Fake angles kinda teleport back like 8 ticks when moving if you have no fakelag
[ ] Rarely bullet tracers origin is like far far away
[ ] Very rarely the sticky aimbot will fail to shoot at the target (it will just shoot where your crosshair is)
[ ] Very rarely bullet tracers are inaccurate with projectiles
[ ] In rijin DT indicator the text's outline is overlapping with the border, which is more visible with colors like blue

I've came across all these bugs in 2 hours of playing
I will try to give recordings to all the glitches i've mentioned, and the config later today
Suggestion
Add ability to snap align your dt bar and other stuff so you can have it perfectly in the middle or in other postitions

Unlocking achievements unlocks only like 5

You have to run it in the main menu while not being connected to a server. It did work for me this way.

Bullet tracers on projectiles doubling - I can fix
Bullet tracers not having glow - HUGE ISSUE, MUST FIX ASAP
Fake angles kinda teleport back like 8 ticks when moving if you have no fakelag - Dunno, haven't really noticed but I know that the fake angle chams are WACKY
The Rijin DT indicator is dependent on your indicator font
Recharging while charging as demoman is because for some reason Baan thinks its cool to stop movement when recharging
Unlocking achievements - unlock in the main menu
Rarely bullet tracers origin is like far far away - honestly, haven't seen this one ever
Sticky aimbot - /shrug
Bullet tracers - /shrug
Suggeston - I did suggest this when Baan was redoing my thing in imgui to add a context menu to put something in the center, might look into it

fixed the major issue here

@canedoly what do you mean by fake angle chams teleporting by 8 ticks?

@canedoly what do you mean by fake angle chams teleporting by 8 ticks?

It's hard to explain this in words but the fake angle chams without fakelag sometimes render like 6-14 ticks behind our original position, its kinda weird I'll provide the screenshot later if I won't forget like last time
So I just tested and there are still bugs

Bullet tracers still sometimes renders twice
Bullet tracers sometimes don't even render
Bullet tracers sometimes are inaccurate asf (most often with demoman)
Bullet tracers origin sometimes is like not even close
Recharging still breaks while charging as demoman

@canedoly what do you mean by fake angle chams teleporting by 8 ticks?

It's hard to explain this in words but the fake angle chams without fakelag sometimes render like 6-14 ticks behind our original position, its kinda weird I'll provide the screenshot later if I won't forget like last time
So I just tested and there are still bugs

Bullet tracers still sometimes renders twice
Bullet tracers sometimes don't even render
Bullet tracers sometimes are inaccurate asf (most often with demoman)
Bullet tracers origin sometimes is like not even close
Recharging still breaks while charging as demoman

who

@canedoly what do you mean by fake angle chams teleporting by 8 ticks?

It's hard to explain this in words but the fake angle chams without fakelag sometimes render like 6-14 ticks behind our original position, its kinda weird I'll provide the screenshot later if I won't forget like last time
So I just tested and there are still bugs

Bullet tracers still sometimes renders twice
Bullet tracers sometimes don't even render
Bullet tracers sometimes are inaccurate asf (most often with demoman)
Bullet tracers origin sometimes is like not even close
Recharging still breaks while charging as demoman

who

me

cares

@canedoly what do you mean by fake angle chams teleporting by 8 ticks?

It's hard to explain this in words but the fake angle chams without fakelag sometimes render like 6-14 ticks behind our original position, its kinda weird I'll provide the screenshot later if I won't forget like last time
So I just tested and there are still bugs
* Bullet tracers still sometimes renders twice

* Bullet tracers sometimes don't even render

* Bullet tracers sometimes are inaccurate asf (most often with demoman)

* Bullet tracers origin sometimes is like not even close

* Recharging still breaks while charging as demoman

The bullet tracers are perfect, are you talking about the ones from projectile weapons? (They are done slightly different)

@canedoly what do you mean by fake angle chams teleporting by 8 ticks?

It's hard to explain this in words but the fake angle chams without fakelag sometimes render like 6-14 ticks behind our original position, its kinda weird I'll provide the screenshot later if I won't forget like last time
So I just tested and there are still bugs
* Bullet tracers still sometimes renders twice

* Bullet tracers sometimes don't even render

* Bullet tracers sometimes are inaccurate asf (most often with demoman)

* Bullet tracers origin sometimes is like not even close

* Recharging still breaks while charging as demoman

The bullet tracers are perfect, are you talking about the ones from projectile weapons?

Suggestion

Team based chams

Also randomly my backtrack chams went black and glow stopped working, I've tried using f_dumpmaterials but the list was so big it didn't fit in the console

this is not a problem with cuntyhack! (probably  is)

So i've found another bug

While using antiaim, and holding melee and trying to attack without aimbot, melee will just attack where the anti aim is looking.


Import IOC World Bird List

@ccicero, @dustymc, I started new imports, and will notify you for every ticket, this way it will be easier for you to see their status.
IOC World Bird List - https://www.worldbirdnames.org/ioc-lists/master-list-2/

Awesome, thanks Dmitry!

IOC World Bird List is now at resolver.globalnames.org, I will move it to index.globalnames.org as well when I renew all databases.
This resource needs some manual work, because the data are versioned, and there is no permanent 'the latest' link. I also decided to convert from Excel to CSV manually, as I need to do a bit of manual involvement anyway.
I did normalized authors accoring to the majority of authorships in GN, for example
(Baird, WM & Baird, SF, 1843) becomes (W. M. Baird & S. F. Baird, 1843)


install script failed with fish shell

https://github.com/willcrichton/flowistry/blob/1b8fedc5e288fa1a7c8c5d252369a96439e681a8/ide/src/setup.ts#L20
I just got an error that seems to stem from the install script failing in fish shell. I think || true should just ignore the value of process.env.SHELL
I'm not familiar with child_process here, but the script has a bash hashbang etc, so I'm guessing it's something about how the script is being invoked that's an issue

@deontologician can you post the full logs? If you use the "Report bug" button, it will autogenerate them for you.

Sorry, I lost it. I'll try to reproduce it

Logs

OS: linux (5.12.10-300.fc34.x86_64)
VSCode: 1.60.1
Error message
 ^

Full log: https://paste.rs/2Ki

I think this is fixed so closing for now, but please reopen if the issue persists.


Tracking issue for google/protobuf features

This is an issue to track google/protobuf features that we would like to include as soon as they are available in a release of protobuf:

[ ] Support for php_namespace option, which will allow us to generate protobuf types into the correct namespaces for google cloud (https://github.com/google/protobuf/pull/3162)
[ ] Support for fluent setters (https://github.com/google/protobuf/pull/3130)
[ ] Support protobuf extension and PHP package together (https://github.com/google/protobuf/pull/3123)

@michaelbausor is this really P1?  Or are they 'nice-to-have' enhancements.  As it happens all three PRs have merged.

@danoscarmike The php_namespace option is a big one, because once it is available, we plan to change how we distribute the protobuf types. The other two could probably be considered P2.
We should be able to close this as soon as protobuf cuts a 3.4 release. (They have released 3.4.0rc2 - so we are very close!)

@vam-google can you please review this one and close it out if done?  Thanks!

Removing priority label as this is not a bug

@michaelbausor can you please review the status of this one? Please drop grpc label if not relevant / no longer relevant.  Thanks!

These features are all supported in protobuf 3.4, so we can close this issue.


multimc: wrapQtAppsHook, add xrandr for lwjgl 2.9.2

Motivation for this change
#65399 fixed by stdenv.mkDerivation => mkDerivation as new docs require
https://github.com/LWJGL/lwjgl/issues/128 fixed by adding xrandr to PATH
cc @cleverca22
Things done

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

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

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

Builds and works fine, tested launching a vanilla 1.14 instance.
For some reason the bin folder contains some shared object files and jar files that are only used internally. Those should be moved to the appropriate directories if possible, but I can address that in a seperate PR.

Hi! :wave:
Thanks for your first contribution!
Overall, a good contribution :+1:, the only thing that I would have liked seen done differently (but still acceptable this way) is to have two commits, one for the fix for wrapping, and one for the xrandr fix. Only something to keep in for your next contributions :).

@petabyteboy you're right that those files should be somewhere else. Though yeah, that's not this PR's business. Though it does add one small hack to make the wrap hook pass.


fatal error:     could not build module 'firebase_core'

Hi @mail4shalini
When opening an issue, please try to provide all of the information indicated in the template.
Closing this issue, since no information has been provided.
Thank you.


_ is not defined

when using this as an include through bower install angular-wizard and then doing an include of dist/angular-wizard.min.js -- it will throw an error about _ not being defined.
I included lodash.underscore.min.js (from another library) to fix this, I notice it says lodash is a dependency in the README file.
But perhaps you can make this more clear in the README that you are going to need to include both lodash & the core files?

it works~!require('lodash.underscore')

The issua of lodash has been brought up several times, I plan on removing the dependency in the next push


Memory leak problem

What version of gRPC and what language are you using?
1.48 (also checked in the lastest version).
What operating system (Linux, Windows,...) and version?
Windows10 pro 21H2.
What runtime / compiler are you using (e.g. python version or version of gcc)
vc++ 2019 v16.9. (x64 build)
What did you do?
Debuging program with Dr.Memory.
What did you expect to see?
No memory leak.
What did you see instead?
Memory leak.
Found bug in source 'src\core\lib\iomgr\error.cc (line 86)'. Not released 'utf8_message' after use it.
Error 43: LEAK 65 bytes
replace_malloc
d:\a\drmemory\drmemory\common\alloc_replace.c(2580):
libRtcMgrRpc.dll!gpr_malloc
D:\grpc\v1.48.0\src\core\lib\gpr\alloc.cc(33):
libRtcMgrRpc.dll!gpr_strdup
D:\grpc\v1.48.0\src\core\lib\gpr\string.cc(48):
libRtcMgrRpc.dll!gpr_tchar_to_char
D:\grpc\v1.48.0\src\core\lib\gpr\string_util_windows.cc(63):
libRtcMgrRpc.dll!gpr_format_message
D:\grpc\v1.48.0\src\core\lib\gpr\string_util_windows.cc(77):
libRtcMgrRpc.dll!grpc_wsa_error
D:\grpc\v1.48.0\src\core\lib\iomgr\error.cc(86):
libRtcMgrRpc.dll!win_write
D:\grpc\v1.48.0\src\core\lib\iomgr\tcp_windows.cc(405):
libRtcMgrRpc.dll!grpc_endpoint_write
D:\grpc\v1.48.0\src\core\lib\iomgr\endpoint.cc(32):
libRtcMgrRpc.dll!write_action
D:\grpc\v1.48.0\src\core\ext\transport\chttp2\transport\chttp2_transport.cc(1004):
libRtcMgrRpc.dll!write_action_begin_locked
D:\grpc\v1.48.0\src\core\ext\transport\chttp2\transport\chttp2_transport.cc(966):
libRtcMgrRpc.dll!grpc_combiner_continue_exec_ctx
D:\grpc\v1.48.0\src\core\lib\iomgr\combiner.cc(259):
libRtcMgrRpc.dll!grpc_core::ExecCtx::Flush
D:\grpc\v1.48.0\src\core\lib\iomgr\exec_ctx.cc(82):
Anything else we should know about your project / environment?

Esun, can you take a look?  I suspect this problem will have gone away with your recent change to move us to absl::Status.


Website is down - HTTP ERROR 525: SSL handshake failed

Ok, it seems like website started to work now,... I don't know why it wasn't working like for 20 mniutes.


storage: ACL doesn't set properly

I'm trying to write public objects to GCS but it doesn't set the acl properly.
b := client.Bucket(bucket)
dest := b.Object(path)
acl := dest.ACL()
acl.Set(c, storage.AllUsers, storage.RoleReader)
acl.Set(c, ProjectOwners, storage.RoleOwner)
acl.Set(c, ProjectEditors, storage.RoleOwner)
acl.Set(c, ProjectViewers, storage.RoleReader)

When I check the file after it is written, this is the ACL returned by gsutil
gsutil acl get gs://bucket/path.json.gz
[
  {
    "entity": "project-owners-111",
    "projectTeam": {
      "projectNumber": "111",
      "team": "owners"
    },
    "role": "OWNER"
  },
  {
    "entity": "project-editors-111",
    "projectTeam": {
      "projectNumber": "111",
      "team": "editors"
    },
    "role": "OWNER"
  },
  {
    "entity": "project-viewers-111",
    "projectTeam": {
      "projectNumber": "111",
      "team": "viewers"
    },
    "role": "READER"
  },
  {
    "entity": "user-111",
    "entityId": "111",
    "role": "OWNER"
  }
]

It's like it completely ignored the public settings option. There aren't many docs, so maybe I'm just using it wrong, but this is how it seems like I should use it.

Two quick notes: you didn't check the error values from your Set calls, and you didn't specify what you expected to see from gsutil.

Ping, @derekperkins. Please clarify.

That's my bad for not reading the docs properly. My misconception was that I was setting them on the object handle and it was all being written out together. My workaround was to set the default bucket ACL and comment out that code. I'll try it out this weekend to see what errors are being returned.


[Feature] Support a list of relative paths por inputs.path

Is this feature missing in the latest version?

[X] I'm using the latest release

Is your feature request related to a problem? Please describe.
Not really. Trying to get certain functionality.
Describe the solution you'd like?
If possible, a list of relative paths should be allowed for inputs.path:
      - name: Get changed files
        id: changed-files
        uses: tj-actions/changed-files@v40
        with:
          path:
            - configs/
            - data/
          dir_names: "true

Describe alternatives you've considered?
Nothing really, just removing the extra changed files with some bash-fu :smi
Anything else?
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

I think it can be done with inputs.files_yaml perhaps?

Hi @tuxillo, the inputs.path is used for specifying where the clone repository is located.
To use relative paths for matching existing files or directories that is already supported.
See:  https://github.com/tj-actions/changed-files?tab=readme-ov-file#inputs- for more information.

Thanks @jackton1, this can be close then!


Defaults options and LINK_SELECTOR querySelector

Hi,
I'm playing with your lib for a Wordpress custom theme, really liking it so far!
Therefore, I had a couple of issues with my initial setup.
First thing, Wordpress will always output the full http:// URL by default (which is a good SEO practice also). Your default LINK_SELECTOR selector is targeting only relative link.
By default, the LINK_SELECTOR could check if URL is for current origin :
const domain = window.location.origin

const swup = new Swup({
    LINK_SELECTOR: `a[href*="${domain}"]:not([data-no-swup]), a[href^="/"]:not([data-no-swup]), a[href^="#"]:not([data-no-swup]), a[xlink\\:href]`,
})

Also, the class selector except the element to starts with the className, this works too :
const swup = new Swup({
    animationSelector: '[class*="a-"]',
})

It might be a little bit too loose though, any class contain this string part would be selected. The default could be something more specific to the purpose like [class*="a-transition-"].
Anyhow, this just my two cents. If you agree with this, I could fork and send a pull request.
Thanks.

Hi Thetoine,
For first question see this https://github.com/gmrchk/swup/issues/4
For second question, and also the first, you can adjust manually the default option like this:
var options = {
LINK_SELECTOR: 'a',
FORM_SELECTOR: 'form[data-swup-form]',
elements: [
'#swup'
],
animationSelector: '[class^="a-transition-"]',
cache: true,
pageClassPrefix: '',
scroll: true,
debugMode: false,
preload: true,
support: true,
disableIE: false,
skipPopStateHandling: function(event){
if (event.state && event.state.source == "swup") {
return false;
}
return true;
},
}
var swup = new Swup(options)
Hope this help

Hi @thetoine,
The LINK_SELECTOR default setting was once pointed out before. I'm all up for it.
I like the idea about animationSelector option. People are having a hard time understanding the meaning of class^=, or just miss it quite often. I was thinking about including the word swup in the selector, but I guess [class*="transition-"] would do just fine. After all, it's a setting that can be changed... It would be nice if you reflect your changes in the readme as well, but I will go through it when you're done anyway, so it's up to you.
Thanks!

just wanted to thank @thetoine  for his solution which worked great for me. Thanks!

@gmrchk sorry, I was way too busy last week on clients job. So you did the change yourself, great !

I don't mean to butt in but I like the convention of including the word swup in the animationSelector by default. I was just thinking about this as I noticed you updated the README with the latest animationSelector example.

@thetoine No worries. I was just updating the docs, so I updated the default options in a process so it all fits. Thanks for making me do so!
@dylanfisher transition-* seems pretty descriptive to me, and in case it's overlapping with some internal classes, it's still a default setting that can be changed. Any suggestion including word swup tho? I like the idea, but swup-transition-* is unnecessarily long and versions like swup-a-* seems like something that could be confusing for people.

@andre94 @thetoine
Hey guys, wanted to check in with some other people who might have implemented this in WP.
I was looking at adding a Webpack plugin for in-lining my critical path CSS, and it was not able to work because it couldn't access any HTML files. I'm wondering if that means that the preload for swup isn't going to work for wp? I'm continuing to use it because I think the animation stuff is useful but I'm curious how useful it actually is for the actual preloading of data etc. Any thoughts?


Use org.winehq.Wine

WINE Flatpak was recently released. Perhaps we can try using this one over com.fightcade.Fightcade.Wine?
I recently opened an MR[1] in the Lutris Flatpak. We could base it on that.

I don't know if it makes sense for us to track the regular Wine Flatpak; we purposely track a pretty outdated version of Wine (currently Wine 5.0.3) since that's what's recommended and tested by the Fightcade developers. From what I've seen there are usually issues with newer wine versions (for example controller support broke for a lot of people running wine 7) and I'd like to avoid the headaches of not having control of the wine version as that was one of my reasons for wanting to sandbox Fightcade in the first place.
I'm definitely open to it so long as someone can tell me what we'd realistically get out of tracking a newer wine? Wine is only really used for running FBNeo which very rarely changes so compatibility with that isn't an issue.
If anyone is interested in doing the initial work they can throw up a PR and I'd be willing to merge it into the beta branch.

I see, and I completely understand that.
My main intention (which I apologize I haven't explained earlier) is to avoid using the user's storage as much as possible. By using org.winehq.Wine, we know we are tracking a "standard" build of WINE Flatpak. By standard, I mean one that is being reused by other applications.
Flatpak deduplicates data, however it depends on the hash of each file. Let's imagine that Fightcade and Lutris use the same org.winehq.Wine Flatpak as a base application. If I install Lutris and Fightcade, they will use the exact same WINE. Since Flatpak deduplicates data, WINE won't be using twice the storage, but only once, despite two applications using it. And this gets more and more efficient the more application that require WINE are installed.
So that was the incentive goal, really.

Right, I guess I was unclear -- I understand the advantages from the Flatpak side, I was more so curious if there were advantages from the Wine side. I guess I misinterpreted your intention in opening this issue as I occasionally get requests to update org.fightcade.Fightcade.Wine to a more current version, but now I see it's from the Flatpak maintainership side.
Tracking org.winehq.Wine is still something I'd definitely consider but as mentioned this specific application (Fightcade) uses Wine to run only two binaries that don't change very often. Until Wine 5.0.3 breaks in some way I'd feel more comfortable tracking the version of Wine recommended by the upstream devs and also avoid the extra headaches that tracking a moving Wine target could cause.
I think it makes sense for the beta branch though, so if a basic PR were to be thrown up I could merge it in there. I could handle the compatibility issues (Fightcade makes a lot of assumptions about the host system and has a lot of weird hacks to get things to play together nicely in the sandbox,) I'd just need whatever the manifest changes to get org.winehq.Wine into com.fightcade.Fightcade would be.

I wonder if we can add multiple base apps. This Flatpak seems to be using the Electron one:
https://github.com/flathub/com.fightcade.Fightcade/blob/dd3b77a6ec79dfb19cb9dd55acd62b95006d79c0/com.fightcade.Fightcade.yml#L2-L3
I'll ask the Flatpak Matrix.

Yeah, that's what I wasn't sure about otherwise I would've just copied your Lutris PR. Let me know what you hear back.

Someone's response was "I don't think" and this came from a contributor. How long does it take for the Fightcade Flatpak to build usually? If the time is short, I could try it locally.

Without Wine it's about five minutes


HBASE-24121 [Authorization] ServiceAuthorizationManager isn't dynamically updatable. And it should be

JIRA link: HBASE-24121

Using HBasePolicyProvider#init instead of RpcServer#refreshAuthManager is because the former is more like a complete version, including refreshing proxy user. In the meantime, the latter synchronized again which is already done at the caller ConfigurationManager#onConfigurationChange.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 39s
Docker mode activated.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
6m 51s
the patch passed

+1 :green_heart:
compile
1m 14s
the patch passed

+1 :green_heart:
javac
1m 14s
the patch passed

+1 :green_heart:
shadedjars
6m 30s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 57s
hbase-server in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
195m 54s
hbase-server in the patch passed.

229m 58s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1439/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1439

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 132b0a8f1177 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 740e937210

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1439/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1439/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1439/1/testReport/

Max. process+thread count
3274 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1439/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

About the test, the functional test of ServiceAuthorizationManager is done in hadoop-common, and the re-config framework is also testify by many other UTs already.
WDYT.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 31s
Docker mode activated.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
7m 29s
the patch passed

+1 :green_heart:
compile
1m 13s
the patch passed

+1 :green_heart:
javac
1m 13s
the patch passed

-1 :x:
shadedjars
0m 12s
patch has 7 errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 46s
hbase-server in the patch failed.

_ Other Tests _

-1 :x:
unit
118m 56s
hbase-server in the patch failed.

140m 58s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1439/2/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1439

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 3625d1fe8736 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 62718cdb28

Default Java
2020-01-14

shadedjars
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1439/2/artifact/yetus-jdk11-hadoop3-check/output/branch-shadedjars.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1439/2/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

shadedjars
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1439/2/artifact/yetus-jdk11-hadoop3-check/output/patch-shadedjars.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1439/2/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1439/2/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1439/2/testReport/

Max. process+thread count
3395 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1439/2/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 31s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+1 :green_heart:
mvninstall
6m 17s
master passed

+1 :green_heart:
compile
1m  2s
master passed

-1 :x:
shadedjars
0m 11s
branch has 7 errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 42s
master passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
5m 43s
the patch passed

+1 :green_heart:
compile
0m 58s
the patch passed

+1 :green_heart:
javac
0m 58s
the patch passed

-1 :x:
shadedjars
0m 10s
patch has 7 errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 36s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
169m 14s
hbase-server in the patch passed.

187m 55s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1439/2/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1439

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux abc935bbbd77 4.15.0-91-generic #92-Ubuntu SMP Fri Feb 28 11:09:48 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 62718cdb28

Default Java
1.8.0_232

shadedjars
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1439/2/artifact/yetus-jdk8-hadoop2-check/output/branch-shadedjars.txt

shadedjars
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1439/2/artifact/yetus-jdk8-hadoop2-check/output/patch-shadedjars.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1439/2/testReport/

Max. process+thread count
3614 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1439/2/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

Meaning someone updates the policy.xml with a new policy, the test runs something to make sure the new policy is in affect, something along those lines.

Yeah, this is what I said, it is exactly about functionality about HDFS's  ServiceAuthorizationManager which shouldn't be tested on HBase side. Even if it doesn't take effect, we can do nothing on HBase side (BTW, it does take effect).

_ Patch Compile Tests _

-1 :x:
mvninstall
2m 48s
root in the patch failed.

-1 :x:
compile
0m 38s
hbase-server in the patch failed.

-0 :warning:
javac
0m 38s
hbase-server in the patch failed.

-1 :x:
shadedjars
3m 48s
patch has 17 errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 37s
hbase-server in the patch failed.

_ Other Tests _

-1 :x:
unit
0m 38s
hbase-server in the patch failed.

21m 16s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1439/3/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1439

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 809be8a06d48 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / eb7df0498c

Default Java
2020-01-14

mvninstall
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1439/3/artifact/yetus-jdk11-hadoop3-check/output/branch-mvninstall-root.txt

shadedjars
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1439/3/artifact/yetus-jdk11-hadoop3-check/output/branch-shadedjars.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1439/3/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

mvninstall
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1439/3/artifact/yetus-jdk11-hadoop3-check/output/patch-mvninstall-root.txt

compile
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1439/3/artifact/yetus-jdk11-hadoop3-check/output/patch-compile-hbase-server.txt

javac
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1439/3/artifact/yetus-jdk11-hadoop3-check/output/patch-compile-hbase-server.txt

shadedjars
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1439/3/artifact/yetus-jdk11-hadoop3-check/output/patch-shadedjars.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1439/3/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1439/3/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1439/3/testReport/

Max. process+thread count
100 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1439/3/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
2m  5s
Docker mode activated.

Yes, related. Just pushed a new commit. Waiting QA.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 37s
Docker mode activated.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
6m 11s
the patch passed

+1 :green_heart:
compile
1m  5s
the patch passed

+1 :green_heart:
javac
1m  5s
the patch passed

+1 :green_heart:
shadedjars
5m 28s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 42s
hbase-server in the patch failed.


[BUG] exo run receives all logs

Describe the bug
When running exo run you get all of the logs for the history of the workspace, not just the logs for the processes you just started.

Yes, it appears to still be true.
My expectation when running exo run would be that it only displays logs for the current run. I wouldn't expect it to display any historical logs. I don't necessarily have an issue with it displaying logs of old components so long as those components are actually running.


Licensing update

Up until now, this project has been made available under Creative Commons Attribution Share Alike 4.0. It's a fairly permissive license that allows a wide range of use cases, including commercial use and code modifications, provided that it retains a license and copyright notice, any code changes are clearly documented and redistribution of derivative work must be released under the same or a similar license.
However, this license was not made for software and is not recommended for that purpose. So, I am looking for another license that is more suitable for software and that keeps about the same level of freedom. Any suggestions?

Something simple, for example, MIT. choosealicense

Yeah, I always liked the conciseness of MIT license. Good idea.


Non-arabic scripts (Japanese) do not auto-populate slug

This was partially addressed in #8, but I'm evaluating wagtail for creating pages for Japan, and unfortunately django's URLify (understandably) doesn't stretch as far to include Japanese. I'm wondering what the best plan of attack is. Some ideas:

If the title is non-blank, but urlify returns a blank string, use something else?

Date?
Post ID
Configurable from settings or model

Just show a warning you need to set the slug too
Show the current slug in the main panel under the title - perhaps clicking on it could bring up the second tab and focus the slug input

I've previously used the unidecode library to produce passable ASCII representations of non-Latin text - maybe that could be used here. (I don't know how well it handles kanji in general, though - I only used it on place names. And maybe this is just pushing the problem further down the road, and eventually we'll encounter another language that unidecode can't handle...)
I guess there's no fundamental reason why slugs have to be ASCII-only - most browsers now display unicode characters in URLs quite happily - so perhaps the answer is simply to use something more permissive than django's urlify. (What do Japanese news/blog sites usually do for URLs - native script, romanized text, or avoid the issue by just using IDs?)

I've seen all 3 used before. To me, romanize versions of th Japanese titles
are the worst option - I can't see it having any SEO benefit whatsoever and
doesn't really make the URLs any more typable.
To be honest, this is something I feel might be better handled in the model
rather than on the front end. There's lots of cases where a datestamp would
be good enough or perhaps just the post's id.
Eg - if the slug is blank run generate_slug method, if that returns blank
string or none raise validation error.
Actually, using the routableurls mixin and an index page, I can see cases
where the slug is never used and the url comes from eg. The post date / ID
and lookup is ID based.
On Friday, June 26, 2015, Matt Westcott<EMAIL_ADDRESS>wrote:

I've previously used the unidecode
https://pypi.python.org/pypi/Unidecode library to produce passable
ASCII representations of non-Latin text - maybe that could be used here. (I
don't know how well it handles kanji in general, though - I only used it on
place names. And maybe this is just pushing the problem further down the
road, and eventually we'll encounter another language that unidecode can't
handle...)
I guess there's no fundamental reason why slugs have to be ASCII-only -
most browsers now display unicode characters in URLs quite happily - so
perhaps the answer is simply to use something more permissive than django's
urlify. (What do Japanese news/blog sites usually do for URLs - native
script, romanized text, or avoid the issue by just using IDs?)
—
Reply to this email directly or view it on GitHub
https://github.com/torchbox/wagtail/issues/1443#issuecomment-115623565.

A commit recently landed in Django adding support for unicode characters in SlugField: https://github.com/django/django/commit/f8cc464452f495fce2a3d6f7494396c8f798a1e6

In [2]: from demo.models import BlogPage

In [3]: BlogPage.objects.all()
Out[3]: [<BlogPage: 블로그를 열었습니다>, <BlogPage: 두 번째 블로그입니다>, <BlogPage: 세번째 블로그입니다.>]

In [4]: BlogPage.objects.all()[0]
Out[4]: <BlogPage: 블로그를 열었습니다>

In [5]: BlogPage.objects.all()[0].slug
Out[5]: 'hello'

In [6]: model_obj = BlogPage.objects.all()[0]

In [7]: model_obj.slug = "한글한글"

In [8]: model_obj.save()

In [9]: model_obj.slug
Out[9]: '한글한글'

I manually manipulated model instance's slug field with unicode string and saved it.
And the unicode slug is working well. (It will be better to write some tests for unicode slug)
But the problem is that when user types unicode string as a page's title in admin,
js automatically cleans non-ascii characters, so I am rewriting codes bellow to work well with unicode..
function cleanForSlug(val, useURLify) {
    if (URLify != undefined && useURLify !== false) { // Check to be sure that URLify function exists, and that we want to use it.
        return URLify(val, val.length);
    } else { // If not just do the "replace"
        return val.replace(/\s/g, '-').replace(/[^A-Za-z0-9\-\_]/g, '').toLowerCase();
    }
}

https://github.com/torchbox/wagtail/blob/master/wagtail/wagtailadmin/static_src/wagtailadmin/js/page-editor.js#L297-L324
Uhm.. do you think this approach is good?

@hanpama Allowing non-ASCII characters in slugs seems to be the right solution, yes. To do this, we would need to update the validation code in both Python and Javascript. In both cases, we want it to accept all characters that are considered alphanumeric in Unicode (not just A-Za-z0-9). Python has built-in support for this, but it seems that Javascript doesn't - we'd have to list all the valid character ranges, as in http://stackoverflow.com/a/22075070/1853523.
On the Python side, we would need to override the default validation on SlugField: https://docs.djangoproject.com/en/1.8/ref/forms/validation/#using-validators
(Your example above manages to bypass this validation because you're writing directly to the model, but the validation still happens at the form level.)
On the Javascript side, we'd need to update the cleanForSlug implementation. We can't use the URLify function from django.contrib.admin (because the current version in Django 1.8 is not unicode-aware, and we won't be dropping Django 1.8 support any time soon) - so we'll have to write our own replacement (including the extra functionality such as removal of stop-words), or bundle our own copy of the Django 1.9 version.

Thank you, @gasman .
I will make some updates on this issue, and send PR soon!

When closed, will the fix to this issue allow prepopulating the slug field with unicode characters if the title is contains non-Ascii unicode characters?

To allow unicode slug, we have to define a class which extends django.db.models.SlugField and replace page model's slug field with custom one. Django 1.9 supports unicode slug, so using its SlugField seems nice but backward compatibility matters.
Do you think it is a nice solution to make a new custom UnicodeSlugField? or... is there a better solution for this?

Fixed (on Django 1.9 - Django 1.8 falls back on the old behaviour) in #2396.


Túlio you deserve some credit - Request to change extension name

Hey man, great work on the tool, I tried a few different ones before deciding yours was the one to use.
Here's the problem: When I randomly see and talk to people at different places and want to tell them to check it out, I'm like "uh.., yeah.. go google Json Viewer...". Then no one can find it because there are multiple Chrome extensions with the exact same name.
So if you changed the name I think more people could appreciate your work, because it'd be easier to find and spread.  How about:  Json Viewer by Team Tulios?  I don't know, I'm not a marketing guy...any change would be fine.

Thanks, @whitneyland. It's super nice to receive some praise!
About the naming issue, when I chose this name back in 2013 there were no extensions called JSON-viewer. I think it is a very hard problem to solve, we have to move away from generic names :)


is this a drop in of ib_insync?

Hi,
i don't find any migration hints. Can i just replace ib_insync with ib_async?
Thx!
Greets

yes, just replace the old module name with the new one.
same topic in discussions

@August1328 to me this does not work.
I did:
git clone https://github.com/ib-api-reloaded/ib_async

import sys
sys.path.append(r'./ib_async/')

from ib_async import *

but this results in:
Traceback (most recent call last):
  File "/opt/metaibcopy/ib-client.py", line 11, in <module>
    import ibkr2
  File "/opt/metaibcopy/ibkr2.py", line 5, in <module>
    from ib_async import *
  File "./ib_async/ib_async/__init__.py", line 105, in <module>
    from .version import __version__, __version_info__
  File "./ib_async/ib_async/version.py", line 5, in <module>
    __version__ = version("ib_async")
  File "/usr/lib/python3.9/importlib/metadata.py", line 551, in version
    return distribution(distribution_name).version
  File "/usr/lib/python3.9/importlib/metadata.py", line 524, in distribution
    return Distribution.from_name(distribution_name)
  File "/usr/lib/python3.9/importlib/metadata.py", line 187, in from_name
    raise PackageNotFoundError(name)
importlib.metadata.PackageNotFoundError: ib_async

I am not familiar with every OS, but did you try pip install ib_async?

OK the reason is the modfied version.py - the original one worked without any pip install. I've reverted to the old version.py ;-) works now. Thanks a lot!

File "/usr/lib/python3.9/importlib/metadata.py", line 187, in from_name

Yes, very much true. The minimum Python version is now 3.10 right now and it will continue to increase over time. Python 3.9 is almost 5 years old by now :(


uv fails to install git pacakges managed by poetry

Hey Astral team!
I found an interesting behavior around installing a git based project that is managed by poetry (as opposed to any other build system).
Since the name of the project is defined under the tool.poetry section uv fails to pick it up when reading the pyproject.toml file.
I'm not sure if this is considered Poetry's fault, but pip definitely succeeds in installing this exact package. I have not checked whether this issue can be also replicated locally with a relative path package.
Many thanks 🙏
What Happens
uv fails to install a (seemingly) valid python dependency. pip successfully installs this project.
Expected Behavior
uv should install the package
Reproduction
cd $(mktemp -d)
uv venv
uv pip install -v git+https://github.com/elevenlabs/elevenlabs-python.git@6db2fdd7458ce5c7f1bbdc2c3936784f995acd44

outputs:
Using Python 3.12.5
Creating virtualenv at: .venv
Activate with: source .venv/bin/activate
DEBUG uv 0.3.1
DEBUG Searching for Python interpreter in system path
DEBUG Found `cpython-3.12.5-macos-aarch64-none` at `/private/var/folders/f0/m68x433x79n628trx7zp0x3h0000gn/T/tmp.BZTiKhI3Af/.venv/bin/python3` (virtual environment)
DEBUG Using Python 3.12.5 environment at .venv/bin/python3
DEBUG Acquired lock for `.venv`
DEBUG At least one requirement is not satisfied: git+https://github.com/elevenlabs/elevenlabs-python.git@6db2fdd7458ce5c7f1bbdc2c3936784f995acd44
DEBUG Using request timeout of 30s
DEBUG Fetching source distribution from Git: https://github.com/elevenlabs/elevenlabs-python.git
DEBUG Acquired lock for `https://github.com/elevenlabs/elevenlabs-python`
DEBUG Using existing git source `Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("github.com")), port: None, path: "/elevenlabs/elevenlabs-python.git", query: None, fragment: None }`
DEBUG Acquired lock for `/Users/soof/Library/Caches/uv/built-wheels-v3/git/8be1b43a58e07c63/6db2fdd7458ce5c7`
DEBUG No static `PKG-INFO` available for: git+https://github.com/elevenlabs/elevenlabs-python.git@6db2fdd7458ce5c7f1bbdc2c3936784f995acd44 (MissingPkgInfo)
error: Failed to extract static metadata from `pyproject.toml`
  Caused by: TOML parse error at line 31, column 2
   |
31 | [project.urls]
   |  ^^^^^^^
missing field `name`

uv --version
uv 0.3.1 (be17d132a 2024-08-21)

Platform
macOS Sonoma

We should fall back to building instead of trying to the read the metadata here, as we're doing in other cases, this is a bug.
Is there a reason you're using [project.urls] here instead of [tool.poetry.urls]?

@konstin
Thanks for the fast response :)
This is not a project I own / maintain, but an external package that is specified as a git dependency in another project.

@konstin -- I'm somewhat unsure... It is spec-incompliant. If we accept it here, we risk false negatives for other projects.

Oh right, because it's not dynamic like in the other cases.
We should change the error message with a note about the [project] table spec, maybe linking to https://packaging.python.org/en/latest/guides/writing-pyproject-toml/

The toml crate doesn't give us this information unfortunately, so we can add better context to the error message: https://github.com/toml-rs/toml/issues/778


consistent and numerical lists

The function is_consistent() doesn't ensure the input list contains just numbers. For instance, is_consistent([ [1,undef], [2,"a"] ]) is true. It ensures that if we substitute each number in the list by 1 and any other simple value by 0, all list items will be equal. The same happens with same_shape().
Some functions, like deriv(), doesn't require just list of numbers but that the list be consistent and containing just numbers. To check the later requires recursion to confirm that each individual item is a number. That is my proposal to such a test:

function is_numerical(list) =
    is_finite(list)
    || is_vector(list)
    || is_matrix(list)
    || ( is_list(list)
         && []==[for(vi=list) if(! is_numerical(vi)) 0]
       );

Note that is_numerical() doesn't ensure consistence and it is usually more expensive than the consistence test.
I will insert this definition in math.scad and the input data checks in deriv() using it.

I have found a bit faster and simpler code for is_numerical. It doesn't call other defined test functions in order to reduce the overload in input data checks.
function is_numerical(list,void=true) =
    ! is_list(list) ? is_num(0*list)
    : ( ( let(v = list*list[0]) is_num(0*(v*v)) ) // true just for vectors and matrices
        || []==[for(vi=list) if(! is_numerical(vi)) 0] );

Another useful test function is the one that approves just consistent numerical arrays. I call it is_addable, for lack of a better name, because any two of its first level entries of the array may be numerically added without a flaw:
function is_addable(list) = // consistent and numerical
    is_list_of(list,list[0])
    &&  ( ( let(v = list*list[0]) is_num(0*(v*v)) )
        || []==[for(vi=list) if(! is_numerical(vi)) 0] );

These function pass the following tests:
assert(is_numerical([]));
assert(is_addable  ([]));
assert(is_numerical([[1]]));
assert(is_addable  ([[1]]));
assert(is_numerical([[1,[]]]));
assert(is_addable  ([[1,[]]]));
assert(is_numerical([[[1],2],[[0],2]]));
assert(is_addable  ([[[1],2],[[0],2]]));
assert(is_numerical([[1,[2]],[2,[3]],[4,[4]]]));
assert(is_addable  ([[1,[2]],[2,[3]],[4,[4]]]));
assert(is_numerical([[[1],2],[[0],[]]]));
assert(! is_addable([[[1],2],[[0],[]]]));
assert(!is_numerical([[[1],2],[[0],[""]]]));
assert(! is_addable ([[[1],2],[[0],[""]]]));

Just to close this issue, Adrian's solution was simpler than the one I had proposed: change is_consistent and same_shape to approve just numerical lists:
function is_consistent(list) =
  is_list(list) && is_list_of(list, _list_pattern(list[0]));

function _list_pattern(list) =
  is_list(list)
  ? [for(entry=list) is_list(entry) ? _list_pattern(entry) : 0]
  : 0;

function same_shape(a,b) = _list_pattern(a) == b*0;

It should be noted that according to this new definition an empty list is consistent because
_list_pattern(undef)==0
is_list_of([],0)==true

I agree with this result. Does anyone disagree?
When the list is empty, list[0] is (currently) undef but _list_pattern can deal with this. If this is considered unsafe, the definition should change:
function is_consistent(list) =
  is_list(list)
  && ( len(list)==0 || is_list_of(list, _list_pattern(list[0])) );

If it is safe, is_consistent may be simplified:
function is_consistent(list) = is_list_of(list, _list_pattern(list[0]));

It's a little hard to guess what's safe at the moment, though it seems that there are some strong forces in favor of keeping list[0] always safe.
It seems to me that empty lists evaluating as consistent is reasonable.   Maybe we should assume it's safe, and make sure it's tested by the regression tests.  It'll be then easy to catch and fix it it ever becomes unsafe.

Actually even if list[0] is safe, undef*0 may not be.

Well, if undef*0 gets unsafe, a lot of our basic check functions will break:
is_finite
is_list_of
is_consistent
is_vector
is_matrix
All those functions multiply an input data by 0 to detect non numerical values, undef included.

I actually think it will be OK.  The undef may be caught earlier.   Or if not, multiplying by 0 will reveal the non-numerical values by generating an error at that point.   It's a bit unclear what will happen:  if 0*undef = undef but no error yet, and then you compare that result to 0, so undef==0...well, that may also be legal because it seemed the idea was to allow undefs to appear in conditions but only generate an error when it is "used".  It's not clear what that means exactly.

It is not so simple. An assert that the input list is a vector or a string would have to care the order of the checks:
assert( is_vector(v) || is_string(v) )
will break if v is a string. Similarly an extra care would be needed in non assert conditionals involving those functions.

No, is_vector(string) is false because is_list(string) is false---the first test in is_vector.  No problem there.
I'm really not sure that there is any problem.  It sounds like you can run 0*undef and nothing fails yet.  You can run -0==undef and that's valid.  So where will it fail?

If 0*undef does fail then there is a problem in the case where you want to allow a vector or matrix or alternatively a list containing strings or booleans.  I think it's a kind of weird case.  So in that case you'd need to test for the list of strings first, yes.
This seems like it's in the category of we'll figure it out once it arrives and we know what has actually arived.
Looks like someone commented out the is_list check in is_consistent.  I think this is resolved, at least for the present.


Ferry/jerk auton

Paths have to go back into the wing so we can shoot pieces for Ferry/Jerk autos

note to edit the ferry auto file with the new updated path sequence


Adding i686 to detected archs for jubilinux powered edison devices

This is to fix an issue with Intel Edison devices uses Jubilinux for their distribution. The debian based distro is built for i686 specifically and thus shows up with the arch of i686. Adding this into the arch detection statement so that mraa can build.

Looks good.
Could you please sign-off your commit as described in:
https://github.com/intel-iot-devkit/mraa/blob/master/CONTRIBUTING.md#code-signing

Signed-off-by: crocycroc<EMAIL_ADDRESS>

Since we moved to the Eclipse Foundation, I am going to close and reopen this MR so that the Eclipse checks can trigger

IMO, this would look a lot nicer with something like DETECTED_ARCH MATCHES "i[356]86".

Any update on this???


Add examples folder

Similar to d3fc-series/d3fc-annotation. Should re-purpose the code from scottlogic/d3fc src/indicators.

Closed with #37


Unary operator fixes

Fixes #26

@EricSmekens What is wrong with this one and it hasn't been merged? Can I help?

@LeaVerou, I was first focussing on low-impact merges to get a release version out soon.
Now I'm back from holiday I will try to release a version soon, and then to focus on PR's like this.
You can always help by checking/testing PR's and confirm them. Makes it more confident for me to merge them, as I cannot completely oversee the impact on jsep yet.

I will check the backslashes soon, if it matches esprima's output or what we can do about that.

@EricSmekens I have pulled this locally, resolved commits, and tested it. Both the jsep testsuite pass, and my own testsuite for Mavo's expression parsing (which uses jsep). Should I merge or do you want to do any more checks?

I'm fine with merging this! :)

Yay, merged!
Thank you @alexwarren!

Uh-oh, I just realized this causes a pretty serious bug.
Run this:
> jsep.addUnaryOp("not");
> jsep("notes")

Damn. Looking into it.


[NEW ICON] Terraform

Skill Name
Terraform
Why?
A high-in-demand DevOps skill, commonly used for automation of cloud infrastructure, but also has other applications, such as Kubernetes.
Reference Image

You can try https://github.com/AnoyiX/dev-icons

Why is this low priority? This is very used tool today.

I second @mjovanc's statement, Terraform is worth its own icon.

100% need this

Given the current situation, maybe OpenTofu logo would also be good?

✅ Added in de91fca307a83d75fc5b1f6ce24540454acead41!


where: 'server' -> Route not found

Hey all,
i've got a Strange Problem. Using a Simple route where: 'server' and the response is a 404 Error. Any Ideas?
Code:
Router.route('/shop/confirmPayment',
  function() {
    this.response.statusCode = 200;
    this.response.end("success");
  },
  {where: 'server'});

In what file is this code located? Please make sure it's available for the server.

Damn it, always had the router.js inside the lib Folder. This time i've used a Template and the router.js was inside the Client. Thanks a lot Batistleman!


[SPARK-38575][INFRA] Use GITHUB_REF to get the current branch

What changes were proposed in this pull request?
Current git --show-current doesn't work because we're not in a git repository when we calculate the changes we need.
Instead, this PR proposes to use GITHUB_REF environment variable to get the current branch.
Why are the changes needed?
To fix up the build. See https://github.com/apache/spark/runs/5583091595?check_suite_focus=true (branch names)
Does this PR introduce any user-facing change?
No, dev-only.
How was this patch tested?
Should monitor test.

Sorry guys for a quick merge, and many followups ... Let me merge this one to fix up.


Create evaluation criteria for Workbench messaging functionality

Conditions of Satisfaction

should accurately reflect differences between alternatives

FIrst crack at it, comments / suggestions welcome.

CriteriaID
Category
Criteria
Prioritization

C1
Cost
Product provides   good value for the cost
n/a

C2
Maintainability
Product is well   maintained / supported / and has strong community support
Should have

C3
Licensing
Product is open   source
Nice to have

C4
Functional   requirement
Integration w/   A2MS solution
Must have

C5
Functional   requirement
Private messaging   b/w individual researchers on a project team
Must have

C6
Functional   requirement
Project team   messaging (i.e., researcher can send a group message to their project team
Must have

C7
Functional   requirement
Ability for admin   to audit a researcher's messages
Should have

C8
Functional   requirement
Email notification   of new messages
Nice to have

C9
Business rule
Researchers must   be prevented from cross project messaging
Must have

C10
Business rule
Researchers must   only see messages for the project they have logged in as
Must have

Additional criteria:

C11
Technical
Product can run in   a Kubernetes / OpenShift
Must have

a few more criteria:
C12	Presentation	White labelling	Nice to have
C13	Legal	Must be compliant with privacy laws	Must have
C14	Technical	API access	Must have
C15	Functional requirement	Keeping formatting of code when copying and pasting	Nice to have
C16	Functional requirement	See presence of team members	Nice to have