Seaport 1.2 Release

Codecov Report
Base: 99.96% // Head: 100.00% // Increases project coverage by +0.03% :tada:

Coverage data is based on head (3d7bbe8) compared to base (9762f59).
Patch has no changes to coverable lines.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@             Coverage Diff             @@
##             main      #958      +/-   ##
===========================================
+ Coverage   99.96%   100.00%   +0.03%
===========================================
  Files          47        26      -21
  Lines        2661      1198    -1463
  Branches      393       132     -261
===========================================
- Hits         2660      1198    -1462
+ Partials        1         0       -1

Flag
Coverage Δ

foundry
?

production
100.00% <0.00%> (ø)

reference
?

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

Impacted Files
Coverage Δ

contracts/lib/Executor.sol
100.00% <0.00%> (ø)

contracts/lib/Verifiers.sol
100.00% <0.00%> (ø)

contracts/lib/Assertions.sol
100.00% <0.00%> (ø)

contracts/lib/AmountDeriver.sol
100.00% <0.00%> (ø)

contracts/lib/OrderCombiner.sol
100.00% <0.00%> (ø)

contracts/lib/CounterManager.sol
100.00% <0.00%> (ø)

contracts/lib/OrderFulfiller.sol
100.00% <0.00%> (ø)

contracts/lib/OrderValidator.sol
100.00% <0.00%> (ø)

contracts/lib/LowLevelHelpers.sol
100.00% <0.00%> (ø)

contracts/lib/ZoneInteraction.sol
100.00% <0.00%> (ø)

... and 30 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


web/forms: IsEmptyString() and IsNilOrEmptyString()

tests errors to see if the field was empty.

<EMAIL_ADDRESS>tagged


cannot create an object of the class tf.layers.Dense()

I want to create an object of the class tf.layers.Dense(), but don't want to do the feedforward step immediately (i.e. not tf.layers.dense(input, units)). Because I want to first declare these modules/layers in a class, and then to have several member functions apply1(x, y), apply2(x,y) to use these layers. But when I did in tensorflow tf.layers.Dense(units), it returned:
layer = tf.layers.Dense(100)
AttributeError: 'module' object has no attribute 'Dense'
How can I fix that?
Thanks

I apologize but I am having a hard time understanding what the problem is, where the problem is, and what version it affects. Please resubmit and pay attention to the issue template (https://github.com/tensorflow/tensorflow/issues/new) . Please provide all the information it asks. Thank you.
(In particular, tf.layers.Dense is not an exported symbol in TensorFlow releases 1.3 and prior. The next release will have them or you need to build from source. Hope that helps)


Failed to SignUp (An error occurred, please reload the application)

Hello,
if i want to sign up on my deployed applicaltion on K8s i get this error:

I haven't changed any vaule except the required frontUrl  and apiUrl  + i added an internal ingress on top.
Ingress looks like this:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: lago-ingress
  namespace: namespace-one
  annotations:
    kubernetes.io/ingress.class: nginx-mpls
    nginx.ingress.kubernetes.io/use-regex: "true"
spec:
  rules:
    - host: billing.ai.company.intern
      http:
        paths:
          - path: /(.*)
            pathType: ImplementationSpecific
            backend:
              service:
                name: lago-front-svc
                port:
                  number: 80
  tls:
    - hosts:
        - billing.ai.company.intern
      secretName: tls-secret

Actually you might have the same problem than me: https://github.com/getlago/lago/issues/368

@jannikstdl you also need to expose the api svc, I assume that the error you have in console is a 404?


Sync device data with Prod

Description
We would like to collect device data from prod so that we can use it to seed Training, Demo, Test, and dev1-7 databases. This data should resemble prod as closely as possible
use metabase api (https://www.metabase.com/docs/latest/api/dataset) to gather these from https://www.simplereport.gov/metabase/

setup a service account in metabase

Data to include:

device_type
specimen_type
device_specimen_type
supported_disease
device_supported_disease

add an endpoint to pull data from prod metabase, /api/device-prod-sync
endpoint only enabled with the following profile (simple-report-non-prod)
apply the profile to all envs that are not prod
wipe and reinsert the mentioned table with the data from prod

Additional Context
Acceptance Criteria

endpoint is available on lower env to seed with device data

@nathancrtr can we close this one now?


wg-outreach Meeting 2019-06-10

This is wg-outreach's regular weekly meeting with varying agenda, usually presented by wg-outreach members. Mostly meant for wg-outreach regulars, but open for anyone who'd like to contribute to AMP outreach.
Meeting date/time (UTC)
17:00 (10am PT)
Instructions for joining the meeting
Please join us on Google Meet with this link.
Agenda
Note: Add a comment on this issue to propose items for the agenda.

[@morsssss] AMP Roadshow update
[@pbakaus] wg-outreach process update
TBC

@ampproject/wg-outreach please add any agenda items for today!


Segfault on OS X 10.10.2

Nokogiri segfaults on my system. I have cross-tested nokogiri versions <IP_ADDRESS>, <IP_ADDRESS>, 1.6.5 and <IP_ADDRESS> with Ruby 1.9.3-p547, 2.0.0-p576 and 2.1.3.
The crash happens right after requiring nokogiri.
I have created https://gist.github.com/cassianoleal/bdf508d12f01a899ec6a with the stack trace and the crash report for nokogiri <IP_ADDRESS> under Ruby 2.0.0-p576.

Hi,
Generally if Ruby crashes like this, it's due to using a C extension that was compiled with different assumptions (different Ruby, different OS, different libraries, etc.). In this case, it appears that Nokogiri may have been compiled with different assumptions than it's currently running under.
 It looks like you're running 10.10.2, so I'm guessing the answer is "yes".
Does this happen if you re-install Nokogiri? I can tell you that 10.10.2 also broke some things during install-time that we haven't been able to diagnose yet (see #1235), so you may not be able to answer this question.
ccing @zenspider so he's aware.

I just confirmed that nokogiri installed fine with stock ruby on 10.10.2 (final) for me.
If there are still problems for you, we need to compare notes and see what variables are different.

This is odd.
I don't use the stock Ruby at all. I install my rubies using chruby/ruby-install. After installing 10.10.2 and seeing the segfault, I deleted all my rubies and gems and started over, but still had the segfault. After doing gem uninstall nokogiri and gem install nokogiri, the segfault was gone.
I have no explanation for that apart from that I'm sure I screwed up at some point. :)
Closing this now, thanks for your help!

On Jan 28, 2015, at 00:59, cassiano<EMAIL_ADDRESS>wrote:
I don't use the stock Ruby at all. I install my rubies using chruby/ruby-install. After installing 10.10.2 and seeing the segfault, I deleted all my rubies and gems and started over, but still had the segfault. After doing gem uninstall nokogiri and gem install nokogiri, the segfault was gone.
I have no explanation for that apart from that I'm sure I screwed up at some point.  Something, at some point, decided it was OK to only build an i386 version of... something else. It stuck around and disagreed with a new install of nokogiri upon linkage. you still had the segfault because you didn't have the new build of nokogiri and your old build had the same linkage problem the new one did. Cleaning it out and reinstalling nokogiri got everyone on 64 bit.
Knowing what that "something else" part is would be nice, but isn't necessary.
@flavorjones: we might want to update the instructions that if someone built their own ruby and gets this i386 linker error, that they'll want to rebuild their ruby at that time. It was probably linked to something on apple's side that changed architectures.

Ok... I went ahead and deleted all rubies and gems once again, then reinstalled Ruby 2.1.3 and my bundle.
Guess what? Segfault again... Now I'm at a complete loss...

Nevermind... Seems like the segfault this time was with the json gem, not nokogiri.

@flavorjones: we also might want to update the instructions and blame the json gem.

Thanks for following up, everybody. If somebody else sees this, hopefully they'll find it on the Googles and comment, and then I'll document it.


[New game]: air hockey

🎮 Game Request
Game logic and basic description:  involves simulating the movement and interactions of the puck and mallets on a table.
Point down the features
Game points: when you put the puck in goal you score
Select program in which you are contributing
GSSoC24
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @suhanibansal-05 !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

/assign

Hey @suhanibansal-05 ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


PSRO V2 rectified training(using joint) code bug

In https://github.com/deepmind/open_spiel/blob/master/open_spiel/python/algorithms/psro_v2/utils.py, function sample_random_tensor_index(probabilities_of_index_tensor) fails when running psro_v2_example.py with --rectified=True flags or any case where sample_joint. The functions could be modified into the following:
`
def sample_random_tensor_index(probabilities_of_index_tensor, shape=None):
  shape = probabilities_of_index_tensor.shape if not shape else shape
  reshaped_probas = probabilities_of_index_tensor.reshape(-1)
  num_strats = len(reshaped_probas)
  chosen_index = random_choice(num_strats, reshaped_probas)
  return np.unravel_index(chosen_index, shape)

def sample_strategy_joint(total_policies, probabilities_of_playing_policies):
  """Samples strategies given joint probabilities.
  Uses independent sampling if probs_are_marginal, and joint sampling otherwise.
  Args:
    total_policies: A list, each element a list of each player's policies.
    probabilities_of_playing_policies: This is a list of play probabilities of
    the joint policies specified by total_policies.
  Returns:
    sampled_policies: A list specifying a single sampled joint strategy.
  """
  shape = tuple([len(ele) for ele in total_policies])
  sampled_index = sample_random_tensor_index(probabilities_of_playing_policies, shape)
  sampled_policies = []
  for player in range(len(sampled_index)):
    ind = sampled_index[player]
    sampled_policies.append(total_policies[player][ind])
  return sampled_policies

`
here an extra shape is passed into sample_random_tensor_index because probabilities_of_index_tensor as a joint is a one-dimensional vector and its shape could not be used for unraveling.

Thanks @qmaai. @paulfmmuller, any ideas?

Hey @qmaai ,
Taking a look into it. Just to minimize time spent searching, do you confirm that this error pops up when running the example and setting --rectifier="rectified" ?
I don't believe it's possible to use joint probabilities for the moment in v2's example ; would you by any chance have been running v1 ? We were planning on ensuring and validating support for joint probabilities in the future, they may therefore not be too robust yet.

thank you Paul. I was using v2 with "--rectifier=rectified" flags. yup.

@qmaai did you see Paul's response that joint probabilities are not yet possible in the v2 example?
Shall we close this or is there continued work being done on it? @PaulFMMuller shall we raise an exception informing the user in this case?

Hey @qmaai ,
I ran the example with --rectifier="rectified" and didn't encounter an issue ; did you add any other flag, or do something else ?
If so, and it's not supported yet, please don't hesitate to make a contribution :)
Otherwise, if there's something I've missed, please don't hesitate to send the entire launch command so I can reproduce the bug.

Hi @qmaai just wondering if this has been resolved for you? If so I am inclined to close this issue for now. Let us know, thanks.


Convert polling stop conditions to use ObservedDigest

UI needs to convert to relying on the ObservedDigest field for polling stop conditions.
TODO: Fill in additional details

Closed by #842


MA-1113: add prop that hides time and only allows Date range

Summary
https://konghq.atlassian.net/browse/MA-1113
Adds the ability to only show the Custom (aka calendar) date range selection via the mode parameter.
Previously, whenever we had both Relative and Custom tabs, we would default to showing a calendar with time selection.
Also - we wanted to show the TZ at the end of the displayed value per https://konghq.atlassian.net/browse/MA-1009
Example
The new relativeDate mode can be seen here:
https://deploy-preview-906--kongponents.netlify.app/components/datetime-picker.html#custom-date-and-relative-time-frames

And the previous Date and Time calendar selection has now become mode="relativeDateTime":
https://deploy-preview-906--kongponents.netlify.app/components/datetime-picker.html#custom-date-time-and-relative-time-frames
PR Checklist

[ ] Does not introduce dependencies
[ ] Functional: all changes do not break existing APIs and if so, bump major version.
[ ] Tests pass: check the output of yarn test
[ ] Naming: the files and the method and prop variables use the same naming conventions as other Kongponents
[ ] Framework style: abides by the essential rules in Vue's style guide
[ ] Cleanliness: does not have formatting issues, unused code (e.g., console.logs, debugger), or leftover comments
[ ] Docs: includes a technically accurate README, uses JSDOC where appropriate

@adamdehaven addressed the comments and also added a new date-fns-tz dependency 😬  for this ticket: https://konghq.atlassian.net/browse/MA-1009
I can explain offline if need be.

@adamdehaven - The confusing comment has been updated :)


[RESOLVED] Unavailable by ICMP ping

Problem started at 00:45:16 on 2023.05.16
Problem name: Unavailable by ICMP ping
Host: ST-FG
Severity: High
Operational data: Down (0)
Original problem ID: 20664
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23133&eventid=20664

Problem has been resolved in 6m 0s at 00:51:16 on 2023.05.16
Problem name: Unavailable by ICMP ping
Host: ST-FG
Severity: High
Original problem ID: 20664


Fix unable to parse engine image with array type condition issue

Fix unable to parse engine image with array type condition issue. Use longhorn client instead.
Partial Longhorn-3470

After this fix the test still errors here, and failed at precondition
Events:
  Type     Reason              Age                   From                     Message
  ----     ------              ----                  ----                     -------
  Normal   Scheduled           6m14s                 default-scheduler        Successfully assigned default/longhorn-testvol-teqvm7-dep-76f95bbb79-pshn2 to ip-172-30-0-131
  Warning  FailedAttachVolume  5m5s (x8 over 6m13s)  attachdetach-controller  AttachVolume.Attach failed for volume "longhorn-testvol-teqvm7-pv" : rpc error: code = FailedPrecondition desc = volume longhorn-testvol-teqvm7 cannot be attached to node ip-172-30-0-131 is already attached to node ip-172-30-0-140
  Warning  FailedMount         4m11s                 kubelet                  Unable to attach or mount volumes: unmounted volumes=[volv], unattached volumes=[volv kube-api-access-l9hqc]: timed out waiting for the condition
  Warning  FailedAttachVolume  118s (x2 over 4m1s)   attachdetach-controller  AttachVolume.Attach failed for volume "longhorn-testvol-teqvm7-pv" : rpc error: code = FailedPrecondition desc = volume longhorn-testvol-teqvm7 cannot be attached to node ip-172-30-0-131 is already attached to node ip-172-30-0-98
  Warning  FailedMount         113s                  kubelet                  Unable to attach or mount volumes: unmounted volumes=[volv], unattached volumes=[kube-api-access-l9hqc volv]: timed out waiting for the condition

https://github.com/longhorn/longhorn/issues/3517#issuecomment-1046591929 cc @derekbit

Test result - https://ci.longhorn.io/job/private/job/longhorn-tests-regression/723/testReport/tests/test_recurring_job/

Found some flaky test results caused by recurring job pod force termination. Added commit in this PR to fix.
Test result - https://ci.longhorn.io/job/private/job/longhorn-tests-regression/730/

Test result - https://ci.longhorn.io/job/private/job/longhorn-tests-regression/741/

Test result - https://ci.longhorn.io/job/private/job/longhorn-tests-regression/767/testReport/tests/test_recurring_job/


OpenAPI

@Francynox No idea if interested, but since we talked about it, the Rest API + OpenAPI docs have been added. Client-sided models + sdk generation should be possible (not tested yet) with the OpenAPI definitions endpoint, similar to how the client-sided graphql code generation works.


Negative bit numbers for field

I have this addrmap:
addrmap mymap {
  reg {
    field {
    } myfld1[14:16];
    field {
    } myfld2[20];
  } myreg;
};

When I print high/msb and low/lsb for the fields I get:
myfld2 13:-6 13:-6
myfld1 16:14 16:14

It seems the problem occurs because I specify 14:16 instead of 16:14.

Good find. This was a bug in validation. Next version will flag this as a compilation error as follows:
bug103.rdl:6:7: fatal: Field 'myfld2' of width 20 infers bit range [-6:13] which extends below bit 0
    } myfld2[20];
      ^^^^^^

The way you specify bit-order of fields also determines how subsequent fields are packed. For example:
reg {
    field {} a[12:8]; // implies this reg is "lsb0" order
    field {} b[4]; // inferred as b[16:13]
} r1;

reg {
    field {} c[8:12]; // implies this reg is "msb0" order
    field {} d[4]; // inferred as b[7:4]
} r2;

This behavior is defined in the spec under clause 9.2-e:

In the mode msb0, unless bit allocation is explicitly defined, fields shall be positioned sequentially
in the order they are instantiated in a register, starting at bit regwidth-1 with no padding between
fields. (Each subsequent field’s least significant bit (LSB) shall be made equal to one (1) less than
the most significant bit (MSB) of the previous field.)

and in 10.7-b:

field_type field_instance [low:high]
implies the use of msb0 ordering

In your example, the 20-bit field myfld2 was correctly packed below myfld1, but validation did not catch that it was out of bounds.

Implemented in v1.20.0


Disabling the verify of https for load balancer domains

Problem
If you want to get an endpoint of load balancer typed service and send a HTTP request to it, you might get TLS validation problem because of your cloud provider load balancer.
Sample Error
x509: certificate is valid for *.abc.com,  not abc-foo.eu-central-1.elb.amazonaws.com. Sleeping for 10s and will try again.
Solution
http.DefaultTransport.(*http.Transport).TLSClientConfig = &tls.Config{InsecureSkipVerify: true}
best,

This PR has been superseded by https://github.com/gruntwork-io/terratest/pull/336.


fix missing route parameter flake

What happened?
TBD: @johncowen to fill this out later

Possibly fixed by https://github.com/kumahq/kuma-gui/pull/3187


Implemented array lookup in UX expressions

UX expressions now support arbitrary array lookups, e.g. {someArray[index+3]}. The same syntax can also be used with string keys, e.g {someObject[someKey]}. The lookup is fully reactive - both the collection and the key/index can change.
This PR contains:

[x] Changelog
[x] Documentation
[x] Tests

Ready for new reveiw/merge

@kusma : what's preventing merge here now?

@Duckers: See the comment I posted. There's now two "Native"-headers.


Trampoline Cloud

Grat app.  However, it would be nice if it could be used as a cloud container.
In order to do that, it should implement at least:
#71  security
#70  monitoring
#37  process API
#45  Rest API for continuos deployment

Hi @andresoviedo
Thanks for you kind words and feedback!!
However, the original goal of Trampoline is to help locally developers. Not sure if this project need to see it in a cloud level. Don't you think there are much more powerful tools released and much more mantained.
Thinking that, I would not do any security development since I guess could be really anoying to have to log in each time in a user level, taking into consideration this local app nature.
What do you think  @cforce??
Cheers

Spring boot also implements some things.  But I dont know if it implements deployment of new microservices.

Sure it does - at least for Cloud Foundry an Kubernetes, which is available
on Azure, AWS and GCE. Trampoline could run the skipper and provide UI for
the skipper rest api, that also provides oauth
Andres Oviedo<EMAIL_ADDRESS>schrieb am Mo., 13. Aug. 2018,
17:29:

Spring boot also implements some things. But I dont know if it implements
deployment of new microservices.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ErnestOrt/Trampoline/issues/72#issuecomment-412558983,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAYARpKU1kM5kGUnEgqqTunEl9umqr-Eks5uQZs9gaJpZM4V5OWj
.

I'm going to start a conversation with Skipper development group then. It could be interesting to set up a discusion and ideas exchange as well for both sides.
Have a great week!

@ErnestOrt @andresoviedo I'm late to the party here I know, but I wanted to throw in my 2 cents as a developer in the microservice/cloud native world.
When I am working locally day to day, I prefer to focus on the services themselves and be able to code and test without the complication of cloud configs, security, deployments, etc so I can turn code around quicker. I save all those bits for later as part of integration tests. This does involve me often having 10+ local services running and its a pain trying to remember whats running in what terminal, whats on which port  etc, a problem shared by most of my team until I read about trampoline. The simplicity was it's appleal and adding all the cloud based aspects of development would turn it into another feature heavy tool with too many options.
However, this is just my own personal experience and opinion, I still would agree with both top comments and I think there is value in what @andresoviedo suggested. Maybe the best approach would be to create a separate fork or project (eg. trampoline-cloud) which focuses on managing cloud based stuff and leave trampoline as a separate tool for simple local development only? Users can pick and choose then depending on their workflow needs? I know eventually I would need to use the features suggested later in my dev cycle but I like a cloud free zone to start with 😄

Personally, I love your service and it has helped a lot - For use also on older windows servers that cannot use virtualization.
There are still some corporate environments that are behind the times.
Not everyone always has access to virtualization, and hence docker/kubernities or cloud providers like azure/aws.
At one of my customers, we have windows housing containers where virtualization has been turned off for us. So, the only solutions are to manually deploy flat jars, jenkins, or to use trampoline.

@menelaosbgr Thanks for sharing your thoughts! Happy to hear it has worked for your use case :)


small patch to support another java version string for 9-internal

when building an onadata docker image, it picked up a java version which fails the logic, preventing any form uploads.

Codecov Report

Merging #436 into master will increase coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #436      +/-   ##
==========================================
+ Coverage   82.83%   82.84%   +0.01%
==========================================
  Files          23       23
  Lines        3402     3404       +2
  Branches      790      791       +1
==========================================
+ Hits         2818     2820       +2
  Misses        439      439
  Partials      145      145

Impacted Files
Coverage Δ

pyxform/validators/odk_validate/__init__.py
75.47% <100%> (+0.96%)
:arrow_up:

Continue to review full report at Codecov.

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


dead link

The link here in the main page is dead.

Thanks @dashesy - please open an issue against the influxdb.org repo, and include more details.


Improve the speed for tracking

Can you please improve the speed for tracking?
Thank you

Hi, @aalzooke Were you able to run this on your own video ? Can you tell me what did you change on the code ?


Warnings during install

After getting to the last part of the install, I get the following warnings.
I'm using Amazon Linux 2.

$ npm install
npm WARN deprecated<EMAIL_ADDRESS>🙌  Thanks for using Babel: we recommend using babel-preset-env now: please read babeljs.io/env to update!
npm WARN deprecated<EMAIL_ADDRESS>Use uuid module instead

><EMAIL_ADDRESS>prepare /home/ec2-user/workspace/ot-node
> npm run snyk-protect

><EMAIL_ADDRESS>snyk-protect /home/ec2-user/workspace/ot-node
> snyk protect

Successfully applied Snyk patches

npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

up to date in 170.072s

This seems to be due to the recent changes in npm. Try to delete package-json.lock and run npm install again. None of it will break the functionality of the code, but we will fix it in the next commit.


Old docs inaccessible

Problem description

Cannot access https://docs.docker.com/v1.12/
I also cannot see - in the current docs for a feature - the history of a feature (i.e. when it was introduced/changed). This would seem a basic requirement for an API as fluid and inconsistent as Docker's.

Problem location

I saw a problem on the following URL: https://docs.docker.com/v1.12/

Project version(s) affected

< current

Suggestions for a fix

Maintenance.

This was fixed by #1496


WIP: Default page templates

I took a stab at implementing default page templates as indicated in #1803.
What I have implemented:

There's a book-level setting to pick a default template
A new page automatically copies the template's html on creation
A new guests page also has the template applied to it
Deleted pages don't work as a template anymore
When deleting a page that is used as a default template somewhere, there's a warning on the delete confirmation screen

What I haven't fully considered or implemented yet:

Any permission/scope problems
If there's a difference in handling HTML vs. markdown templates
A better selector to pick the default template (pagination, AJAX search) like the one in the book.edit sidebar (template-manager)
Should other entities also support a default template? (User, Shelf, Chapter) If so, which one has priority when multiple default templates are chosen on different levels?
Applying a template from a URL parameter (@cod3monk and #3794)

Random small fixes I came across:

Autofocus on the name field on guest-create.blade
Template Manager: fixed cancel icon placement

If anyone with more thorough knowledge of the codebase would like to shine some light onto this PR, that would be great.

@ssddanbrown Would you mind taking a look if you find the time? Thanks.

Hi @lennertdaniels,
Sorry for my lack of response so far, I plan to review pending PRs after finishing up the next release.
I remember doing a quick scan across the PR code when opened, and from what I can remember it was all looking really good, with maybe just needing some thought into ensuring the selection is scalable/efficient. Of course I need to look into this to properly review your code and considerations.
The one bit of feedback I will provide now is to not worry about any optional sub-features at this time (query param, other entities). I prefer to keep implementation/scope narrow and only expand on proven requirement/demand, to keep the platform surface area reasonable.
Should review towards the end of the month unless things go further wrong (Current release cycle is being a challenge).

@ssddanbrown absolutely fine, take your time. I just wasn't sure wether I had to add some tag/reviewer/assignee or something  to this PR. :)
I'll take your quick feedback into consideration and work on it a little more over the coming weeks.

Hi @ssddanbrown,
I'm slowly chipping away at your remarks whenever I find some spare time :) Will update the PR in due time.
The feedback was very useful, thanks!

Hi @lennertdaniels, have you managed to make any progress on this PR? It's a feature I'd really love to have in BookStack :)

Hi @lennertdaniels,
Would you be okay for me to take this on and finish things off from this point?

@ssddanbrown please do!
I wasn't able to dedicate a lot of time to this PR, sorry. I'm excited to see this feature come alive :)

Alright, I'll assign this to take on for the next release.
Please keep your fork & branch, and this PR up and active in the meantime until this is merged.

I wasn't able to dedicate a lot of time to this PR, sorry.

No reason to be sorry, thanks for contributing and getting this started!


Scrape automation

Add script/scrape_reddit_data.py script which is a scheduled script running at 10pm CET to get post and comment information from WSB frontpage. It will initially run once to get some data. Data is saved to local folder reddit_data/
scraping_python_functions module has been updated to allow recursive crawling of comment threads with optional maximum depth.

Thanks a ton Edward!


not taking EEPROM data

When the menu item is created, the initial data is assigned to the variable. But If I try to assign an EEPROM data it's not updating, it is taking the initial data only.
If I change the value from the Menu it is updating, but if I manually update the data outside the Menu it is not taking.
This will work
For ex:
//if this is my menu Item
ItemInput("ValueA", String(valueA), inputCallback)

//Inside inputCallback
if (selectedMenu == "ValueA") {
    valueA = value.toFloat();
    Serial.println("valueA: " + String(valueA));
  }

If I try to update "valueA" outside the inputCallBack it is not working
Something like this:
void updateA() {
  valueA = 10;
  menu.show();
}

Same for EEPROM data.

Please look the answer to #9

Thank you for the reference.
I was able to change using menu.getItemAt(0)->value  = "New value"
But not with this one menu.[``your position``][``your sub position``]->value = "your new value here"
I was getting the expected a member name error, this is not allowed.

menu.getItemAt(0)->value  = "New value" is equivalent to  menu[0]->value  = "New value"
Did you try this? menu[``your position``][``your sub position``]->value = "your new value here" only works if the menu item which you want to access is in a submenu (not in the main menu).
The first index [] is for the submenu's position in the main menu and the second index [] is for the item index in the submenu.
If indeed your item is in a sub-menu, I will have a look at the implementation to see if I made some errors

menu[0]->value = "New value" works
but not menu[``your position``][``your sub position``]->value = "your new value here"
This is the error I'm getting

Try this menu[1][2].value, I think that it should work this way, because, from the code, the second operator doesn't return a pointer.

Thank you so much, this is working. I spent one week achieving this output. But I created a new library for the menu in that process : )


add issue templates

as for the issue labels, "bug" should become "qsl bug", "game issue", and "crash"


sql: Flyway support

Background: https://airtable.com/tblD3oZPLJgGhCmch/viwdV1sM5KEK2L14K/recvRLFkfHVO4jMNH
PRs:

@jordanlewis, once this work is ready for inclusion in our docs, please assign the ready label and link to any relevant PRs. Thanks!

Closing this in favor of https://github.com/cockroachdb/docs/issues/2979, where we'll create a new "third-party tools" section and call out flyway for schema migration.


Signup icon is not visible with Latest SC RC (<IP_ADDRESS>10)

Note, this work fine in RC <IP_ADDRESS>50 but not in RC <IP_ADDRESS>10
Steps to reproduce

Install starcounter RC <IP_ADDRESS>10
Install  Sign In v5.1.1 from app warehouse
Install  Website v1.0.0 from app warehouse
Install  WebsiteProvider v1.0.0 from app warehouse

Expected result
Sigin in icon in upper right corner

Actual result

Technical information
Involved apps' version
StarcounterPrefabs/Sign In v5.1.1
StarcounterPrefabs/Website v1.0.0
StarcounterPrefabs/WebsiteProvider v1.0.0

This is not reproducible with develop branches. New versions will be released soon

As far as I know It should be fixed right know. @andwah Please check and update.

Closing as not reproducible anymore


fix possible channel duplicate close problem

Fixes: #133

Problem:  The stop channel may be closed twice which will cause panic.

Solution: Wrap the stop channel to avoid duplicate closing

Test plan: None

A mutex is used to lock any stop operations, so the channel will not be closed twice.


Potentially remove internal filter_message_top_n

Maybe this is a bug somewhere in Aragorn, but sometimes the workflow is included in the call to aragorn_ranker. In that workflow is the filter_message_top_n operation, which isn't a valid operation and scorer throws a 422. I'm not sure why the workflow is included. We either need to remove this pseudo operation or find out why the workflow is being included in subservice queries.

Never mind. I saw an error from scorer and then tried to pass the response through scorer myself, but the return message from Aragorn does include the workflow to show the user what workflow was run. Though that now makes me worried that some upstream service might do some TRAPI validation (they really should) and they would end up barfing on our response. So I'm going to double down on removing it as an internal pseudo workflow operation. We either need to remove it or get filter_message_top_n into the TRAPI spec.


Feature/synchronize

To synchronize the code with our gitlab

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.yuexiang.xyx seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

It seems that there are still several conflicts.

I have resolved the conflicts accordingly.

How about remove docker_file/feratedscope_jupyterhub?


FAQs

Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description

Please describe your changes: __________________________________
Jira/GitHub Issue numbers (if any): ______________________________
Preview links/images (Internal contributors only): __________________

PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged:

[ ] Successful preview build.
[ ] Code owner review.
[ ] No merge conflicts.
[ ] Release notes/new features docs: Feature/version released to at least one prod environment.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://66218bcb2511342ab08aca48--harness-developer.netlify.app

approved from CI perspective. Please wait for approval from other writers before merging.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://66218ef4b035282adb4b8867--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://66219fd23721d63bf53dbb71--harness-developer.netlify.app

@SushrutHarness @aimurphy Are we okay to merge this? If we keep it open longer, it'll cause merge conflicts in multiple FAQ files.

@SushrutHarness @aimurphy Are we okay to merge this? If we keep it open longer, it'll cause merge conflicts in multiple FAQ files.

I am good from CI perspective

@douglas-j-bothwell Do you approve for STO?

approved from CI perspective. Please wait for approval from other writers before merging.

@aimurphy Yes, thanks. I just realized STO was here too. I added a comment for Doug's approval.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://662291583d38352f2c4cc914--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://662295a358679c2c6122a0cc--harness-developer.netlify.app

@brian-f-harness @aimurphy I tweaked the STO FAQ a little. Will approve once the preview build finishes.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://66229d334ac4fe0091b330f0--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6622a06ba81bb9008f655296--harness-developer.netlify.app


Remove the defunct "custom labware" factory reset checkbox

This checkbox is apparently defunct.

APIv1 custom labware is actually cleared by the labware calibration factory reset.
APIv2 custom labware is not persisted on the robot, so there is nothing to clear.

So it should be removed.

Re-categorized as an API because the app populates the options in this UI based on the GET /settings/reset/options endpoint


Add Run function to controller's implementation

So that users can put additional running logic in this function.

This PR does provide an empty default version of Run for *ControllerImpl. The user can leave this Run empty if no additional run steps need to be taken.

Er, I meant that instead of creating an empty implementation, we could do something similar to what we do for the "ValidateUpdate" function - where there is a base implementation in an embedded class.  That way as we add additional functions such as this one, we can automatically add defaults to the embedded struct and users won't need to update their structs with empty implementations.
I would add a new file called pkg/controller/default_fns.go with
`go
type DefaultFunctions struct {}
func (DefaultFunctions) Run(stopCh <-chan struct{}) {
// Implement any additional non-blocking run logic here
}
`
then update the controller creation code to embed an instance of that in the {{.Kind}}ControllerImpl.
then update the generated code that constructs the ControllerImpl to include an instance of the DefaultFunctions struct.
This strategy will allow us to add more functions for users to override to the controller type definition without breaking backwards compatibility (forcing users to update their controller definitions)

@louyihua I definitely appreciate the contribution, and if my suggestion is too much a of hassle I can merge your PR and do the refactoring I suggested myself :)

Seems the second CI task needs the update of master to run correctly?

@louyihua Hm I think you are right.  The second CI might be using the latest version of the libraries that is merged, not what is local.  Would be a good thing to fix :)
I will merge the PR and we can confirm.


Cyborgs do not have space movment near tiles

Description
Cyborgs lack the minor spacemovent that other entities have when near walls.
Screenshots
I curently have no momvent here dispite being surrounded by walls. Other entities will be able to move here.

Additional context
This makes it extremely cumbersome to enter space and will often times result in you getting stuck and ending your round.
Is this an intended issue because borgs lack hands?

This issue seems to have been resolved. Closing


Buttons not translatable, check for readonly property of field.

Hi,
I've added a pull request #1 to allow the following:

Translate the text shown on the buttons.
Check if the field is readonly, if so: hide the Generate button, Only activate Copy button when the field contains a value.

For context: I was using the field for generating unique coupon codes. Once generated and saved it we don't want the field to be updated again. And we have our backend in dutch ;-)

PR already merged, thanks for accepting!

Thanks for the PR. i will create a feature release now.

Realesed: v2.1


[SPARK-20468] Refactor the ALS code

What changes were proposed in this pull request?
This is a non-feature-changing refactoring of the ALS code (specifically, the org.apache.spark.ml.recommendation package), done to improve code maintainability and to add significant documentation to the existing code.  My motivation for this PR is that I've been working on an online streaming ALS implementation [SPARK-6407] (PR coming soon), and I've been refactoring the package to help me understand the existing code before adding to it.  I've also tried my best to include a fair bit of Scaladocs and inline comments where I felt they would have helped when I was reading the code.
I've done a fair bit of rebasing and sausage making to make the commits easy to follow, since no one likes to stare at a 2,700-line PR.  Please let me know if I can make anything clearer.  I'd be happy to answer any questions.
In a few places, you'll find a PLEASE_ADVISE(danielyli): tag in the code.  These are questions I had in the course of the refactoring.  I'd appreciate if the relevant folks could help me with these.  Thanks.
How was this patch tested?
As this is a non-feature-changing refactoring, existing tests were used.  All existing ALS tests pass.

Can one of the admins verify this patch?

Preparing a PR like this takes a lot of efforts. Please try to follow the guidelines in http://spark.apache.org/contributing.html. (create a jira and rename the title).
Like you said, I doubt if anyone would be able to review and confidently merge a PR of this scope. Could you please share some reasons for the refactoring or pain points of the current implementation? Then maybe we can find a way to break it down to some smaller changes. Thanks.

Hi @hhbyyh,
Thanks for the pointer.  I've created a Jira ticket and renamed this issue to reflect it.
The individual commits in this PR are written to be self-contained and clear enough to follow linearly, like sub-PRs that build upon each other.  That said, I'm happy to break them into separate PRs if that makes reviewing easier (though each PR will look more or less like an individual commit).  I'm curious what others think is the best way forward.

This is far too big -- please close it for now and lets' start on the JIRA.

Test build #3678 has started for PR 17767 at commit ac01f7c.

Test build #3678 has finished for PR 17767 at commit ac01f7c.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds no public classes.


Ionic 3 header height on IOS 10 or 11

Resources:
Before submitting an issue, please consult our troubleshooting guide (http://ionicframework.com/docs/troubleshooting/) and developer resources (http://ionicframework.com/docs/developer-resources/)
Please make sure you are posting an issue pertaining to the Ionic Framework. If you are having an issue with the Ionic Pro services (Ionic View, Ionic Deploy, etc.) please consult the Ionic Pro support portal (http://support.ionicjs.com)
Ionic version:  (check one with "x")
(For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1)
[ ] 2.x
[ x] 3.x
[ ] 4.x
I'm submitting a ...  (check one with "x")
[x ] bug report
[ ] feature request
Please do not submit support requests or "How to" questions here. Instead, please use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:

Header height changed and come more bigger on IOS 11, but on browser or ionic view is okay.
Please check the following image.
On browser or ionic view image
VS
On Real Device or simulator image
Expected behavior:

the default header height not changed
Steps to reproduce:

Related code:

<ion-header>
  <ion-navbar>
    <button ion-button menuToggle>
      <ion-icon class="icon-menu" name="menu"></ion-icon>
    </button>
    <ion-title>{{ 'home.HomePageTitle' | translate }}</ion-title>
  </ion-navbar>
</ion-header>

Other information:

Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
cli packages: (#\AppData\Roaming\npm\node_modules)

    @ionic/cli-utils  : 1.10.2
    ionic (Ionic CLI) : 3.10.3

global packages:

    Cordova CLI : 7.0.1

local packages:

    @ionic/app-scripts : 1.3.0
    Cordova Platforms  : android 6.2.3 ios 4.4.0
    Ionic Framework    : ionic-angular 3.0.1

System:

    Node : v6.10.3
    npm  : 3.10.10
    OS   : Windows 10

Hello! Thank you for opening an issue with us!
Your Ionic Framework version (3.0.1) is fairly old. The current version is 3.6.1 with 3.7.0 hopefully being released soon. Please let me know if this is still an issue with the newer versions.
Also, for iOS 11, be sure to apply the changes mentioned here: https://blog.ionic.io/ios-11-checklist/
Thank you for using Ionic

@kensodemann I updated the ionic framework to the last version now.
Now after update I got this issue and I can't test my app, When I run my app in the real device I got white screen after splash screen and never go to the home page.
have any idea why ?

@ionic/cli-utils  : 1.12.0
ionic (Ionic CLI) : 3.12.0
global packages:
cordova (Cordova CLI) : 7.0.1

local packages:
@ionic/app-scripts : 2.1.4
Cordova Platforms  : android 6.2.3 ios 4.4.0
Ionic Framework    : ionic-angular 3.6.1

System:
Node : v6.10.3
npm  : 3.10.10
OS   : Windows 10

Misc:
backend : legacy

@kensodemann I solved the white screen issue, because I add viewport in the meta tag in the index.html file.
<meta name="viewport" content="viewport-fit=cover, width=device-width, initial-scale=1.0, minimum-scale=1.0, maximum-scale=1.0, user-scalable=no">
Anyway, what happen is!  If I put the viewport in the meta tag the app header gonna fixed and perfect in the simulator but when I try it on the real device it'll show white screen.
If I remove this viewport from the meta tag, it'll work in the real device normaly but the header issue will still exist like before.

Adding viewport-fit=cover should not be an issue. I added that to my viewport meta object in several apps and they run fine on sims and on my iPhone. It must be something else.
Can you duplicate this using a sample project and then share that sample via GitHub?

I created the sample project using ionic-start command and still issue the same.

I run it on the real device ( given me white screen with loading long time ).
I tried remove view-fit=cover from the meta tag it's work fine on the real device but the header issue still exist.

Check the project on the GitHub Ionic-Test
My device information : iPhone 6s with IOS11
Use Xcode 9

ohameds-iMac:MyTest mohamedqasem$ ionic info
cli packages: (/usr/local/lib/node_modules)
@ionic/cli-utils  : 1.12.0
ionic (Ionic CLI) : 3.12.0

global packages:
cordova (Cordova CLI) : 7.0.1

local packages:
@ionic/app-scripts : 2.1.4
Cordova Platforms  : ios 4.4.0
Ionic Framework    : ionic-angular 3.6.1

System:
ios-deploy : 1.9.2
Node       : v6.11.3
npm        : 5.4.2
OS         : macOS Sierra
Xcode      : Xcode 9.0 Build version 9A235

Misc:
backend : pro

I tried use --prod in the sample and work fine but with header issue
Anyway on my application still
with view-fit=cover --> White screen
without view-fit=cover --> Normal with header issue

I have tried your sample and it works just fine on a sim and on my device. I am also using XCode 9 for the build. My device is an iPhone 7 with iOS 11.0.1 installed.
How are you building for iOS? Your ionic info states you are using Windows 10? Perhaps there is something odd with your build system?

I'm using MAC VM.
My project was built in Windows 10, then I transfer the project to the MAC VM to build it for iOS.
The test sample was built in the MAC vm and work fine but still the header issue exist.

This sounds to me like the same same issue I'm seeing as well, and also sounds like the same thing as issue #13010 .
When the viewport-fit=cover is added, I get the extra padding around my content areas, but without it, I get white bars above and below my app on iOS.

Actually, you two sound like you are saying the opposite of each other.
@mqasem92 says:
with viewport-fit=cover --> White screen
without viewport-fit=cover --> Normal with header issue
@uniphonic says:
When the viewport-fit=cover is added, I get the extra padding around my content areas
without it, I get white bars above and below my app on iOS
Also, @mqasem92 says "white screen" which I assume to mean a totally blank screen
Also, @mqasem92 is seeing different results on a sim than on a regular device. Are you as well @uniphonic?

@mqasem92 your sample app is working fine on my device (iPhone 7 iOS 11) when viewport-fit=cover.
When you say you get a "white screen" with viewport-fit=cover on your device, does that mean a total white screen?
Without viewport-fit=cover, I get the same issue as you, but that is expected. You should be using viewport-fit=cover, so let's not worry about that case.
Looking at your app sample app, it does not appear that you have followed the instructions that are here: https://blog.ionic.io/ios-11-checklist/ (which have changed a bit since this morning's release of 3.7.0), but that is mostly a big deal when running on an iPhone X.
When I apply the stuff from the blog, including 3.7.0, then I get the issue outlined in #13010.

@kensodemann Omg !!!!
can't believe !!
Finally it's working now and the header design issue solved too !!
Anyway, All what I did the follow all steps here https://blog.ionic.io/ios-11-checklist/
and I missing make ionic-angular updated after update ionic framework .. using the following command.

npm install -g ionic@latest
npm install<EMAIL_ADDRESS>--save
npm install<EMAIL_ADDRESS>--save-dev
npm install<EMAIL_ADDRESS>--save
npm install<EMAIL_ADDRESS>--save
npm install<EMAIL_ADDRESS>--save
npm install<EMAIL_ADDRESS>--save
npm install<EMAIL_ADDRESS>--save
npm install<EMAIL_ADDRESS>--save
npm install<EMAIL_ADDRESS>--save
npm install<EMAIL_ADDRESS>--save
npm install<EMAIL_ADDRESS>--save
npm install<EMAIL_ADDRESS>--save

Also, I added WKWebView using instruction here readme
And then it show me error when I trying to build about the app-script, I type the following command.

npm install @ionic/app-scripts@latest

Thanks man.


[Date] [Time] Picker Feature Request

Hi, as suggested by @jolic here, I would like to start a PR for the material design pickers.
But before that I have some questions:

Although the component is not available in mdl but it would be a really nice addition to react-mdl. There is already a PR on mdl repo for the component so why not add it to react-mdl as well? :smile:
Should there be two PRs for the two components?
Any more things I should be aware of before starting the PRs
If I can and should start the PR?

I would be using https://github.com/puranjayjain/md-date-time-picker as a starting point and for api.(but suggestions are welcome)

I believe MDL will soon have a date time picker. See https://github.com/google/material-design-lite/pull/4187
Once it gets merged (or even before), someone can help me implementing it for react-mdl ;)

Seems MDL is not getting date time picker. Should this issue get unblocked?

MDL is progressively getting deprecated so, it's better to look for the new React-MDC library that @idancali is planning to create.
Also watch this https://github.com/material-components/material-components-web/issues/54

@tleunen , I didn't find React-MDC in @idancali's repos, but I did find react-mdc by @haoxins. I believe this npm package is directly related to that repo.
Is that what I should be looking into?
If I understood correctly, I can't use material-components-web directly in react, since they aren't react components.


BLE GATT Server ask for pairing

When trying to connect to the server hosted on an Android device, it opens a pairing request on both server and client.
The service and advertising looks like this:
 await BlePeripheral.addService(
        BleService(
          uuid: serviceTicketing,
          primary: true,
          characteristics: [
            BleCharacteristic(
              uuid: characteristicTicketing,
              properties: [
                CharacteristicProperties.write.index,
              ],
              value: null,
              permissions: [AttributePermissions.writeable.index],
            ),
          ],
        ),
      );

      /// set callback for advertising state
      BlePeripheral.setAdvertisingStatusUpdateCallback(
          (bool advertising, String? error) {
        print("AdvertisingStatus: $advertising Error $error");
      });

      BlePeripheral.setWriteRequestCallback(
          (deviceId, characteristicId, offset, value) {
        print(
            "WriteRequest: $deviceId ${String.fromCharCodes(value?.toList() ?? [])} : $offset : $value ");

        final userId = String.fromCharCodes(value?.toList() ?? []);

        if (userId.isNotEmpty) {
          addUserId(userId);
        }

        return null;
      });

      // Start advertising
      await BlePeripheral.startAdvertising(
        services: [serviceTicketing],
        localName: "ticketing",
      );

@GurgenHOVH yes android will try to pair if any device will try to connect,
if you think your use case does not requires pairing on android, you can try to replace [this] code, and check if it still works for you without bonding
BluetoothProfile.STATE_CONNECTED -> {
                            handler?.post {
                                gattServer?.connect(device, true)
                            }
                            synchronized(bluetoothDevicesMap) {
                                bluetoothDevicesMap.put(
                                    device.address,
                                    device
                                )
                            }
                        onConnectionUpdate(device, status, newState)
                    }

Thanks @rohitsangwan01 for the quick reply. Will try and update here tomorrow.

Hi @rohitsangwan01 . The code you have provided works. Would be great to turn this into a setting and update the package. Thanks!

@gurgenAya not sure if you are using any encrypted Char which causes Pairing request, or maybe thats the default android behaviour, but now that you have removed the pairing code from the native part, that program should not be responsible for making pair requests, you can cross check with Nrf Connect app maybe, in NrfConnect you can create a GattServer, and then try to see if that also makes any pairing request

Hi @rohitsangwan01 . The code you have provided works. Would be great to turn this into a setting and update the package. Thanks!

Sure, maybe will  add this as an optional setting to StartScan in next update


Clearing All data do a conflict with nativescrip-ios-uuid !

Hi @EddyVerbruggen,
I remarque since a few days that the uuid on ios change for each install ! do you think this happen because the plugin clear all data about app ?
here is the source code of nativescript-ios-uuid :
function getUUID() {
    var appName = NSBundle.mainBundle.infoDictionary.objectForKey(kCFBundleNameKey);
    var strApplicationUUID = SSKeychain.passwordForServiceAccount(appName, "incoding");
    if (!strApplicationUUID){
        strApplicationUUID = UIDevice.currentDevice.identifierForVendor.UUIDString;
        SSKeychain.setPasswordForServiceAccount(strApplicationUUID, appName, "incoding");
    }

    return strApplicationUUID;
}
exports.getUUID = getUUID;

``
`

Hi @kefahB, using the 'remove all' feature will wipe all data from the keychain (related to your app), so with the above snippet in mind it will also clear the uuid.
Did you try passing in a service property when interacting with this plugin? That may prevent this issue.


Add service_template_ansible_tower factory, inherit naming from parent

This is necessary for https://github.com/ManageIQ/manageiq/pull/18464 to pass because we only apparently have https://github.com/ManageIQ/manageiq/blob/gaprindashvili/spec/factories/service_template_ansible_tower.rb on g, and we have specs on master using that factory that's deleted. Don't ask me how that works.
We should also be inheriting the naming of these from the parent because we validate that they all have names, so I've no idea why it was written to only have the naming set on a couple to start with.
Related to
https://github.com/ManageIQ/manageiq/pull/18464

@miq-bot assign @gmcculloug
@miq-bot add_reviewer @bdunne

@mkanoor @bzwei @tinaafitz are you all okay with this?

Honestly, what am I supposed to label this?
@miq-bot add_label test
Because this factory was deleted after gaprindashvili, does this count as a bug?

@bdunne
we still use binary blobs in specs, too.
spec/models/miq_task/purging_spec.rb:14:          FactoryBot.create(:binary_blob, :name => "recent", :resource_type => 'MiqTask', :resource_id => @new_task.id)

Unnecessary factories were removed in favor of https://github.com/ManageIQ/manageiq/blob/cdfb8d6e209d42f3cb1976267b4a501b0aaa4775/spec/support/missing_factory_helper.rb so you can still use FactoryGirl.build or create on anything, but it will call new or create! on the class.


Create orders command

Users needs to create buy and sell orders, for this we need to create a new command neworder.
This command receive this arguments:

kind: which have only two possible values buy or sell
amount: Sats amount, it can receive a single positive number and also can be a range order min-max i.g.: 10-50
fiatamt: Fiat currency amount
fiatcurrency: Fiat currency (everything that is not bitcoin is fiat)
paymentmethod: This is the way how users will send fiat money
prime: Prime or discount, this is optional, default: 0
buyerinvoice: Lightning network invoice to receive sats, this is only required if the kind is buy, mostro can receive amountless invoices but if the invoice have amount it must be equal to amount.

After receive this arguments the cli will create a JSON-serialized string (with no white space or line breaks) of the following structure:
{
  "version": "0",
  "action": "Order",
  "content": {
    "Order": {
      "kind": "Buy",
      "status":"Pending",
      "amount": 4000,
      "fiat_code": "EUR",
      "fiat_amount": 1,
      "payment_method": "bank transfer",
      "prime": 0,
      "buyer_invoice": "lnbcrt1p3l7j0kpp5v8fuqtc6d6v580ezzdhwk63z72f50vlv7pd0lyka6pwl4wzc4rwqdqqcqzpgxqyz5vqsp58lmpa4m77nh2sf6wxjaafdjy9xqru6cgd6nnfs36rdv5nlv97jjq9qyyssqluj83p47c6k87awd57f9hpqw4jvz0sav77c5wkcpw3dw2zp9yvjzvrldxn2fwr0gpzggcusekwer624uxdjl8yvu6kdd9m6wa5vr0pspfq05mm"
    }
  }
}

Then sends an encrypted message to mostro's pubkey with the json encrypted as content:
{
  "id": "8af95e0ae6dcf65505474ea8885b3f2eb46c1f094f06339f76c711af43a2242d",
  "kind": 4,
  "pubkey": "f6c63403def1642b0980c42221f1649cdc33d01ce4156c93f6e1607f3e854c92",
  "content": "base64encoded-encrypted-invoice",
  "tags": [
    ["p", "7590450f6b4d2c6793cacc8c0894e2c6bd2e8a83894912e79335f8f98436d2d8"]
  ],
  "created_at":<PHONE_NUMBER>,
  "sig": "a21eb195fe418613aa9a3a8a78039b090e50dc3f9fb06b0f3fe41c63221adc073a9317a1f28d9db843a43c28d860ba173b70132ca85b0e706f6487d43a57ee82"
}

closing this issue by PR #16


[⭐FR] add option to efault to "all" search instead of "pinned"

Describe your suggested feature
Currently it defaults to only searching pinned sources every time you open the global search, so it would be nice if you could add the option to disable this and set the default search to "all" instead.
TachiJ2k has this option, but without the "pinned", "all" and "has results" buttons on the search screen.
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with an official extension, I should be opening an issue in the extensions repository.
[X] I have updated the app to version <IP_ADDRESS>.
[X] I will fill out all of the requested information in this form.

Yeah, this was the previous behaviour, now the pinning system has forced an extra button press to get this behaviour back unless you just pin all the sources which renders pinning pointless. Would be nice to have this as an option – also perhaps an option for defaulting to only showing those which have results now that's an option.

Seriously, why is this still a thiing? Pinned filter should not be default. Trash.

Pin the sources you want to do a global search on.

Pin the sources you want to do a global search on.

So just pin everything if you want to default search every source and make pinning pointless to begin with?

That's one way to use it, but not everyone will use it that way and those will benefit from the separation between pinned and all.


Language Server cannot start with local LuaRocks installation

After manually installing the extension I discovered that the language server doesn't start up correctly if the tl package is installed to the local LuaRocks tree via luarocks install --local tl. Instead, it fails with the following reason:
[Info  - 5:19:27 PM] Connection to server got closed. Server will restart.
events.js:177
      throw er; // Unhandled 'error' event
      ^

Error: spawn tl ENOENT
    at Process.ChildProcess._handle.onexit (internal/child_process.js:264:19)
    at onErrorNT (internal/child_process.js:456:16)
    at processTicksAndRejections (internal/process/task_queues.js:84:9)
Emitted 'error' event at:
    at Process.ChildProcess._handle.onexit (internal/child_process.js:270:12)
    at onErrorNT (internal/child_process.js:456:16)
    at processTicksAndRejections (internal/process/task_queues.js:84:9) {
  errno: 'ENOENT',
  code: 'ENOENT',
  syscall: 'spawn tl',
  path: 'tl',
  spawnargs: [ 'check', '/tmp/tmp-320698azbtbUp7T3xE' ]
}
[Error - 5:19:27 PM] Connection to server got closed. Server will not be restarted.

Installing tl globally via sudo luarocks install tl solves the problem.

Sorry, my network did something really weird and submitted the issue twice. Closing this one.


Change User resource id from username to email.

Reason is that GCP Cloud Composer changes username upon first
user login. This makes Terraform think that the user has been
deleted. An Airflow user is not only unique by its username but
also e-mail. So changing the Terraform user id to e-mail fixes
is safe.
note: I don't have any prior Go experience so excuse me for any non-idiomatic Go use. Happy to update!

yeah ive looked into this a bit, im not sure about this change. i think it might be easier to do some kind of state check and suppress diff (if new user value is email ). let me try to test this on the side.

DJLemkes would you care to rebase, i would like to look into this


Add pyenv snake emoji in venv

Issue
add the same green snake emoji from pyenv in venv
Screenshot

Environment
Spaceship version: 3.0.2
Zsh version: 5.2
Zsh framework: oh-my-zsh
Zsh plugin manager: None
Terminal emulator: Gnome-Terminal
Operating system: GNU/Linux Ubuntu 17.10
Relevant .zshrc

Please, can anyone explain why we should change snake (the symbol of Python) to confusing 🅿? As I know virtualenv can be used not only with Python. In another hand, pyenv is used only with Python.
Moreover, moving 🐍 to indicate another section might cause confusions for users.
I'm against this change. This will lead to breaking changes in UX, which is user unfriendly.

Could you explain where virtualenv is used other than python? Just curious.

@denysdovhan Would you be open to a patch which adds a PYTHON_VENV_SYMBOL variable, defaulting to nothing? That way current behaviour would be preserved, but people could configure as they see fit.

Could you explain where virtualenv is used other than python?

@SanketDG I cannot explain it because I'm not working with this tool. However, my ex-coworker had told me about how he used virtualenv for Ruby development.
Anyway, I think I've explained the reason about UI-inconsistency pretty clear.

@JonyEpsilon, I'd open to add a SPACESHIP_VENV_SYMBOL option default to nothing or to the corresponding icon. That would be more consistent. In that case, @SanketDG will be able to switch icons between sections.


Update to LmP v84.

Updated the boot.cmd for imx8mmevk to select SD card.

@petedyerarm  - i.mx8 build seems to have failed.

The patch is no longer required, but I didn't remove it.
In fact the patch and the bbappend that brings it in are no longer required.
Fix on it's way.


feat: entity index

Add index support for entities. Also upgraded ts-jest (they don't support semantic versioning and the latest version is the first that supports typescript 5).
const myEntity = entity("myEntity", {
    attributes: {
       pk: z.string(),
       pk2: z.string(),
       field1: z.number(),
       field2: z.number(),
    },
    partition: ["pk", "pk2"]
});

// create a GSI with pk as the only key part.
const index1 = myEntity.index("index1", {
    partition: ["pk1"]
});

// create a GSI with the original partition key [pk, pk2]
// NOTE: tables without a sort key cannot have LSIs
const index2 = myEntity.index("index2", {
    sort: ["field1"]
});

// create a GSI with the partition key [pk], ordered by field1
const index3 = myEntity.index("index3", {
    partition: ["pk1"],
    sort: ["field1"]
});

const myEntity = entity("myEntity", {
    attributes: {
       pk: z.string(),
       pk2: z.string(),
       field1: z.number(),
       field2: z.number(),
    },
    partition: ["pk", "pk2"],
    sort: ["field1"]
});

// create a GSI with pk as the only key part.
const index1 = myEntity.index("index1", {
    partition: ["pk1"]
});

// create a LSI with the original partition key [pk, pk2]
const index2 = myEntity.index("index2", {
    sort: ["field1"]
});

// create a GSI with the partition key [pk], ordered by field1
const index3 = myEntity.index("index3", {
    partition: ["pk1"],
    sort: ["field1"]
});

Do we differentiate between GSI and LSI? Is that implicit based on key or explicit?

Do we differentiate between GSI and LSI? Is that implicit based on key or explicit?

Oh never mind, lol, it's in the description


[BLOCKED] Error when creating a datastore in regions other than global

Scrapi tool to create datastore with global as region works but not for other regions.
Expected Behavior
Should create a datastore in us region
Current Behavior
InvalidArgument: 400 Location must be "global", got "us".
Possible Solution
Should create a datastore in region given by caller.
Steps to Reproduce

Follow the code in go/scrapi-data-stores
just change location to us

Detailed Description
Trying Vertex Search and Conversation features with scrapi tool.

Quick Update:
I've identified the issue is on the Discovery Engine API side, not with SCRAPI.
The API is blocking any value other than global, which means it will fail when you try us.
I've filed a bug internally for the issue.
We'll keep this item open for now and track it, but there's no action item on our side for now, and that means unfortunately any users wishing to take this action via API are blocked.


tools: add buf as better alternative of grpcurl

Motivation: https://buf.build/blog/buf-curl.
Sources:

https://github.com/bufbuild/buf
bufbuild/buf/buf

Read also https://www.fullstory.com/blog/tale-of-grpcurl/.


Skype: Not able to send file attachment to user OR Hyperlink url of file location

I have a requirement for the Bot to send a file as a downloadable to the users in Skype. The files are in physical path.
The below mentioned is the code
public async Task SelectedOptionAsync(IDialogContext context, IAwaitable argument)
{
var message = await argument;
var replyMessage = context.MakeMessage();
Attachment attachment = null;
attachment = GetLocalAttachment();
replyMessage.Attachments = new List { attachment };
await context.PostAsync(replyMessage);
await this.DisplayOptionsAsync(context);
}
private static Attachment GetLocalAttachment()
{
var Path = HttpContext.Current.Server.MapPath("~/images/demo.pdf");
var pdfdata = Convert.ToBase64String(File.ReadAllBytes(Path));
return new Attachment
{
Name = "demo.pdf",
ContentType = "application/pdf",
ContentUrl = $"data:application/pdf;base64,{pdfdata}"
};
}
In the above code i am trying to attach the contents of the file in the Message attachment. When I checked the Skype Channel, it displays "MIME type is Invalid"
I am using  Skype Client (desktop application)
Version: <IP_ADDRESS> & <IP_ADDRESS>
Note: This is working in the Emulator & I am not using Skype for Business. Also I am aware that this functionality does not work in the Skype for Business.  -->

Also I need to send the location of the file as Hyperlink URL to the user. Currently we were only able to send as String and not as a URL.

Please help us out which solution to overcome these issues.

please provide details

Hi Jason,
Please find the details below,
I have a requirement for the Bot to send a file as a downloadable to the users in Skype. The files are in physical path.
The below mentioned is the code
public async Task SelectedOptionAsync(IDialogContext context, IAwaitable argument)
{
var message = await argument;
var replyMessage = context.MakeMessage();
Attachment attachment = null;
attachment = GetLocalAttachment();
replyMessage.Attachments = new List { attachment };
await context.PostAsync(replyMessage);
await this.DisplayOptionsAsync(context);
}
private static Attachment GetLocalAttachment()
{
var Path = HttpContext.Current.Server.MapPath("~/images/demo.pdf");
var pdfdata = Convert.ToBase64String(File.ReadAllBytes(Path));
return new Attachment
{
Name = "demo.pdf",
ContentType = "application/pdf",
ContentUrl = $"data:application/pdf;base64,{pdfdata}"
};
}
In the above code i am trying to attach the contents of the file in the Message attachment. When I checked the Skype Channel, it displays "MIME type is Invalid"
I am using  Skype Client (desktop application)
Version: <IP_ADDRESS> & <IP_ADDRESS>
Note: This is working in the Emulator & I am not using Skype for Business. Also I am aware that this functionality does not work in the Skype for Business.  -->

Also I need to send the location of the file as Hyperlink URL to the user. Currently we were only able to send as String and not as a URL.

Please help us out which solution to overcome these issues.


Proposal: When lint no-supported file, show warning message

When lint no-supported file, textlint is ended silently.
$ textlint file.not-supported-ext

We want to improve this behavior.
$ textlint file.not-supported-ext
Warning: ".not-supported-ext" file format is not supported

But, this change is a bit breaking.
After included this change, You want to supress this message, please use --quiet option
$ textlint --quiet file.not-supported-ext

ESLint related:

https://github.com/eslint/eslint/issues/7390
https://github.com/eslint/eslint/pull/7395


ci: don't override nixpkgs version (use the lock file's version)

This should avoid surprises like martinvonz/jj#299, I hope.

Thanks! (This thanks supersedes https://github.com/martinvonz/jj/pull/300#pullrequestreview-963750363)


Use short CONTRIBUTING.md instead of HACKING.md

Only the most important parts and some new guidelines in CONTRIBUTING.md.
Complete HACKING.md content moved to the GitHub wiki:
https://github.com/ninja-build/ninja/wiki
README is now also Markdown formatted.

HACKING.md has always become outdated in the past, there are still some outdated infos in there (especially Windows). I think the wiki is a better place.
CONTRIBUTING.md (I think GitHub will create a link to that file automatically above the issues) has some additional info about C++11, using namespace std; and clang-format, but in general it's much more to the point. Objections?

Unfortunately Git ignore git mv when I change so much of the file. Maybe I should split this into two commits.


Can't type anything in Homested upgrades.

If you make a homested and add an upgrade you can't enter anything into the upgrade description box.

I can't reproduce this. Is it still an issue in 1.808?

The Update seemed to have fixed it. Thx.


kubernetes-helm: 3.8.1 -> 3.8.2

Description of changes
https://github.com/helm/helm/releases/tag/v3.8.2
Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

@saschagrunert Notice:

Which platform have you built? Maybe the extra patch should be done for Linux only.

I've pushed an update that hopefully deals with the failures on linux, although if someone w/ a linux machine could review this PR, I'd be very appreciative.

I've pushed an update that hopefully deals with the failures on linux, although if someone w/ a linux machine could review this PR, I'd be very appreciative.

@techknowlogick Can you correct the 3 issues I pointed out?

If it does not error for Darwin, should skip for Linux only.
Rename package to "kubernetes-helm" to match top-level.
Add mainProgram = "helm";

@superherointj thanks :) I've made those changes.

@superherointj thanks :) I've made those changes.

Did you add mainProgram = "helm"; to meta?
IMO, stdenv.isLinux is more precise. Shorter also.

Did you add mainProgram = "helm"; to meta?

whoops, you're right. Added it to the wrong place. Thanks again for all your patience.

IMO, stdenv.isLinux is more precise. Shorter also.

updated

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

2 packages built:

kubernetes-helm
telepresence2


Docker compose install on Ubuntu 18.04 bare metal : Authenticated user does not have namespace 'guest'

Hello,
I am trying a basic install on a bare meta server Ubuntu 18.04 updated.
Docker and Docker compose installed last versions
I follow the OpenWhisk documentation for Docker compose install :
$ git clone https://github.com/apache/incubator-openwhisk-devtools.git
$ cd incubator-openwhisk-devtools/docker-compose
$ make quick-start
The 'make' works until this error occurs :
ok: whisk auth set. Run 'wsk property get --auth' to see the new value.
ok: whisk API host set to https://<IP_ADDRESS>
error: Authenticated user does not have namespace 'guest'; set command failed: Get https://<IP_ADDRESS>/api/v1/namespaces: dial tcp <IP_ADDRESS>:443: getsockopt: connection refused
Makefile:289: recipe for target 'init-whisk-cli' failed
I looked at the makefile, different mailing lists but no clue on how to fix the problem.
Any idea is welcome.
Thanks
FZ

After some more investigation :

netstat report that the port 443 is open
It looks that the API web server is not working

@Franzerfos I'm sorry you're having issues.  Can you check the https://github.com/apache/incubator-openwhisk-devtools/blob/master/docker-compose/README.md#troubleshooting doc and see if it helps ?

@Franzerfos is this still an issue? Please reopen if so.


About Discourse Graph in ACL2020 GraphSum

Thanks for your work, I read your paper and code of GraphSum. But I have a question. How to implement discourse graph? I don't find it in your code.

The discourse graph is constructed based on http://knowitall.cs.washington.edu/gflow/

The discourse graph is constructed based on http://knowitall.cs.washington.edu/gflow/

@Weili-NLP How do you preprocess discourse graph to the model input?


build: improved test output filtering style

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (ea7f20b) to head (c8663c2).

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #35   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           46        46
  Lines          872       872
=========================================
  Hits           872       872

Flag
Coverage Δ

gi
100.00% <ø> (ø)

optional
100.00% <ø> (ø)

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

coverage: 100.0%. remained the same
when pulling c8663c2793a0904bea2e30dfb5804a3aa3994a45 on feature/make-tools
into ea7f20b124179e81697c382133b575b8c702f58a on main.


destructuring e.g. in HtmlInputElement (jsx) brings up wrong error

Environment (please complete the following information):

OS (e.g., Windows 10): macos
Extension version (e.g., 1.2.3):Last updated
05/04/2022, 22:35:16

Describe the bug:

when destructuring an object in an htmlinputelement (like <input {...someObject}....) with someObject having properties like title, value, name etc, The extension brings up error of category axe/forms:
Element has no title attribute Element has no placeholder attributeMicrosoft Edge Toolsaxe/forms
i understand that attributes are not propeties, but the code would be working fine and i think this is done pretty often and shouldnt bring up an error
Repro steps:

yarn create react-app --template typescript
replace App component with

function App() {

  const [test, setTest] = useState( {title: 'hi', placeholder:'blubb', type:'text', name:'a', value:'value'} as HtmlInputData)

  return (

      <input {...test} onChange={e => handleChange(e.target.value)} />

  );

  function handleChange(value: string): void {
    throw new Error('Function not implemented.');
  }
}

Expected behavior:

dont show error
Additional context:

Thanks @bertutron! This is definitely a false-positive that shouldn't happen.
I created a bug in the webhint project we depend on to track this there as well (since that's where we'll need to make the fix first). We'll take a look and see if we can get this fixed.

https://github.com/webhintio/hint/issues/5166


Replace nwb with Vite and Storybook

While extending this library, I discovered that the project cannot be built or previewed via nwb, as OpenSSL does not support the utilized algorithm anymore. The matching exception is as follows:
 ⠙ Creating UMD buildsnode:internal/crypto/hash:80
  this[kHandle] = new _Hash(algorithm, xofLen, algorithmId, getHashCache());

 Error: error:0308010C:digital envelope routines::unsupported
    at new Hash (node:internal/crypto/hash:80:19)
    at Object.createHash (node:crypto:139:10)
    at module.exports (super-react-gist/node_modules/webpack/lib/util/createHash.js:135:53)
    at NormalModule._initBuildHash (super-react-gist/node_modules/webpack/lib/NormalModule.js:417:16)
    at super-react-gist/node_modules/webpack/lib/NormalModule.js:452:10
    at super-react-gist/node_modules/webpack/lib/NormalModule.js:323:13
    at super-react-gist/node_modules/loader-runner/lib/LoaderRunner.js:367:11
    at super-react-gist/node_modules/loader-runner/lib/LoaderRunner.js:233:18
    at context.callback (super-react-gist/node_modules/loader-runner/lib/LoaderRunner.js:111:13)
    at super-react-gist/node_modules/babel-loader/lib/index.js:59:103 {
  opensslErrorStack: [
    'error:03000086:digital envelope routines::initialization error',
    'error:0308010C:digital envelope routines::unsupported'
  ],
  library: 'digital envelope routines',
  reason: 'unsupported',
  code: 'ERR_OSSL_EVP_UNSUPPORTED'
}

Node.js v21.7.1

nwb has not been updated in more than 3 years. After updating, it still contains 93 vulnerabilities reported by NPM: 5 low, 45 moderate, 35 high, and 8 critical.
For my own purposes, I changed nwb out with Vite and Storybook.
This pull request contains those changes, hoping to improve the future development experience:

Remove any dependency on nwb.
Build the NPM package via Vite, containing the file paths in the package layout previously used by nwb. This is to maintain backwards compatibility with applications that rely on linking the UMD file export by UNPKG, for example via a <script> tag.
Define React and react-dom as a peer dependency, addressing #3.
Convert the demo into a Storybook and set up a matching GitHub Action, which automatically publishes it to the repositories GitHub pages. This keeps the demo documentation up-to-date automatically and removes the need for the current, outdated page and the branch gh-pages. For the action to work, you need to set up the repository to allow Pages to be deployed as, described in the Action documentation.
Format table in README properly and remove unnecessary return at the end of a function.

hello @hfxbse. First, thank you for taking the time to work on such major improvements. As with most OSS this library got unmaintained, as I am quite busy lately and forgot to check it. People like you make OSS worth it. I will take a better look on the weekend and will get back to you. Thanks again for your effort.


Some(tuple) is two args in the online playground

Repro: playground. The option should have the type: option((int, int)).
It works in rtop and with my own function:
let f = (a) => a;
f((1,1));

It works in the new playground that we'll be switching to soon.


Add a license?

Can you add a license? I'd like to use this code, but not sure what the license is. Thanks!
Also, would you be open to a PR that replaces sha1sum with the internal sha1 function?

My favorite license. The same as chat:
The chat program is in public domain. This is not the GNU public license. If it breaks then you get to keep both pieces.


ENH: Update ITK CI tags to v5.2rc02

Update ITK CI to reference ITK master branch as of 02-10-2021.

build-test-documentation (ubuntu-18.04) ran into:
Run sed -i "6559d" /opt/hostedtoolcache/Python/3.8.6/x64/lib/python3.8/site-packages/sphinx/domains/cpp.py
  sed -i "6559d" /opt/hostedtoolcache/Python/3.8.6/x64/lib/python3.8/site-packages/sphinx/domains/cpp.py
  shell: /bin/bash -e {0}
  env:
    pythonLocation: /opt/hostedtoolcache/Python/3.8.7/x64
sed: can't read /opt/hostedtoolcache/Python/3.8.6/x64/lib/python3.8/site-packages/sphinx/domains/cpp.py: No such file or directory
Error: Process completed with exit code 2.

Looks like build-test-documentation (ubuntu-18.04) is failing in other PRs as well rather than stemming from these changes. See PR 193 checks.

Seeing failures aligning with Issue 178 again. Is this a blocking issue?

Looks like build-test-documentation (ubuntu-18.04) is failing in other PRs as well rather than stemming from these changes. See PR 193 checks.

build-test-documentation is fixed in #187

Time to rebase other PRs on top of this.


Description
https://git-scm.com/docs/git-commit#Documentation/git-commit.txt---signoff
Suggested Solution
oco --signoff <email>
if this takes too long we can alias.
Alternatives
set in some config file
or have a way to not have oco prompt for push oco config set OCO_GITPUSH=false
.. then we can && git commit --amend --signoff && git push --force
Additional Context
https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository#about-commit-signoffs
https://wiki.linuxfoundation.org/dco
For linux foundation, DCO is a requirement.

DCO sign-offs must be present on every single commit, or else the contribution will not be accepted.
A contributor agreement may be signed by a third party, like a company, on behalf of its employees, whereas the DCO is always an attestation by the author of the contribution.

@kaovilai
How about using prepare-commit-msg hook?
By doing the following, the AI-generated message by oco will be set from the beginning when you commit with git.
This way, you can use all git options in combination.
$ oco hook set // set prepare-commit-msg hook
$ git commit --signoff // in addition to the signoff message, the message generated by oco is set from the beginning (overwriting is also possible)

Sure if it would be documented as the way opencommit dev prefer to this issue.

Can we customize the message template on the prepare-commit-msg hook? For instance, I want to add the ticket ID as a prefix to the generated message by opencommit. Regex won't be a problem, please don't focus on this part.
Branch name: MPL-1234-some-bug-fixes
Commit message should be like this: "MPL-1234: ${generatedMessage}" and signoff ("signoff" can be added via git commit command as you mentioned above).


DB access in perform()

Hey,
How i can access database in perform() method of Job class in codeignitor?
I have implemented it and it is working but i want to do some sort of updation in perform() method. Is there any way to do this?

@rabnawazPikesSoft

I haven't used CodeIgniter since late version 2.x, so I don't know how it works now.  When I was using it, though, I had a CLI-only route set up that would set up the environment variables and include(FCPATH . '/vendor/bit/resque'), thus ensuring I had access to the framework from within my jobs, since the framework had started the worker(s).  (You can also use the APP_INCLUDE environment variable to include() any file you like to do this, but that doesn't seem to work as well for this.)
One thing to keep in mind is that each job is run in a forked process, so you'll need to reconnect to your DB manually when the job starts (or, more accurately, sometime between job start and the first DB interaction).  The same goes for pretty much any other PHP resource-type value.


Version bump to 0.4.0

@JuliaRegistrator register

@JuliaRegistrator register

Registration pull request updated: JuliaRegistries/General/19843
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.4.0 -m "<description of version>" fba4756150c8675efb0b0d07b65bcbce7974e2c5
git push origin v0.4.0


Migration to Hugo

I am considering creating a new repository with support for Hugo instead of Jekyll. I am satisfied with all aspects of this blog, but I am not a fan of Jekyll. I am posting this issue to gauge the level of interest in this idea and determine if it is worth further exploration.

Since this is not an bug or enhancement, rather it is to see if people are interested on a port to a different framework and probably out of scope for this repository, I am converting this to a discussion.
PS: It will be very interesting to see a Hugo port of al-folio. I have previously thought making a port myself but held back as it might not have such a interested user base.


"devServerPort" Invalid option change

When I try to change the devServerPort in app/config and run npm run dev again, the port will automatically change back to 8080 @scriptPilot

@crcms - Solved for you?


Rework interactables

Interactables use an empty Node3D as a parent and 'origin' node to set up both handles and interactable_handle_driven scenes. This PR will attempt to make the scenes stand alone and more intuitive. Sliders can be orientated in the editor and slide along their rotated axis. Hinges can do the same and offer 'hinge_axis' as a variable to allow the user to specify an axis to rotate around.
These are breaking changes and a work in progress. Joysticks must be incorporated and handles tested. I'll adjust the interactable_demo_scene to feature the final changes.

Last commit also adding 'hinge_wrapping' bool for wrapping between min and max limits (infinitly spinning wheel)


Need to set up documentation

One part of documentation should include models for the eight schools and the radon datasets (the 'hello-world's of Bayesian and multilevel models.


[IGNORE]-Moving to new subscription

PR for issue
What is being addressed
Describe the current behavior you are modifying.  Please also remember to update any impacted documentation.
How is this addressed

Describe the changes made, and if appropriate, why they are addressed this way
Note any pending work (with links to the issues that will address them)
Update documentation

/test

/test

/test-force-approve


Add thumbnail for metaclasses talk

The image URL you use seems to be a format that isn't widely supported among browsers (yet?): https://caniuse.com/#feat=webp
Would you mind changing this to use the jpeg version?

@jonemo , I updated the PR with the JPEG version.
Thanks @aktech for spotting this!

Thanks @redapple


Remove PodIP from ContainerStatus

Fix #5524

Needs a rebase btw.

Looks good, just the rebase and the nit.

Rebased.

Addressed the comments.

Resolve an issue caused by rebase. Thanks!

LGTM, will merge on green thanks @dchen1107!


Alacritty + ueberzug on Nix OS

I'm running yazi on NixOS inside Alacritty, and the image previews are not working.
I also tried opening a shell with uberezugpp available and then starting alacritty and yazi from there, but this doesn't seemt o make a difference.
Any tips on getting this working?

Please do a echo $TERM, $TERM_PROGRAM, $XDG_SESSION_TYPE and paste the result here.

❯ echo term: $TERM, termprogr: $TERM_PROGRAM, sesstype: $XDG_SESSION_TYPE
term: alacritty, termprogr: sesstype: wayland

Please run ueberzug layer and paste
{"action":"add","identifier":"preview","max_height":0,"max_width":0,"path":"/your/image-path.jpg","x":0,"y":0}

into it, then Enter, and to see if any image is shown, without exit the ueberzug

I think you might have the same issue
https://github.com/sxyazi/yazi/issues/207#issuecomment-1732191416

Please reopen this issue if the problem persists, closing then


Fix brotli link order

When brotli is linked as a static library with MinGW, it breaks

@ivanka2012 thanks so much for your  patch. I did not test enough in MinGW.


[StarOS] Plan is different from local table if there is colocation group occasionally

Steps to reproduce the behavior (Required)
nosetests-3.4 -s --with-xunit --xunit-file=./result/test_pipeline_local_shuffle_py_TestPipelineLocalShuffle_test_aggregate_on_others.xml --verbose case/system_case/test_dql/test_pipeline_local_shuffle.py:TestPipelineLocalShuffle.test_aggregate_on_others --nologcapture
Expected behavior (Required)
Test passes.
Real behavior (Required)
Test failed.
StarRocks version (Required)

You can get the StarRocks version by executing SQL select current_version()

The logic of colocation group of lake table is different from local table, and sometimes it takes up to 10 seconds for the colocation group  to be stable. If the colocation group is not stable, local bucket shuffle join can be executed. So the times of  local shuffle join of lake table is less than local table.


Cassandra source closes socket

In writing a set of integration tests. Cassandra-rs will fail to connect to shotover configured with a Cassandra source, while cqlsh will connect succesfully.
After a quick look at wireshark, it appears that the cassandra-rs driver (a wrapper around the c/c++ datastax one) tries a few unsupported protocol version, which fail or get downgraded. Cassandra itself wont shutdown the tcp connection, whereas shotover will causeing the driver to error out.
Given Cassandra supports this behaviour (as broken as it seems), shotover needs to support this. Protocol version errors shouldn't cause us to drop the connection.

Testing works locally, now trying to get automated build to work.


buildings dataset for Russia

Hello. We (Geoalert.io) are creating buildings dataset based on automatic buildings detection across Russia. Now it contains more features than pure OSM. We would like to propose this dataset (or the difference with OSM) to be implemented into RapID to share with community. What shell we do?

Thanks for bringing up the idea @Godnik ! Supporting arbitrary data sources is also an idea we start to develop, and it requires quite a bit of efforts to reach the stage of being purely user driven.
Right now, to handle it in a similar way to MS buildings, we need to do some extensions on the backend service. Do you guys have a webservice that hosts the generated data and can be queried with spatial constraints (e.g. bbox)? Engineering wise that will make the backend integration easier to do. Also, what is the license on your data? Do you have a webpage explaining the license on the data?

Thanks for your reply. Yes, we do have a service that provides API for querying by bbox / polygon.
We created the initial project description at https://github.com/Geoalert/urban-mapping, we should make it clearer in details soon.

@gaoxm we started to upload first parts of the buildings dataset https://github.com/Geoalert/urban-mapping

@Godnik thanks for the follow-up! The demo looks amazing - let us know when a description of the API is available and our team will look into possible ways of integration.

@gaoxm the description of API is ready at our page.
Can your team contact us for we provide them with the authorization details?
<EMAIL_ADDRESS>

Hi @Godnik! @gaoxm will be unavailable for a bit so I'll be your contact point here! I will contact you at the address you provided.

We have not forgotten about this! Please be patient with us...

@Bonkles is it fair to say that Esri's Community Maps data sharing is the best route to make this data available in Rapid.
@Godnik I realise this issue is quite a few years old now. Are there any new datasets that you'd be interested to make available in Rapid?